[CONDUIT #UDU-273265]: CONDUIT data.

Hi Carlos,

re:
> I have not yet received any communication regarding this ticket.
> would you please tell me what is the status of it?

I apologize for this slipping through the cracks!

re:
> Hi, I've been trying to get GFS data via the ldm without much success.
> our host at New Mexico Tech is heron.nmt.edu running ldm-6.6.5
> we are currently receiving IDS|DDPLUS and UNIWISC from rainbow.al.noaa.gov

> The following line:
> notifyme -v -l - -o 3600 -p "^data/nccf/com/gfs/.*/GFS/.*" -f CONDUIT -h 
> idd.unidata.ucar.edu

> produces the following output:

> Apr 04 21:57:38 notifyme[12099] NOTE: Starting Up: idd.unidata.ucar.edu: 
> 20080404205738.736 TS_ENDT {{CONDUIT, "^data/nccf/com/gfs/.*/GFS/.*"}}
> Apr 04 21:57:38 notifyme[12099] NOTE: LDM-5 desired product-class: 
> 20080404205738.736 TS_ENDT {{CONDUIT, "^data/nccf/com/gfs/.*/GFS/.*"}}
> Apr 04 21:57:38 notifyme[12099] INFO: Resolving idd.unidata.ucar.edu to 
> 128.117.140.3 took 0.034184 seconds
> Apr 04 21:57:38 notifyme[12099] NOTE: NOTIFYME(idd.unidata.ucar.edu): OK
> Apr 04 21:57:40 notifyme[12099] INFO: 49003 20080404212931.712 CONDUIT 004 
> data/nccf/com/gfs/prod/gfs.2008040418/gfs.t18z.pgrbf03.grib2 
> !grib2/ncep/GFS/#000/200804041800F003/OZMR/10 Pa PRES! 000004

I just verified that the pattern "^data/nccf/com/gfs/.*/GFS/.*" used in a 
'notifyme'
invocation will result in lots of data being reported as being available on
idd.unidata.ucar.edu.

> However, the line

> request CONDUIT "^data/nccf/com/gfs/.*/GFS/.*" idd.unidata.ucar.edu

> in ldmd.conf together with the lines

> CONDUIT "^data/nccf/com/gfs/.*/GFS/#.*/([0-9]{12})/.*"
>        FILE -overwrite -close data/ncep_gfs/gfs_\1.grib

> in pqact.conf do not produce any files

Your pqact.conf entry is incorrect because it:

1) encloses the Extended Regular Expression (ERE) in quotes (the quotes
   are needed for the 'notifyme' invocation so that the shell does not
   try to expand the ERE's .*, etc.)

2) specifies that the 12-digit datetime (#.*/CCYYMMDDHHMM) is immediately 
followed
   by a '/' (slash).  The 'notifyme' output shows that the datetime is 
immediately
   followed by a forecast hour specification, F003.

Consider one of the headers returned from your 'notifyme' invocation:

data/nccf/com/gfs/prod/gfs.2008040418/gfs.t18z.pgrbf03.grib2 
!grib2/ncep/GFS/#000/200804041800F003/OZMR/10 Pa PRES! 000004

Your ERE matches as follows:

^data/nccf/com/gfs/.*/GFS/# -- matches 
data/nccf/com/gfs/prod/gfs.2008040418/gfs.t18z.pgrbf03.grib2 !grib2/ncep/GFS/#

.*/([0-9]{12}) -- matches 000/200804041800

And then the next characters in the header is 'F003', not '/.*'.

I think you wanted to use either:

CONDUIT ^data/nccf/com/gfs/.*/GFS/#.*/([0-9]{12}).*/
        FILE -overwrite -close data/ncep_gfs/gfs_\1.grib

-- or, better yet --

CONDUIT ^data/nccf/com/gfs/.*/GFS/#.*/([0-9]{12})
        FILE -overwrite -close data/ncep_gfs/gfs_\1.grib

(better because the '.*/' is not needed to match).

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: UDU-273265
Department: Support CONDUIT
Priority: Normal
Status: Open