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

[CONDUIT #JEK-252803]: conduit gfs

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.

  • Subject: [CONDUIT #JEK-252803]: conduit gfs
  • Date: Wed, 10 Apr 2013 14:58:22 -0600
Patrick,

I'm guessing this is because the helicity fields and possibly others were 
removed, as Rebecca Cosgrove mentioned in your message to gembud.

Pretty easy to check, though, with GDINFO on an old and new file.

Michael James
Unidata



> Conduit / LDMers,
> 
> I have an old script that uses 72 hours of gfs forecasts, that sniffs
> file sizes to ensure everything is ingested before the application runs.
> 
> For years I would have a lower limit of 57etc.. last week or so, the
> program didn't run so I lowered it some more to 54etc.. and this morning
> I see the program didn't run again, so I decided to investigate.
> 
> notice here that some of the F000-F072 files are below the 54etc threshold:
> 
> http://modelweather.com/files/patrick/gfs/gfs.size.04.10.2013.png
> 
> are fields being removed from the 0.5deg gfs, or is something else amiss?
> 
> cheers,
> 
> --patrick
> 
> --
> --------------------
> 
> Patrick L. Francis
> VP Media Logic Group
> http://www.medialogicgroup.com
> http://www.hamweather.com
> http://www.alertsbroadcaster.com
> http://www.modelweather.com
> 
> FB: http://www.facebook.com/wxprofessor
> --
> 
> 

Ticket Details
===================
Ticket ID: JEK-252803
Department: Support CONDUIT
Priority: Normal
Status: Open