[GEMPAK #EKM-763392]: 20080220: help with GEMPAK decoders at UNCO

Hi Gary,

re:
> ..., could you help me out some with the installation of the
> GEMPAK decoders?  I have been trying to figure that out without much
> success.

The installation of GEMPAK decoder support in the LDM environment is
pretty easy (even I have done it :-):

1) install GEMPAK as per instructions on the Unidata GEMPAK web pages:

   http://www.unidata.ucar.edu/software/gempak

   Please remember that part of this installation/upgrade is:

   - creating the NAWIPS link in the HOME directory of the user account
     in which GEMPAK is to be installed (this is recommended to be
     /home/gempak):

     <as 'gempak>
     cd ~gempak
     ln -s GEMPAK5.11.1 NAWIPS

   - create the Gemenviron link in the HOME directory of 'gempak'

     ln -s NAWIPS/Gemenviron .                   <- Csh, Tcsh users
     -- OR --
     ln -s NAWIPS/Gemenviron.profile Gemenviron  <- Bash, Bourne, Ksh users

   - adding a 'source' of Gemenviron in 'gempak's shell definition file
     (.cshrc for Csh and Tcsh; .bash_profile for Bash, Sh, and Ksh)

     For the Cshell, this would look like:

# set GEMPAK environment
source /home/gempak/Gemenviron

   - N.B., you _must_ insure that the user running your LDM (typically user
     'ldm') has read access to the ~gempak/NAWIPS directory hierarchy.  'ldm'
     needs to be able to read tables in the GEMPAK distribution to know how
     to name output data files, etc.

2) prepare the LDM account to use GEMPAK decoders

   - over in the LDM account, you need to make sure that you have created a 
     directory in which decoders will be copied (we recommend ~ldm/decoders)
     and also make sure that directory is in the PATH for the user running
     the LDM (again, user 'ldm'):

     <as 'ldm'>
     mkdir ~ldm/decoders
     -- edit 'ldm's shell definition file and make sure that ~ldm/decoders,
        ~ldm/util, and ~ldm/bin are in the PATH definition

     If this directory did not exist before this step, or if this directory
     was not in the PATH for 'ldm', you will need to:

   - source your shell definition file (e.g., 'source .cshrc') and then
     stop and restart your LDM

   - copy the decoders from the GEMPAK distribution to the ~ldm/decoders
     directory.

     Example if your OS is Linux:

     <as 'ldm'>
     cd ~ldm/decoders
     cp /home/gempak/NAWIPS/os/Linux/bin/dc* .

   - add sourcing of the GEMPAK environment file Genenviron to 'ldm's shell
     definition file in the same way that was done for the user 'gempak'
     (you do not have to create a Gemenviron link in the LDM HOME directory
     like was done for 'gempak', but you do have to replicate reading the
     /home/gempak/Gemenviron file like the example above).

   - make sure that the Gemenviron file is sourced and then stop and restart
     your LDM

You will see from the above that the user running the LDM _must_ have read
access to the GEMPAK installation directory hierarchy, otherwise environment
variables defined in ~gempak/Gemenviron will not be set; needed GEMPAK tables
will not be read; and the decoding will not work.


That's pretty much it in a nutshell.  Please let us know if you have problems
or further questions.

> Thanks!

No worries.

Cheers,

Tom
****************************************************************************
Unidata User Support                                    UCAR Unidata Program
(303) 497-8642                                                 P.O. Box 3000
address@hidden                                   Boulder, CO 80307
----------------------------------------------------------------------------
Unidata HomePage                       http://www.unidata.ucar.edu
****************************************************************************


Ticket Details
===================
Ticket ID: EKM-763392
Department: Support GEMPAK
Priority: Normal
Status: Closed