20010108: Gempak - LDMBRIDGE Decoder actions example pqact.co nf

Fred,

That was an oversight...it still works on our system because
I have both versions installed. I have corrected the decoder example.
You no longer have to give the path to the packing and station tables,
if the GEMTBL environmental variable is set, the decoder will find
$GEMTBL/stns/sfworld.tbl and $GEMTBL/pack/watch.pack on its own.

Steve Chiswell



>From: "Kopp, Fred" <address@hidden>
>Organization: UCAR/Unidata
>Keywords: 200101082053.f08Kr5o20045

>My question really was:
>   Why is gempak 5.6 using tables from gempak 5.4? Why not use the tables
>from 5.6? Do we have to use the tables from 5.4 for the decoder dcwatch?
>Or was this an oversight in the LDMBRIDGE Decoder actions examle on the
>UNIDATA web page?
>   When I got the LDM 5.1.2 running and Gempak5.6 installed, I downloaded
>the
>example pqact.conf files and put them together (without looking at every
>line)
>and everything worked more or less the way we wanted. However, in looking at
>the pqact.conf file line by line I note that one decoder is looking for
>tables
>from version 5.4. I hope that my question is clearer.
>
>Fred Kopp
>
>
>-----Original Message-----
>From: Unidata Support [mailto:address@hidden]
>Sent: Monday, January 08, 2001 1:19 PM
>To: Kopp, Fred
>Cc: 'address@hidden'
>Subject: 20010108: Gempak - LDMBRIDGE Decoder actions example pqact.conf
>
>
>
>>From: "Kopp, Fred" <address@hidden>
>>Organization: UCAR/Unidata
>>Keywords: 200101081849.f08Inxo12151
>
>>The following is extracted from the example pqact.conf file on your web
>>page. My question is: Should the 
>>references be to gempak5.4 or the current 5.6 (or 5.6A when I get around to
>>it)? I just noticed this 
>>because our firewall disappeared and we have been hacked and etc, etc. I am
>>trying to bring LDM 
>>back up independent of a local network.
>>Fred Kopp
>>
>># 
>># Watch box coordinates 
>># 
>>DDPLUS ^WWUS40 KMKC ([0-3][0-9])([0-2][0-9])
>> PIPE decoders/dcwatch -t 30 
>>-d data/gempak/logs/dcwatch.log 
>>-s /home/gempak/NAWIPS-5.4/gempak5.4/tables/stns/sfworld.tbl 
>>-p /home/gempak/NAWIPS-5.4/gempak5.4/tables/pack/watch.pack 
>>data/gempak/storm/watches/watches_YYYY_MM.gem # 
>>
>
>
>Fred,
>Most references from 5.6 are the same as in 5.4, with a few exceptions:
>
>1) in 5.6, the decoders can now be passed an environmental variable with
>the -e flag, so that the above could be represented in 5.6 as:
>DDPLUS ^WWUS40 KMKC ([0-3][0-9])([0-2][0-9])
>       PIPE    decoders/dcwatch -t 30
>       data/gempak/logs/dcwatch.log
>       -e GEMTBL=/home/gempak/NAWIPS-5.4/gempak5.4/tables
>       -s sfworld.tbl -p watch.pack
>       data/gempak/storm/watches/watches_YYYY_MM.gem
>
>As, a result, if you follow the tutorial examples for 5.6, you will see
>the -e flag is used. You will have to set the complete path in 5.4.
>
>2) 5.6 now has dcmetr instead of dchrly
>
>3) 5.6 has several additional decoders in the pqact.conf examples that
>   you won't find in 5.4.
>
>
>You can find the 5.4 old pqact.conf decoders examples from the web pages at:
>http://www.unidata.ucar.edu/packages/gempak/tutorial/pqact/decoders.tbl_5.4_
>last
>
>Steve Chiswell
>****************************************************************************
><
>Unidata User Support                                    UCAR Unidata Program
><
>(303)497-8644                                                  P.O. Box 3000
><
>address@hidden                                   Boulder, CO 80307
><
>----------------------------------------------------------------------------
><
>Unidata WWW Service                        http://www.unidata.ucar.edu/
><
>****************************************************************************
><
>