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

20000816: Download and installation instructions for GEMPAK

>From: "Pandya, Rajul E." <address@hidden>
>Organization: UCAR/Unidata
>Keywords: 200008161424.e7GEOFN07882

>Hi, 
>
>I think I have successfully installed and configured the LDM, and things
>seem to be working as they are supposed to. The web-pages on installation
>were excellent; I just went along, step by step. 
>
>I thought before I spent a lot of time configuring pqact.conf myself, I'd
>get the pqact.confs that are released with the GEMPAK and modify those. So,
>I'd like to go ahead and install GEMPAK, now, if I could. I am on a Intel
>machine, running Solaris.  (SunOS 5.7).  Is there a binary available?
>
>Finally, a question. I tried to install udunits, and ran into problems.  The
>problem centers around trying to build udunits with gcc, but I am wondering
>if I can postpone dealing with this problem and concentrate on getting
>GEMPAK usable first. Or are there dependencies in udunits (or the LDM) that
>are going to be a problem? 
>
>Thanks. 
>Rajul
>
>Rajul Pandya                                           
>Department of Geology and Astronomy            
>West Chester University
>West Chester, PA 19383
>V:610.436.2213   F:610.436.3036
>http://geology.wcupa.edu/~rpandya
>

Rajul,

GEMPAK does not rely on udunits or LDM, so that is not a problem.
If you don't have Sun's sparcworks fortran compiler (F77), then I'd suggest 
using the binary installation of GEMPAK for Solaris X86.

In the gempak ftp account, you will find the binary tarfile under:
nawips-5.4/binary/solaris_X86/gempak5.4_pl17_x86.tar.gz

You don't need the gempak5.4_pl17_libs.tar.gz tar file, unless you were writing
your own programs to access the GEMPAK libraries.
Also in that directory are several shareable libraries that you might need
in order to run the GEMPAK binaries. 

Once you download the tarfile, unpack it in an empty directory, typically
/home/gempak/NAWIPS-5.4 with the command:
gunzip -c gempak5.4_pl17_x86.tar.gz | tar xvf -

Once you have unpacked the tarfile, edit the Gemenviron file and modify
the directory specified by the NAWIPS environmental variable to
the directory name that you unpacked the distribution in (if it is
different than I suggested).

The Gemenviron file contains cshenvironmental variables which should be
used by any account that wishes to run GEMPAK. After you have edited 
Gemenviron, source the contents into your csh environment with the command:
source Gemenviron

Typically, you will want to add this command to your .cshrc file
(using the appropriate path to Gemenviron).

Once you have sourced the Gemenviron file, the $GEMLIB variable should
be set. You can move to this directory with "cd $GEMLIB".
I suggest you download the shareable library files (the *.so.* files
in the binary ftp directory) into your $GEMLIB data directory.
Then, set your LD_LIBRARY_PATH environmental variable to include this
directory, eg:
setenv LD_LIBRARY_PATH /usr/dt/lib:/usr/openwin/lib:${GEMLIB}

You can verify that your system is finding all the libraries needed to
run GEMPAK programs by using the command:
ldd $GEMEXE/garp

You should get a listing of all the libraries being found, such as:
ldd $GEMEXE/garp
        libXm.so.4 =>    /usr/dt/lib/libXm.so.4
        libXt.so.4 =>    /usr/openwin/lib/libXt.so.4
        libX11.so.4 =>   /usr/openwin/lib/libX11.so.4
        libm.so.1 =>     /opt/SUNWspro/lib/libm.so.1
        libF77.so.4 =>   /opt/SUNWspro/lib/libF77.so.4
        libM77.so.2 =>   /opt/SUNWspro/lib/libM77.so.2
        libsunmath.so.1 =>       /opt/SUNWspro/lib/libsunmath.so.1
        libc.so.1 =>     /usr/lib/libc.so.1
        libSM.so.6 =>    /usr/openwin/lib/libSM.so.6
        libICE.so.6 =>   /usr/openwin/lib/libICE.so.6
        libXext.so.0 =>  /usr/openwin/lib/libXext.so.0
        libsocket.so.1 =>        /usr/lib/libsocket.so.1
        libnsl.so.1 =>   /usr/lib/libnsl.so.1
        libdl.so.1 =>    /usr/lib/libdl.so.1
        libmp.so.2 =>    /usr/lib/libmp.so.2

