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

[NOAAPORT #VHS-648329]: noaaport ingest

Hi Randy,

> Sorry for the delay in getting back with you. As you know we have an upstream 
> box
> (noaapnew) and a downstream box (noaapxcd). According to Heather we are using 
> the 2nd
> option you mentioned.


> Randy:
> This ldmd.conf file is on noaapnew.  Currently we have the second setup that 
> Tom
> mentioned, with all 4 instances:
> EXEC    "noaaportIngester -m"
> EXEC    "noaaportIngester -m"
> EXEC    "noaaportIngester -m"
> EXEC    "noaaportIngester -m"
> However, the first setup is in the file, but is commented out.  There are 
> older versions
> of this conf file sitting in the /usr/local/ldm/etc directory.  They had 
> setups similar
> to the first that Tom mentioned, but with some of the lines commented out.  
> Check out
> this file: /usr/local/ldm/etc/ldmd.conf.062111.
> Heather

> Since we only run mcidas, how do we tell whether we are Requesting the data

Login to your downstream box, noaapxcd, as the user 'ldm' (assuming, of
course that you are running the LDM as the user 'ldm' and then run the 

cd ~ldm
grep -i ^request etc/ldmd.conf

This will list back each REQUEST line in your LDM configuration file, 
that is uncommented.  The set of REQUESTs should answer the question if you
are, indeed, REQUESTing the data from your upstream machine, noaapnew.

> and if we are how would we look at the data in mcidas (adde) for example the 
> NIMAGE data.

The pieces that must be in place for you to look at the data in McIDAS
using ADDE are:

1) REQUEST the data in the LDM setup

   After the needed REQUEST lines are included in your ~ldm/etc/ldmd.conf
   file AND the LDM has been restarted so that those lines are activated,
   you can use the LDM utility 'notifyme' to see if you are receiving the

<as 'ldm'>
notifyme -vl- -f NGRID -o 3600
notifyme -vl- -f NIMAGE -o 3600

notifyme -vl- -o 3600

2) process the data REQUESTed

   This is done by action(s) in one or more LDM pattern-action files.  If
   your LDM setup for McIDAS followed the recommendations listed in the
   Unidata McIDAS-X User's Guide, you should have file following files
   in your ~ldm/etc directory:


   And, you should have EXEC lines in your LDM configuration file,
   ~ldm/etc/ldm.conf, that run 'pqact' invocations using these
   pattern-action files.  The LDM pattern-action files, LDM configuration
   file entries and 'ldm' crontab entries are created when the 'mcidas'
   user runs the 'mcxconfig' script from the $MCDATA directory of the
   'mcidas' account:

<login as 'mcidas' on noaapxcd>

 -- answer questions about which datastreams you want to configure
    for use

 NB: three different directories will need to be writable by 'mcidas'
 for the script to function fully/properly:

 - the directory in which McIDAS decoding will occur
 - the HOME directory of 'ldm'
 - the ~/etc directory of 'ldm'
  This example has the
   NIMAGE data being processed by the pqact invocation that is using
   the pqact.conf_mcidasA pattern-action file, but it does not contain
The EXEC lines that the person configuration things for McIDAS XCD
decoding will have to include in ldmd.conf will look something like:

exec    "pqact -f FSL2|NLDN|NNEXRAD|UNIWISC etc/pqact.conf_mcidasB"

   I say "something like" because the set of datastreams included in
   the '-f' option to pqact can vary. What you may find on your system
   depends on how the person who setup the decoding (Martha?) choose to
   do things (sorry, I don't know what this is)

3) ADDE dataset definitions will have to have been created so that the
   data files processed by the LDM actions in 2) can be found and

4) remote ADDE access may or may not need to be setup

   If you are only using the data from the 'mcidas' account on the
   noaapxcd machine, then remote server access does not need to be
   setup/configured.  If you want to access the data served by
   ADDE from an account other than 'mcidas' on noaapxcd or from
   some other machine, then the remote ADDE access needs to be

I don't know how things are configured there, so I can't provide more
specific information on what may or may not need to be done.


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: VHS-648329
Department: Support NOAAPORT
Priority: Normal
Status: Closed

NOTE: All email exchanges with Unidata User Support are recorded in the Unidata inquiry tracking system and then made publicly available through the web. If you do not want to have your interactions made available in this way, you must let us know in each email you send to us.