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

[LDM #YFY-835740]: Question about requesting conduit GFS ensembles

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: [LDM #YFY-835740]: Question about requesting conduit GFS ensembles
  • Date: Fri, 10 Nov 2006 13:01:33 -0700
David,

Your request line in ldmd.conf has some stray parentheses that are likely your
problem.

>"(MT.mrf.*|(prod/ruc2a.*grib2)|(ST.opnl/MT.gfs|prod/gfs.*pgrb[^2]|prod/gefs)
> |nccf/com/nam.*awip3d)"

You can also remove all references to "MT." and "ST.opnl" as these file paths
from the NWS telecomunications gateway are no longer used now that the
transition to the NCEP server is complete.

Your request pattern asks for RUC grib2, GFS 1.0 degree and 2.5 degree, 
ensemble,
and NAM 40km grids.


A pattern for these could look like
"prod/(ruc2a.*grib2|gfs.*pgrb[^2]|gefs|nam.*awip3d)"

Once you are receiving the data, the pqact.gempak_decoders patterns for gefs 
will work.

Steve Chiswell
Unidata User Support




> Dear ldm users,
> 
> 
> 
> I've been trying to configure ldmd.conf (ldm version 6.4.4; Gempak 5.9.4) to
> request the GEFS product and I'm stumped. Here is my request line in
> ldmd.conf:
> 
> 
> 
> request CONDUIT
> "(MT.mrf.*|(prod/ruc2a.*grib2)|(ST.opnl/MT.gfs|prod/gfs.*pgrb[^2]|prod/gefs)
> |nccf/com/nam.*awip3d)" hostname_of_data_server
> 
> 
> ^^^^^^^^^^^
> 
> 
> 
> Here are the relevant lines in pqact.conf:
> 
> 
> 
> #
> # CONDUIT ensemble products
> # ----------------------------------------------
> #
> CONDUIT     MT.ensg
> PIPE  decoders/dcgrib2 -d data/gempak/logs/dcgrib2_CONDUITens.log
> -e GEMTBL=/home/gempak/GEMPAK5.9.4/gempak/tables
> data/gempak/model/ens/YYYYMMDDHHfFFF_ens@@@.gem
> #
> # GRIB2 ensemble
> #CONDUIT    prod/gefs\.(........)/(..)/pgrb2a/(ge.*)\.t..z\.pgrb2af(.*)
> !(.*)!
> # data/nccf/com/gens/prod/gefs.20061004/06/pgrb2a/gep07.t06z.pgrb2aanl
> CONDUIT     data/nccf.*/(ge[cp][0-9][0-9])\.t[0-2][0-9]z\.pgrb2.* !(.*)!
> PIPE  decoders/dcgrib2 -v 1 -d data/gempak/logs/dcgrib2_CONDUITens.log
> -e GEMTBL=/home/gempak/GEMPAK5.9.4/gempak/tables
> data/gempak/model/ens/\1_YYYYMMDDHHfFFF.gem
> #
> # For now, don't mix TIGGE files with other ensembles since not all
> parameters
> # are available for all members
> # data2/TIGGE/gep07.t06z.pgrb2cf00
> CONDUIT     data2/TIGGE/(ge[cp][0-9][0-9])\.t[0-2][0-9]z\.pgrb2.* !(.*)!
> PIPE  decoders/dcgrib2 -v 1 -d data/gempak/logs/dcgrib2_CONDUITens.log
> -e GEMTBL=/home/gempak/GEMPAK5.9.4/gempak/tables
> data/gempak/model/tigge_gefs/\1_YYYYMMDDHHfFFF.gem
> 
> 
> What modifications need to be made to the above to receive the GFS ensemble
> products?
> 
> 
> 
> Thanks in advance for any help.
> 
> 
> 
> David Gold
> 
> 
> 
> 
> 
> 
> 


Ticket Details
===================
Ticket ID: YFY-835740
Department: Support CONDUIT
Priority: Normal
Status: Closed