Christian,
The first thing I see is that
gfs\.(........)/gfs
does not match
gfs.2006112000/gfs
Your pattern only looks for 8 characters where there are 10. Try
gfs\.(........).*/gfs
The other thing I'd suggest is running
ldmadmin watch -f conduit
so you can see what you are actually getting based on
your request line.
David
> Hello all,
>
> I am still struggling with CONDUIT data selection in ldmd.conf, and
> appropriate regex in pqact.conf.
> I have succeeded for ensemble GSF data, with:
> ldmd.conf:
> request CONDUIT "(status|prod/gefs.*TMPK/850)" flood.atmos.uiuc.edu
> pqact.conf:
> CONDUIT prod/gefs\.(........)/(..)/p.*/(ge.*)\.t..z\.pgrb.*TMPK/850
> FILE data/models/conduit/ens/\1\2_\3_TMPK_850.grib
>
> However, I am trying to do something similar for the operational GFS in
> GRIB1 with:
> ldmd.conf:
> request CONDUIT
> "(status|prod/gfs.*PRMSL|prod/gfs.*HGT/500|prod/gfs.*HGT/1000|prod/gfs.*APCP|prod/gfs.*RH/2.m||prod/gfs.*TMP/2.m|pr\
> od/gfs.*TCDC/atmos_col|prod/gfs.*HGT/0C|prod/gfs.*UGRD;VGRD/10.m|prod/gefs.*TMPK/850)"
> flood.atmos.uiuc.edu
> pqact.conf:
> CONDUIT prod/gfs\.(........)/gfs\.t(..)z.*
> FILE data/models/conduit/gfs/\1\2_gfs.grib
>
> In the latter case, I don't get any file, not even the directory...
> I had validated my regex using the files injected in the CONDUIT:
> http://motherlode.ucar.edu/cgi-bin/ldm/statusgen_new.csh?/data/nccf/com/gfs/prod/gfs.2006112000/gfs.t00z.pgrbf03
> which shows, by example, that the file:
> /data/nccf/com/gfs/prod/gfs.2006112000/gfs.t00z.pgrbf03
> with the key: !grib/ncep/GFS/#003/200611200000/F003/HGT/500_mb!
> was sent, though I didn't get anything.
>
> Any thoughts on the possible errors in these regex?
> --
> Christian Pag_
> UQAM
