This archive contains answers to questions sent to Unidata support through mid-2025. Note that the archive is no longer being updated. We provide the archive for reference; many of the answers presented here remain technically correct, even if somewhat outdated. For the most up-to-date information on the use of NSF Unidata software and data services, please consult the Software Documentation first.
Hi Samuel, re: > How do I check that there are no old files? There are some files with the > "2007" in > their name(for example WSR2.152.2007314.2300.1.255.grib), and they're > creation time > is in November, however they seem to have access times that are much more > recent. > Are they still being used somehow, or should I delete them? You should delete those files. I have learned that the BUFR/GRIB/MySQL scouring script, xcdscour, can miss some files whose names include dates that are outside of the scouring range being used. This results in old files being left on disk when they should be scoured. I have also seen GRIB messages where the date stamp inside the message does not match the runtime/valid time for the model run. This can result in files with seemingly very old dates/times in their names or files with dates that are in the future. I am not sure what to do about this just jet. Cheers, Tom **************************************************************************** Unidata User Support UCAR Unidata Program (303) 497-8642 P.O. Box 3000 address@hidden Boulder, CO 80307 ---------------------------------------------------------------------------- Unidata HomePage http://www.unidata.ucar.edu **************************************************************************** Ticket Details =================== Ticket ID: XRR-599672 Department: Support McIDAS Priority: Normal Status: Closed