[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[McIDAS #XRR-599672]: Configuring scouring of McIDAS data
- To: zehel@xxxxxxx
- Subject: [McIDAS #XRR-599672]: Configuring scouring of McIDAS data
- From: "Unidata McIDAS Support" <support-mcidas@xxxxxxxxxxxxxxxx>
- Date: Tue, 18 Mar 2008 07:55:58 -0600
- Delivered-to: support-mcidas@unidata.ucar.edu by laraine.unidata.ucar.edu (Postfix) with ESMTP id EEE9ACB18F; Tue, 18 Mar 2008 07:55:58 -0600 (MDT) id D3098D5116; Tue, 18 Mar 2008 07:55:58 -0600 (MDT)
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
support@xxxxxxxxxxxxxxxx Boulder, CO 80307
----------------------------------------------------------------------------
Unidata HomePage http://www.unidata.ucar.edu
****************************************************************************
Ticket Details
===================
Ticket ID: XRR-599672
Department: Support McIDAS
Priority: Normal
Status: Closed