[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

20050912: Storing only completed gribs?

Joseph,

The .status file will be inserted following the last grib product within a file.
If feed requests aren't being split, then you can check for receiving that file.
Also, the .status file contains the inventory of the data inserted, including
the number of bytes your output file should be if you need to check on that
if you are splitting the feed requests such that you may be receiving the
products out of order from which they were inserted.

Steve Chiswell
Unidata User Support

On Mon, 12 Sep 2005 address@hidden wrote:

>
> Hello list,
>
> We're currently pulling in GFS grids over the CONDUIT feed.  They are
> stored piece by piece into flat files by pqact using the FILE action
>
> CONDUIT 
> ^/afs/\.nwstg\.nws\.noaa\.gov/ftp/SL\.us008001/ST\.opnl/MT\.(gfs|avn)_CY.([0-9][0-9])/RD\.([0-9][0-9][0-9][0-9][0-9][0-9][0-9][0-9])/PT\.grid_DF\.gr1/fh\.0([0-9][0-9][0-9])_tl\.press_gr\.onedeg.*$
> FILE    data/avn/\3\2/avngrib.\3\2.f0\4
>
> Processes which use this data poll the directories containing those flat
> files, looking for new data.  They fail, however, if that file doesn't
> have a complete set of data yet.   Is there a common strategy for indicating
> that a grib has come in completely?   My only thought right now is to
> EXEC to a script which runs GRIB utilities to find out if a
> complete set has come in, and only when complete store the file in the final
> destination.
>
> Any help would be appreciated.  Thanks!
>
> Joseph Sheedy
> Technical Specialist
> 3TIER Environmental Forecast Group
> address@hidden
> (206)325-1573 x116
>