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

[Support #KEQ-115435]: RE: [ldm-users] New to LDM and Conduit

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: [Support #KEQ-115435]: RE: [ldm-users] New to LDM and Conduit
  • Date: Thu, 25 Oct 2007 09:39:06 -0600
Hi Samuel,

re:
> O.K. I think I have a regular expression that satisifies the CONDUIT
> part of this request.  Could you verify the following:

> REQUEST CONDUIT 
> "nccf/com/(gfs/prod/gfs.*pgrb2f|gens|ruc/prod/ruc2a.*(pgrb|sgrbf)20|nam/prod/nam.*(awip3d|awip12))"
>  ldm.meteo.psu.edu   PRIMARY
> REQUEST CONDUIT 
> "nccf/com/(gfs/prod/gfs.*pgrb2f|gens|ruc/prod/ruc2a.*(pgrb|sgrbf)20|nam/prod/nam.*(awip3d|awip12))"
>  idd.cise-nsf.gov    ALTERNATE

You can/should verify the request lines yourself using the LDM 'notifyme' 
utility.
Even though 'notifyme's to shu.cup.edu do not work (likely because of a firewall
setting), a 'notifyme' _from_ shu.cup.edu to your upstream feed host(s) should 
work
fine.

Please try the following yourself to get familiar with how 'notifyme' works:

<you logged as 'ldm' on shu.cup.edu>

notifyme -vxl- -f CONDUIT -o 3600 -h ldm.meteo.psu.edu -p 
'nccf/com/(gfs/prod/gfs.*pgrb2f|gens|ruc/prod/ruc2a.*(pgrb|sgrbf)20|nam/prod/nam.*(awip3d|awip12))'

Also do the same notifyme to your alternate upstream feed host, 
idd.cise-nsf.gov.

Modify the patter portion of the the 'notifyme' invocation to get a listing of 
exactly
the products you want and then transfer that pattern into your ldmd.conf 
request line.

> Also, how do I file this data for McIDAS to use?

I would not recommend that you process CONDUIT data for McIDAS just yet.  I 
have seen
some bugs in the code that handles GRIB2 messages so your experience with the
CONDUIT content may be less than optimum.  If, however, you want to try anyway,
you would simply add CONDUIT to the list of datastreams in the pattern action
file that sends model data to 'xcd_run'.  I seem to remember that your current
pattern looks like:

HDS   .*   PIPE
    xcd_run HRS

You would modify this to look like:

HDS|CONDUIT    .* PIPE
    xcd_run HRS

NB: be careful to use tabs were needed in pattern/action entries.

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: KEQ-115435
Department: Support CONDUIT
Priority: Normal
Status: Closed