[LDM #FVG-157850]: ldmd.conf & pqact.conf

Hi Elmer,

re:
> Well, finally got it to file the data.  There is apparently something it
> doesn't like with the
> NNEXRAD ^SDUS[2357]. ....
> ([0-3][0-9])([0-2][0-9])([0-6][0-9]).*/p(...)(N0R) line. If you make it
> NNEXRAD ^SDUS[2357]. ....
> ([0-3][0-9])([0-2][0-9])([0-6][0-9]).*/p(...)(...), it does file all
> products just as you said.

Oops, the pattern should be:

NNEXRAD ^SDUS[2357]. .... ([0-3][0-9])([0-2][0-9])([0-6][0-9]).*/p(N0R)(...)

The only difference is in the very last part -- the product type comes
before the station ID.

The easiest way to check your pqact.conf patterns is to use the LDM utility
'notifyme'.  Here is an example:

<as 'ldm'>
notifyme -vxl- -f NNEXRAD -p "^SDUS[2357]. .... 
([0-3][0-9])([0-2][0-9])([0-6][0-9]).*/p(N0R)(...)"

You can play around with the pattern specified until it matches the product(s) 
you
want.  Then take the pattern and incorporate it into the pattern/action in 
pqact.conf.

re:
> Is there any way to get just the 1km products? (The 1km BREF is what I
> need, the rest is wasted space.)

The base reflectivity NNEXRAD (NOAAPORT Nexrad Level III) products are all 1 km 
as
are a number of the other products.

When you say you only need the BREF products, do you mean you only need thos
products at the first radar tilt (BREF1 aka N0R), or do you man that you want
the BREF products at all tilts?

In either case, there are two ways to accomplish what you want:

1) only request the products you want from the upstream LDM server. This is
   done by adjusting the ~ldm/etc/ldmd.conf 'request' line to request only
   the product(s) you want.

   For instance, if you want only the BREF1 products, your ldmd.conf request
   line for the NNEXRAD feed could look like:

request NNEXRAD "/pN0R" your_upstream_feed_host

   If, on the other hand, you want all of the BREF products (all tilts), your
   ldmd.conf request line could like like:

equest NNEXRAD "/pN.R" your_upstream_feed_host

2) if you want to continue to receive all products but only process the BREF
   product at tilt 1, your ~ldm/etc/pqact.conf pattern/action could look like:

NNEXRAD ^SDUS[2357]. .... ([0-3][0-9])([0-2][0-9])([0-6][0-9]).*/p(N0R)(...)
   FILE -close  data/nexrad/NIDS/\5/\4/\4_(\1:yyyy)(\1:mm)\1_\2\3

   If you want to process products from all tilts, your pqact.conf action
   could look like:

NNEXRAD ^SDUS[2357]. .... ([0-3][0-9])([0-2][0-9])([0-6][0-9]).*/p(N.R)(...)
   FILE -close  data/nexrad/NIDS/\5/\4/\4_(\1:yyyy)(\1:mm)\1_\2\3

> And what format are these files in?

They are in the format created by the PUP.  Details of the format can be
found on various NOAA websites.

> Do they need to be decoded in any way?

This depends on what you want to do with the files.  Unidata applications can
read/use the data files directly as can the SSEC distribution of McIDAS.  If
you have some other appliction that you want to use, you may be forced into
converting the data files into a format it can use.  How you would do this
is dependent on what other application you want to use.

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: FVG-157850
Department: Support LDM
Priority: Normal
Status: Closed