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

Re: Re: GFS ensemble data: name change affects ldmd.conf regex?

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.

  • Subject: Re: Re: GFS ensemble data: name change affects ldmd.conf regex?
  • Date: Mon, 02 Oct 2006 16:52:20 -0600
Christian,

The 850 mb data will have a pattern such as:
prod/gefs.*TMPK/850 Pa PRES

(the Pa is because the vertical coordinate of the grid data is actually
Pascals
though the 850 is scaled be 10-2 for printing equvalent mb)

You can see the names of each field in the status file, such as:
data/nccf/com/gens/prod/gefs.20061002/18/pgrb2a/gec00.t18z.pgrb2aanl !
grib2/ncep/SPEC62MRF/#000/200610021800F000/TMPK/850 Pa PRES! 000009

Steve Chiswell
Unidata User Support

On Fri, 2006-09-29 at 22:37 +0200, Christian Pagé wrote:
> Steve,
> 
> Thanks again for being so quick to help us!
> Since our bandwidth is a little bit limited, is it possible, by
> example, to just ask for TMPK at 850 mb for ensemble data?
> 
> Let's say that I have this pqact.conf action:
> CONDUIT
> prod/gefs\.(........)/(..)/pgrb2a/(ge.*)\.t..z\.pgrb2af(.*)
> !grib2/ncep/(.*)/\
> (.*)/(.*)/TMPK/850 mb!
> 
> Can I put this in the ldmd.conf to ask only for this field??
> request      CONDUIT      "status|ST.opnl/MT.nam|(prod/gefs.*
> !grib2/ncep/.*/.*/.*/TMPK/850 mb!)"
> 
> Regards,
> 
> Christian
> UQAM
> 
> 2006/9/29, Steve Chiswell <address@hidden>:
> > Christian,
> >
> > For the CONDUIT files on the idd, the NAM files will match with
> > "MT.nam", and the new ensemble files will match with "prod/gefs". The
> > other parts of your request line shown below will have no effect since
> > there are no longer MT.eta headers in the data
> > stream, and the bmoav and cy23r strings don't match any CONDUIT
> > products.
> >
> > A single request line for nam and ensembles (which will receive the
> > status files) can look like:
> >
> > request      CONDUIT      "ST.opnl/MT.nam|prod/gefs"
> >
> > If you want all the status files for the other products too, but just
> > the NAM and Ensemble grids, then
> >
> > request      CONDUIT      "status|ST.opnl/MT.nam|prod/gefs"
> >
> >
> > Steve Chiswell
> > Unidata User Support
> >
> >
> > On Fri, 2006-09-29 at 22:10 +0200, Christian Pagé wrote:
> > > Hi everyone,
> > >
> > > WIth the new name change for GFS ensemble data in the CONDUIT feed:
> > > how this affects the regex used in ldmd.conf feed configuration?
> > >
> > > I currently have:
> > > request         CONDUIT "(status)|(ST.opnl/MT.(eta|nam|bmoav|cy23r|ensg))"
> > >
> > > How must I change this request to take into account of the name changes?
> > > I am not sure how I should update this request line.
> > >
> > > Regards,
> > >
> > --
> > Steve Chiswell <address@hidden>
> > Unidata
> >
-- 
Steve Chiswell <address@hidden>
Unidata