[ldm-users] 20130620: re: Urgent! CONDUIT GFS002 and GFS003 don't appear in our queuej

• To: donna Cote <d-cote@xxxxxxxx>
• Subject: [ldm-users] 20130620: re: Urgent! CONDUIT GFS002 and GFS003 don't appear in our queuej
• From: Tom Yoksas <yoksas@xxxxxxxxxxxxxxxx>
• Date: Thu, 20 Jun 2013 11:54:04 -0600

Hi Donna,

re:
>I've thoroughly read 
>https://www.unidata.ucar.edu/data/conduit/ldm_idd/gfs_files.html
>
>and find that we (tamu.edu) are receiving gfs004 files but not gfs002 or 
>gfs003 files.
>
>For example:
>> [ldm@bigbird logs]$ date
>> Thu Jun 20 10:33:16 CDT 2013
>> [ldm@bigbird logs]$ ls -lth notify*
>> -rw-rw-r-- 1 ldm ldm 5.6M Jun 20 10:32 notifyme-dlc-gfs-2ndtest20130619.txt
>> -rw-rw-r-- 1 ldm ldm 1.1M Jun 19 17:00 notifyme-dlc-gfs-test20130619.txt
>> [ldm@bigbird logs]$ grep "#002" notifyme-dlc-gfs-2ndtest20130619.txt | wc -l
>> 0
>> [ldm@bigbird logs]$ grep "#003" notifyme-dlc-gfs-2ndtest20130619.txt | wc -l
>> 0
>> [ldm@bigbird logs]$ grep "#000" notifyme-dlc-gfs-2ndtest20130619.txt | wc -l
>> 24879
>> [ldm@bigbird logs]$
>
>I see the same results on sasquatch. These relay machines have the same 
>requests, that being:
>
>> $ grep -v ^# etc/ldmd.conf | grep -wi request | grep -wi conduit
>> REQUEST      CONDUIT "([09]$)"       idd.unidata.ucar.edu
>> REQUEST      CONDUIT "([18]$)"       idd.unidata.ucar.edu
>> REQUEST      CONDUIT "([27]$)"       idd.unidata.ucar.edu
>> REQUEST      CONDUIT "([36]$)"       idd.unidata.ucar.edu
>> REQUEST      CONDUIT "([45]$)"       idd.unidata.ucar.edu
>> REQUEST      CONDUIT "([09]$)"       weather3.admin.niu.edu
>> REQUEST      CONDUIT "([18]$)"       weather3.admin.niu.edu
>> REQUEST      CONDUIT "([27]$)"       weather3.admin.niu.edu
>> REQUEST      CONDUIT "([36]$)"       weather3.admin.niu.edu
>> REQUEST      CONDUIT "([45]$)"       weather3.admin.niu.edu
>> $

It looks like the portion of the Product ID that used to be #002 or
#003 is now #000.

re:
>Can anyone tell me why?
The products are all there, but the Product ID is different.

re:
>I've been at this for two days, so if you want 
>further details, just reply.

The LDM pattern-action file actions we use to process the GFS fields
from CONDUIT should be of help to you (and others) (NB: mind the
blank space that are actually tabs!):

# GFS grids Global_onedeg
#
CONDUIT ^data/nccf/com/gfs/prod/gfs\.(........)(..).*pgrbf(..|1..)\.grib2
        FILE
        
data/pub/native/grid/NCEP/GFS/Global_onedeg/GFS_Global_onedeg_\1_\200.grib2
#
# GFS Global_2p5 grids
#
CONDUIT ^data/nccf/com/gfs/prod/gfs\.(........)(..).*pgrbf([2-9]..)\.grib2
        FILE
        
data/pub/native/grid/NCEP/GFS/Global_2p5deg/GFS_Global_2p5deg_\1_\200.grib2
#
# GFS grids Global_0p5 
CONDUIT ^data/nccf/com/gfs/prod/gfs\.(........)(..).*pgrb2f
        FILE
        
data/pub/native/grid/NCEP/GFS/Global_0p5deg/GFS_Global_0p5deg_\1_\200.grib2

If you still are having problems, please send an email to:

support-idd@xxxxxxxxxxxxxxxx

OR

support-conduit@xxxxxxxxxxxxxxxx

Sorry for your frustration!

Cheers,

Tom
--
+----------------------------------------------------------------------------+
* Tom Yoksas                                            UCAR Unidata Program *
* (303) 497-8642 (last resort)                                 P.O. Box 3000 *
* yoksas@xxxxxxxxxxxxxxxx                                  Boulder, CO 80307 *
* Unidata WWW Service                            http://www.unidata.ucar.edu/*
+----------------------------------------------------------------------------+

• Follow-Ups:
  • Re: [ldm-users] 20130620: re: Urgent! CONDUIT GFS002 and GFS003 don't appear in our queue
    • From: Cote, Donna L

• References:
  • [ldm-users] Urgent! CONDUIT GFS002 and GFS003 don't appear in our queuej
    • From: donna Cote