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

20030114: NLDN ldm-mcidas decoders for mcidas (cont.)

>From: "Happel, Shelly" <address@hidden>
>Organization: USF
>Keywords: 200301091811.h09IBGt26938 ldm-mcidas nldn2md


>Thanks so much (as always!!!!) for your much needed assistance. 
>I am still having some serious issues and I believe I understand some of
>where the problem is occurring. 
>I am unable to locate any MDXX files on the server. I know the NLDN packet
>is coming through because I can do the notifyme NLDN and see it arriving. 

This implies that the decoding is not working.

>I think my problem is in my pqact.conf - but I copied it from the
>ldm-mcidas-pqact.conf file. 


>Is there any way you can take a look at my machine. I am really lost on this
>and there's no one on campus to help me. My usual support guy is completely
>clueless and so am I. 

I jumped onto metlab and see that 'root' is editing ~ldm/etc/pqact.conf.
Can you exit your vi session for this file?

I took a quick look at the action for NLDN decoding, and see that it
is incorrect:

# Lightning data

        FILE    data/ldm/mcidas/lightning/\1_\2
        PIPE    -close
        nldn2md -d /home/ldm/data/mcidas 70 NLDN DIALPROD=LD \1\2 \3\400 DEV=CCN

You can not have both a FILE and PIPE in a single action.

I took a look at my example NLDN action in ldm-mcidas-pqact.conf, and
see that it doesn't have this mistake:

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
        PIPE    -close 
        nldn2md -vl logs/ldm-mcidas.log
        -d data/mcidas 70 NLDN DIALPROD=LD \1\2 \3\400 DEV=CCN

>Thanks in advance,

As soon as the edit session for pqact.conf is exited, I will fix the NLDN
action and see if we can't get the lightning decoding running on metlab.


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.