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

20000201: Gempak decoder actions



Ka Kit,

You have to create your own pqact.conf file tailored to your own needs.

The nwx.tbl and decoders.tbl entries shown on the GEMPAK www
pages are examples of entries that you might want to have in your pqact.conf.
The pqact.conf file that comes with he LDM distribution only contains some 
sample
lines. In general, you will want to use GEMPAK or McIDAS actions to store
the data into files appropriate to what data you want to look at on your system.

As an example, if you decide you want to use NWX, then take the sample
entries in the nwx.tbl file and import them into your pqact.conf file.
Similarly, if you want to run any or all of the GEMPAK decoders,
then import those entries from the decoders.tbl file into your pqact.conf file. 
The LDM only uses the one pqact.conf file. In that file you will have all your
data filing actions.

When incorporating entries from the sample files into your pqact.conf file,
remember that the TAB character psitions are important. Cutting and pasting
from an xterm will remove TAB characters and replace them with space characters.
Instead, it is generally easier to open the pqact.conf file in your
editor and the import the other tables into the file. Then, either
modify the entries as needed for your system, or comment the unneeded
entries out (using the # characters at the beginning of those lines).

The nwx.tbl examples should not need any editing to use them, except for
the location of the ldmConnect script from the 
ftp://ftp.unidata.ucar.edu/pub/decoders/decoders.tar.Z package
for storing the zone forecasts. The decoders.tbl entries will need 
to be modified according to where the decoders and ancillary tables are
located on your system (eg, the GEMEXE and GEMTBL locations).


Steve Chiswell
Unidata User Support




>From: "Ka Kit Lai" <address@hidden>
>Organization: .
>Keywords: 200002012044.NAA25677

>Steve:
>   I think I have something very wrong. The pqact.conf which stores in 
>/usr/local/ldm/etc was totally different from your description. Your 
>description of the pqact.conf file was very similar to the decoders.tbl in 
>my machine. I think I am confused. I thought the pqact.conf file was already 
>inside the LDM once I install the LDM, and I just download the decoders.tbl 
>and nwx.tbl. Can you please login to my machine again and check out the 
>pqact.conf (/usr/local/ldm/etc), decoders.tbl and nwx.tbl (both reside in 
>usr/local/ldm/bin). There is also another pqact.conf reside in 
>/usr/local/ldm/runtime/etc. Thank you.
>
>Or what you means is that I have to copy and paste the entry in the 
>decoders.tbl to the pqact.conf file to suit my preference. If that is the 
>case, which pqact.conf should I modify /usr/local/ldm/etc/pqact.conf OR 
>/usr/local/ldm/runtime/etc/pqact.conf
>
>>From: Unidata Support <address@hidden>
>>To: "Ka Kit Lai" <address@hidden>
>>CC: address@hidden
>>Subject: 20000201:  Gempak decoder actions
>>Date: Tue, 01 Feb 2000 12:52:32 -0700
>>
>>Ka Kit,
>>
>>You will edit your pqact.conf file to provide decoder pattern actions
>>such as those we previously discussed that are shown in the www page 
>>examples
>>*nwx.tbl and decoders.tbl).
>>
>>The pqact.conf file format is:
>>FEEDTYPE <tab> PATTERN
>><tab> PIPE <tab> decoder_action
>><tab>               decoder options
>><tab>              decoder options
>><tab>              output file
>>
>>The TAB positions are very important in the pqact.conf file.
>>You use the TAB characters to space between the various
>>parts of the pattern action statement.
>>So for example, to run the dchrly metar decoder from pqact, you specify:
>>
>>DDPLUS|IDS    ^S[AP].*
>>      PIPE    /usr/local/gempak/bin/sol/dchrly
>>      -b 9 -m 24
>>         -d data/gempak/logs/dchrly.log
>>         -p /usr/local/gempak/gempak5.4/tables/pack/hrly.pack
>>         -s /usr/local/gempak/gempak5.4/tables/stns/sfmetar_sa.tbl
>>         data/gempak/surface/YYYYMMDD_sao.gem
>>
>>The DDPLUS|IDS is the feedtype, meaning both DDPLUS and IDS data.
>>The pattern ^S[AP].* means to pass all data that start with SA or SP
>>(metar and speci reports), PIPE means to send the data directly to the
>>input of the decoder. The decoder dchrly I show as an example as being
>>installed in the /usr/local/gempak/bin/sol/ directory (assuming here
>>that /usr/local/gempak/bin is the $NAWIPS directory).
>>The -b, -m, -d, -p and -s options pass information to the decoder,
>>The -d option tells the decoder where to log its status information
>>(you need tor create the directory ~ldm/data.gempak/logs).
>>The -p option points to the $GEMTBL/pack/hrly.pack file which
>>tells the decoder what parameters from the data to store in the gempak 
>>file.
>>The -s option points to the $GEMTBL/stns/sfmetar_sa.tbl station table for 
>>location
>>information to use with the stations reporting.
>>
>>The final line in the sequence is the file name to putput the data to.
>>The data directory is relative to the ~ldm directory, so
>>this will store the GEMPAK data file in ~ldm/data/gempak/surface (again, 
>>you
>>have to create that directory).
>>
>>The GEMPAK format file will be created like 
>>~ldm/data/gempak/surface/20000201_sao.gem.
>>Once you have decoded data in those files, programs like Garp can read the 
>>data and plot
>>it for display. Garp uses the GEMDATA, SAT, HDS and other gempak variables
>>to located the decoded data files on your disk.
>>
>>The data storage options for nwx are very similar, however, they
>>simply use the FILE action to store the data to a file instead of having to
>>PIPE it to a decoder. nwx displays text bulletins like forecasts which
>>are not decoded. Nwx relies on the $TEXT_DATA variable to find the data
>>stored under the ~ldm/data/gempak/nwx directory.
>>
>>Steve Chiswell
>>Unidata User Support
>>
>> >From: "Ka Kit Lai" <address@hidden>
>> >Organization: .
>> >Keywords: 200002011913.MAA22775
>>
>> >Steve:
>> >   Sorry to bother you again because I really need to have gempak work 
>>this
>> >week. I already create those directories and there is no problem 
>>launching
>> >the gempak. Now comes to problem of how to load those data which comes in
>> >from albany. I know the pqact.conf is used to define what actions will be
>> >used to store the data on my system. But I dont know how to make the
>> >modification to this file? Do I specify where are those files should be
>> >stored? And how can I retrieve those files in the gempak? Do I need to
>> >create any crontab job?
>> >
>> >                                           Ka Kit Lai
>> >
>> >
>> >
>> >
>> >
>> >>From: Unidata Support <address@hidden>
>> >>To: "Ka Kit Lai" <address@hidden>
>> >>CC: address@hidden
>> >>Subject: 200021: 2000131: Gempak Gemenviron file
>> >>Date: Tue, 01 Feb 2000 11:27:04 -0700
>> >>
>> >>Ka Kit,
>> >>
>> >>You have to create the directory that $SAT points to.
>> >>
>> >>I logged in and sourced Gemenviron, and successfully echoed GEMDATA.
>> >>
>> >>halo{root}% source Gemenviron
>> >>halo{root}% echo $GEMDATA
>> >>/usr/local/ldm/data/gempak
>> >>
>> >>halo{root}% echo $SAT
>> >>/usr/local/ldm/data/gempak/images/sat
>> >>halo{root}% ls $SAT
>> >>/usr/local/ldm/data/gempak/images/sat: No such file or directory
>> >>
>> >>So, the Gemenviron file is correctly setting the variables to what you 
>>have
>> >>defined, but you will have to create the $SAT directory which should be
>> >>$GEMDATA/images/sat. The TEXT_DATA directory that nwx will use will
>> >>also need to exist. Presumably you will have your LDM create these data
>> >>products.
>> >>
>> >>The primary problem I see is that you have installed the Gempak
>> >>distribution
>> >>into the same tree that you are using as your GEMDATA tree. While this 
>>will
>> >>not prevent you from using the software, it will be quite messy to
>> >>maintain.
>> >>Typically, the gempak distribution is installed somewhere like 
>>/home/gempak
>> >>or
>> >>/usr/local/gempak, and the data ($GEMDATA) is under the ~ldm/data/gempak
>> >>tree
>> >>but the gempak data tree is not the same tree as $NAWIPS.
>> >>
>> >>At any rate, you will want to create your pqact.conf entries for your 
>>LDM
>> >>to
>> >>create the data products that Gempak will use.
>> >>
>> >>Steve Chiswell
>> >>Unidata User Support
>> >>
>> >>
>> >> >From: "Ka Kit Lai" <address@hidden>
>> >> >Organization: .
>> >> >Keywords: 200002011808.LAA20422
>> >>
>> >> >Steve:
>> >> >    I can only load the xsharp and garo. But I cannot load nsat, nwx 
>>and
>> >> >ntrans in the GUI. The Env variable SAT is still not defined. The
>> >>variable
>> >> >SAT is set to $GEMDATA/images/sat and I set the GEMDATA to
>> >> >/usr/local/ldm/data/gempak, but for some reason, I cannot echo GEMDATA
>> >>after
>> >> >I source this file. Did I set GEMDATA to the wrong path because
>> >> >$GEMDATA/images/sat does not exist. Is there any other variable I need 
>>to
>> >> >change for gempak to work?
>> >> >
>> >> >                                     Ka Kit Lai
>> >> >
>> >> >
>> >> >>From: Unidata Support <address@hidden>
>> >> >>To: "Ka Kit Lai" <address@hidden>
>> >> >>CC: address@hidden
>> >> >>Subject: 2000131: Gempak Gemenviron file
>> >> >>Date: Tue, 01 Feb 2000 09:36:38 -0700
>> >> >>
>> >> >>Ka Kit,
>> >> >>
>> >> >>In copying/pasting the Gemenviron file, you wrapped an if statement
>> >> >>line so that the "(" was continued on the next line. I fixed
>> >> >>your Gemenviron file so that the line is contained on 1 line now.
>> >> >>
>> >> >>Steve Chiswell
>> >> >>Unidata User Support
>> >> >>
>> >> >>
>> >> >>
>> >> >> >From: "Ka Kit Lai" <address@hidden>
>> >> >> >Organization: .
>> >> >> >Keywords: 200002011600.JAA16074
>> >> >>
>> >> >> >I think I have the data feed from Albany now. But there is still 
>>some
>> >> >> >problem when I launching the gempak. I edit following path for the
>> >> >> >Gemenviron file:
>> >> >> >setenv NAWIPS /scratch/gempak
>> >> >> >setenv GEMDATA /usr/local/ldm/data/gempak
>> >> >> >
>> >> >> >But when I source this file, a message:
>> >> >> >
>> >> >> >Too many ('s
>> >> >> >
>> >> >> >appears, what does that means? I didnt touch any of the parenthesis
>> >>and I
>> >> >> >dont think I have ever delete or add one. But I still can source 
>>this
>> >> >>file,
>> >> >> >but when I launch the gempak, something is wrong. The ntrans cannot 
>>be
>> >> >> >launch. And when I click on the nsat, it said:
>> >> >> >
>> >> >> >Env variable SAT is not defined.
>> >> >> >
>> >> >> >The variable SAT is set to $GEMDATA/images/sat and I set the 
>>GEMDATA
>> >>to
>> >> >> >/usr/local/ldm/data/gempak, but for some reason, I cannot echo 
>>GEMDATA
>> >> >>after
>> >> >> >I source this file. Did I set GEMDATA to the wrong path because
>> >> >> >$GEMDATA/images/sat does not exist. Is there any other variable I 
>>need
>> >>to
>> >> >> >change for gempak to work? If possible, please login to my machine 
>>and
>> >> >>take
>> >> >> >a look. I really appreciate it.
>> >> >> >
>> >> >> >                                      Ka Kit Lai
>> >> >> >
>> >> >>
>> >> 
>> >>**************************************************************************
>> > **
>> >> >><
>> >> >>Unidata User Support                                    UCAR Unidata
>> >> >>(303)497-8644                                                  P.O. 
>>Box
>> >> >>address@hidden                                   Boulder, 
>>CO
>> >> 
>> >>--------------------------------------------------------------------------
>> > --
>> >> >><
>> >> >>Unidata WWW Service                        
>>http://www.unidata.ucar.edu/
>> >> 
>> >>**************************************************************************
>> > **
>> >> >><
>> >> >
>> >> >______________________________________________________
>> >> >Get Your Private, Free Email at http://www.hotmail.com
>> >> >
>> >>
>> >>**************************************************************************
> **
>> >><
>> >>Unidata User Support                                    UCAR Unidata
>> >>(303)497-8644                                                  P.O. Box
>> >>address@hidden                                   Boulder, CO
>> >>--------------------------------------------------------------------------
> --
>> >><
>> >>Unidata WWW Service                        http://www.unidata.ucar.edu/
>> >>**************************************************************************
> **
>> >><
>> >
>> >______________________________________________________
>> >Get Your Private, Free Email at http://www.hotmail.com
>> >
>>
>>**************************************************************************** 
>><
>>Unidata User Support                                    UCAR Unidata 
>>(303)497-8644                                                  P.O. Box 
>>address@hidden                                   Boulder, CO 
>>---------------------------------------------------------------------------- 
>><
>>Unidata WWW Service                        http://www.unidata.ucar.edu/     
>>**************************************************************************** 
>><
>
>______________________________________________________
>Get Your Private, Free Email at http://www.hotmail.com
>