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

20030507: NLDN data and LDM instructions



>From: "Huffines Gary R Maj AFIT/ENP" <address@hidden>
>Organization: AFIT/ENP
>Keywords: 200305071324.h47DOr7V010796

Gary,

>Sorry to bother you again over the NLDN data issue.  We sent you an
>email asking about conversion of NLDN data from GEMPAK format to netCDF
>a couple of days ago and the reply you gave us works pretty well, but
>isn't exactly what I would like to do.  I have another question that may
>be easier or not.

>I would like to be able to save the NLDN data in its original format as
>it comes from SUNY-Albany and allow it to be converted to GEMPAK format
>for other programs to use.  Right now, we have the LDM pqact.conf file
>set up to pipe the NLDN data to the conversion program that puts it into
>GEMPAK format.  If we could save it to a file in its original format and
>convert it to GEMPAK that would be outstanding! Is there a way to
>configure the LDM commands to do both?

Yes, you can put as many actions in ~ldm/etc/pqact.conf for a product
as you like.  All you need to do is add a FILE action to your pqact.conf
file to save the data as received in individual files; check the
interity of the pqact.conf file (check for typos, etc.) using
'ldmadmin pqactcheck'; and, assuming that there are no mistakes, send
a HUP signal to the pqact process using 'ldmadmin pqactHUP'.

Here is one example of a FILE action for NLDN lightning data:

NLDN    
^([12][0-9][0-9][0-9]|[0-9][0-9])([0-3][0-9][0-9])([0-2][0-9])([0-5][0-9])([0-5][0-9])
        FILE    -close  data/nldn/\1\2\3.ingest

This will file NLDN data in files whose names look like:

/local/ldm/data/nldn% ls
200312413.ingest  200312504.ingest  200312519.ingest  200312700.ingest
200312414.ingest  200312505.ingest  200312520.ingest  200312701.ingest
200312415.ingest  200312506.ingest  200312521.ingest  200312702.ingest
200312416.ingest  200312507.ingest  200312522.ingest  200312703.ingest
200312417.ingest  200312508.ingest  200312523.ingest  200312704.ingest
200312418.ingest  200312509.ingest  200312614.ingest  200312705.ingest
200312419.ingest  200312510.ingest  200312615.ingest  200312706.ingest
200312420.ingest  200312511.ingest  200312616.ingest  200312707.ingest
200312421.ingest  200312512.ingest  200312617.ingest  200312708.ingest
200312422.ingest  200312513.ingest  200312618.ingest  200312709.ingest
200312423.ingest  200312514.ingest  200312619.ingest  200312710.ingest
200312500.ingest  200312515.ingest  200312620.ingest  200312711.ingest
200312501.ingest  200312516.ingest  200312621.ingest  200312712.ingest
200312502.ingest  200312517.ingest  200312622.ingest  200312713.ingest
200312503.ingest  200312518.ingest  200312623.ingest

The pattern used for the filing uses the YYYY (\1), Julian day JJJ (\2)
and hour HH (\3).

You can use the LDM 'notifyme' command to get an idea of what the product
headers look like as follows:

notifyme -vxl- -f NLDN -o 3600

This asks your own LDM to let you know about all of the NLDN products
received in the past hour (3600 seconds).  After you see what the
headers look like, you can setup your own regular expression pattern
for them to use in pqact.conf and FILE the data anywhere you have
write permission.

>Thanks for your time.

No worries.

>Gary
>GARY R. HUFFINES, Major, USAF, PhD
>Assistant Professor of Atmospheric Physics
>Air Force Institute of Technology
>
>Mail to:
>AFIT/ENP
>2950 P Street BLDG 640
>Wright Patterson AFB OH 45433-7765
>Voice: 937-255-3636 ext 4511
>Fax: 937-255-2921

Tom Yoksas

>From address@hidden Wed May  7 08:22:05 2003

Thanks for the feedback!  I'll give it a try this afternoon.

Regards!

Gary Huffines