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

[IDD #LFO-343862]: No GFS 0.5degree since yesterday

Hi Gyorgi,

> It seems that either I have stopped getting GFS 0.5degree data or gempak
> stopped processing it.
> Do I need to change anything in my setup?

Most likely yes.  NOAA/NCEP switched generation of products that get distributed
in CONDUIT to a new super computer, and part of the upgrade was a slight change
in the Product IDs for GFS model output.

Very simply, the change that was made (again, by NCEP, not us) can be seen in 
'notifyme' snippets:

pre-update of NCEP super computer:

!grib2/ncep/GFS/#000/202206291200F003/RELH/500 hPa PRES! 000350

after update of NCEP super computer:

!grib2/ncep/GFS/#000/202206291200F003/RELH/500 hPa PRES! 000350

The change was 'prod' field is now 'v16.2'.

Give the above, your LDM pattern-action file action(s) that are used for 
processing CONDUIT
products will need to be modified to replace 'prod' in the extended regular 
(ERE) with '.*'.  Here is an example of the kind of change we need to make for 
TDS GFS processing:

old action:

# GFS Global 0.25 degree analysis only
CONDUIT ^data/nccf/com/gfs/prod/gfs\.(........)/(..).*pgrb2\.0p25\.a

modified action:

# GFS Global 0.25 degree analysis only
CONDUIT ^data/nccf/com/gfs/.*/gfs\.(........)/(..).*pgrb2\.0p25\.a

Note that the 'prod' field was simply replaced by '.*' (no quotes, of course).


After making a change to a pattern-action file that is in active use, you do 
need to restart your LDM for the change(s) to take effect.  All you have to do

-- edit the action(s) in the pattern action file(s)

-- check that there were no gross typos in the edit:

ldmadmin pqactcheck

-- if there were no errors indicated, send a HUP signal to the lead LDM server:

ldmadmin pqactHUP

> I have ldm 6.13.16, and the new community gempak 15.0.

The version of the LDM will not matter, and I can't imagine that
the version of GEMPAK will matter either.

Please let us know if you have questions on the above.


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: LFO-343862
Department: Support IDD
Priority: Normal
Status: Closed
NOTE: All email exchanges with Unidata User Support are recorded in the Unidata 
inquiry tracking system and then made publicly available through the web.  If 
you do not want to have your interactions made available in this way, you must 
let us know in each email you send to us.