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

20050425: GEMPAK / LDM

Mark,

The pqact.gempak file that is generated will expect you to copy the
GEMPAK decoders into a "decoders" directory under LDMHOME.

That is, in your ~ldm directory create a "decoders" directory,
and then copy the current GEMPAK decoders you have into that
directory with: 

cd ~ldm/decoders
cp $GEMEXE/dc* .

By keeping copies of the GEMPAK decoders there, the running versions won't 
be damaged when you install new versions of GEMPAK.

Your ~ldm/directory should have a "data" directory, which is where your ldm.pq 
will reside. The GEMPAK decoders will create subdirectories under 
~ldm/data/gempak
as they run, though you should create the ~ldm/data/gempak/logs directory
so that you would get error messages even if the decoder fails to  be able to
create its edata directory.

After that, if you have problems getting your data, please send in the
appropriate log files from ~ldm/data/gempak/logs so that I can
see what the decoder is doing. The ~ldm/logs/ldmd.log will have log information
from pqact if the decoder is failing to execute. The $GEMDATA/logs directory
will have decoder specific logging such as table information, bad data etc.

Steve Chiswell
Unidata User Support


>From: Mark Seefeldt <address@hidden>
>Organization: UCAR/Unidata
>Keywords: 200504252304.j3PN4sv2010253

>I am finally getting around to getting LDM and GEMPAK running.  I 
>recently installed LDM 6.3.0 and I installed GEMPAK 5.8.1.  After 
>completing the installation I worked on the configuration files.
>
>I created the file pqact.gempak using the shell script gen_pqact.csh.
>I then copied the generated file, pqact.gempak, to /usr/local/ldm/etc.
>A copy of this file can be found at:
>http://foehn.colorado.edu/seefeldt/pqact.gempak
>
>After completing the
>I then edited the ldmd.conf file:
>added:  exec    "pqact etc/pqact.gempak"
>I then requested three sets of products from my upstream site:
># observational data from the #NOAAPORT streams
>request    IDS|DDPLUS    ".*"    rainbow.al.noaa.gov
># ETA/NAM model
>request    HDS    "/mNAM_84"    rainbow.al.noaa.gov
># RUC model
>request    HDS    "/mRUC"    rainbow.al.noaa.gov\
>A copy of this can be found at:
>http://foehn.colorado.edu/seefeldt/ldmd.conf
>
>The next step was then staring up the ldm:  ldmadmin start
>
> From my amateur perspective, the ldm is handling the retrieving of that 
>data without much problem.  Some of the files are also showing up in the 
>data directory without any problems.  Yet there are also some files like 
>SAO and model output which does not appear to be making it anywhere.
>
>In the instructions:
>http://my.unidata.ucar.edu/content/software/gempak/GEMPAK5.8/configuration.htm
> l
>It says: "Create your data and log directories that LDM will expect 
>under the ~ldm/data/gempak tree."
>How am I supposed to know which data and log directories I am to create?
>
>My guess is that it is either a read/write problem and/or directory 
>creation.
>
>A copy of the ldm log file can be found at:
>http://foehn.colorado.edu/seefeldt/ldmd.log
>
>Please advise me as to what I need to do next.
>
>Thank You
>
>Mark Seefeldt
>
>
--
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.