If any of these entries are marked as not found, then you will
need to re-examine your LD_LIBRARY_PATH. You probably will want
to add this LD_LIBRARY_PATH definition your your ldm account as
wee so that the decoders will be able to run.

All the GEMPAK data decoders are found in the $GEMEXE executable directory.

The pqact.conf examples for the decoders typically need
to find ancillary station and packing tables from the
GEMPAK distribution. You should ensure that these paths are correctly
set for where you installed the GEMPAK tarfile on your system.
I usually copy the $GEMEXE/dc* programs into ~ldm/decoders for
convenience- and to make upgrading the GEMPAK distribution easier.

The NWX patterns for pqact.conf are just FILE actions and so decoders
are not needed, except for the entries that use the ldmConnect perl script 
from the ~ftp/pub/decoders/decoders.tar.Z distribution. This perl script 
joins together bulletins that are transmitted in several pieces.

I have attatched the general download instruction for GEMPAK below.

Steve Chiswell


---------------------------------------------------------------------
The information you need to download gempak is:
host: ftp.unidata.ucar.edu
login: gbuddy
passwd: XXXXXX

Please record the above information for your records.

Here are the general source download and building instructions. If
you are running Solaris x86 or Linux, you can download binary distributions
for these platforms. In particular, GEMPAK requires Motif which is not
part of Linux (must be purchased separately), so you would likely
need to download the binary distribution.

The source distribution for building is found under
~gbuddy/nawips-5.4/gempak54upc_pl17.tar.gz

The current tar file is patched through patch level 17.

To build Gempak from source, download and unpack the distribution into
a clean directory. Edit the csh file Gemenviron in the top directory
and define the NAWIPS environmental variable to be the directory you
unpacked into. Source the Gemenviron variables into your csh
environment to define $NAWIPS and all the tree locations relative to
NAWIPS. Then, if your system is standard configuration for Solaris,
Solaris for Intel (X86) IRIX, OSF/1, AIX, Linux, HPUX- you should be able 
to just type "make all", followed by "make install" when the compilation 
finishes. 
If you have libraries in non-standard places, then the 
$NAWIPS/config/Makeinc.xxxxx
file for your OS would have to be modified. You should not modify the 
optimization levels since some compilers don't work well with aggressive
optimization (Especially Digital UNIX).

Documentation for GEMAPK can be found as postscript files under
the $NAWIPS/doc/User_Guide directory, as well as online at:
http://www.unidata.ucar.edu/packages/gempak/tutorial/

All users that use Gempak should source Gemenviron into their csh
environment to define the Gempak variables and add the executable
directory into their path. Once the distribution is installed,
you can edit the data directory locations defined in Gemenviron-
but thats not a priority for building.

Plese refer all questions about the distribution and any problems
you may have to address@hidden. You may also wish to
subscribe yourself to the gembud email list at:
http://www.unidata.ucar.edu/mailinglist/mailing-list-form.html

Announcements about the GEMPAK distribution, including new distributions,
patches, and feature enhancements are made through that list. Also,
if you have information or need to find other users who may have
experience with a specific data set, then you are encouraged to
use the email list which is composed of fellow GEMPAK users in our community.

Once you have GEMPAK installed, you can use the "dc" realtime data decoders
with the LDM package to decode the data into GEMPAK format as it arrives
at your site. Refer to the LDM web pages for the installation of LDM and
getting connected to the IDD. Examples of LDM pqact.cont pattern/action entries 
for 
the various types of data for the GEMPAK decoders are found in the tutorial
as well as in the Examples section of the GEMPAK www pages.


Steve Chiswell