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 Gyorgi, re: > 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 two 'notifyme' snippets: pre-update of NCEP super computer: data/nccf/com/gfs/prod/gfs.20220629/12/atmos/gfs.t12z.pgrb2.1p00.f003 !grib2/ncep/GFS/#000/202206291200F003/RELH/500 hPa PRES! 000350 20220629T153848.938716Z after update of NCEP super computer: data/nccf/com/gfs/v16.2/gfs.20220629/12/atmos/gfs.t12z.pgrb2.1p00.f003 !grib2/ncep/GFS/#000/202206291200F003/RELH/500 hPa PRES! 000350 20220629T153848.938716Z 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 expression (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 FILE /data/ldm/pub/native/grid/NCEP/GFS/Global_0p25deg_ana/GFS_Global_0p25deg_ana_\1_\200.grib2 modified action: # # GFS Global 0.25 degree analysis only # CONDUIT ^data/nccf/com/gfs/.*/gfs\.(........)/(..).*pgrb2\.0p25\.a FILE /data/ldm/pub/native/grid/NCEP/GFS/Global_0p25deg_ana/GFS_Global_0p25deg_ana_\1_\200.grib2 Note that the 'prod' field was simply replaced by '.*' (no quotes, of course). NB: After making a change to a pattern-action file that is in active use, you do _not_ need to restart your LDM for the change(s) to take effect. All you have to do is: -- 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 re: > 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. 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: 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.