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

20030317: LDM with NOAAPORT SDI

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: 20030317: LDM with NOAAPORT SDI
  • Date: Mon, 17 Mar 2003 18:36:18 -0700
>From: "Hongming Qi" <address@hidden>
>Organization:  NOAA
>Keywords:  200303122036.h2CKaqB2028638 NOAAPORT SDI LDM-6

Hongming,

>I am trying to configure how to connect LDM  with Noaaport. SSEC said 
>that data could be read from NOAAPORT output stream via FIFOs. Therefore 
>I tried to use the LDM command "pqing". The lightning data is under WMO 
>header SFUS41 KWBC. The following is my setting in LDM:
>
>1) add the below in the file "ldmd.conf"
>
>      exec    "pqing -f wmo  /tmp/jmb.fifo.2"

Two things: first, the feed type should be capitalized. Second, WMO is a
mnemoic for several feed types (i.e., it is a compound feed type).  WMO is
the same as the combination of IDS|DDPLUS (a single stream) and HRS.
Since the lightning data is binary, what you really want is:

exec    "pqing -f HRS /tmp/jmb.fifo.2"

>2) add the below in the file "pqact.conf"
>
>      WMO     ^SFUS(..) (....)  .*
>                     FILE    /home/ldm/incoming/US\2\1

And this would then change to:

HRS     ^SFUS(..) (....)  .*
        FILE    /home/ldm/incoming/US\2\1

Beware of which white space is tabs and that no white space can
occur before the feed type:

- no white space before HRS
- tab between HRS and ^SFUS
- tab before FILE
- tab between FILE and /home/ldm/...

Also the trailing '.*' on the pattern is not necessary since it is
redundant.

>But no data is coming by using the above. I want to know if my 
>configuration for LDM is correct.

I would make the changes I indicate above.  The other thing I would
do is use the LDM 'notifyme' command to see if/when the products
are received:

notifyme -vl- -f ANY -o 3600 -p SFUS41

I just did this on an LDM we have setup to ingest the HRS data
from a NOAAPORT SDI, and I see lots of SFUS41 products:

% notifyme -vl- -f ANY -o 3600 -p SFUS41
Mar 18 01:29:10 notifyme[8365]: Starting Up: localhost: 20030318002910.481 
TS_ENDT {{ANY,  "SFUS41"}}
Mar 18 01:29:10 notifyme[8365]: NOTIFYME(localhost): OK
Mar 18 01:29:17 notifyme[8365]:     1242 20030318002923.293     HDS 45834860  
SFUS41 KWBC 180027
Mar 18 01:29:34 notifyme[8365]:     1236 20030318003026.093     HDS 45835516  
SFUS41 KWBC 180028
Mar 18 01:29:35 notifyme[8365]:     1302 20030318003125.263     HDS 45836178  
SFUS41 KWBC 180029
Mar 18 01:29:36 notifyme[8365]:     1194 20030318003227.384     HDS 45836738  
SFUS41 KWBC 180030
 ...

>I check the manual about command 
>"pqing", it seems like I should specify the tty device name or the file 
>name. But I asked our system administrator, he said there is no 
>specified device name of  ingester. So I used the filename instead. 
>That's the binary Noaaport data ouput stream from SSEC ingester system. 

Your system administrator is correct.

>Could you help me check if these settings are correct? Specially for the 
>command "pqing". I have no experince about this command before. I 
>appreciate it.

Please let me know if the above helped.

Tom