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

20000628: ** Gempak Password Needed **



>From: James T Brown <address@hidden>
>Organization: UCAR/Unidata
>Keywords: 200006281544.e5SFi3T18691

>Unidata Support:
>
>I seem to have misplaced the password needed to 
>access the Gempak Distribution directories.  I
>seem to remember "XXXXXX", but
>I sure they have long sinced changed.
>
>I have a student that works with Dr Julie Winkler
>here at Michigan State that has requested use
>of the Gempak software and I would like to 
>reinstall and rebuild Gempak, Garp, etc.  Only
>problem is I can no longer download.
>
>Could you please send access information to
>either me (address@hidden) or Julie (address@hidden).
>
>Many thanks.
>
>Jim
>
>
>
>
>-- 
>==========================================================
>James T. Brown   
>UNIX Systems Administrator
>Geography/Fisheries & Wildlife
>Michigan State University
>
>email: address@hidden
>

Jim,

Believe it or not...same password as above. 
host: ftp.unidata.ucar.edu
login: gbuddy
passwd: XXXXXX

I'll attatch the basic Gempak download/installation instructions just in case.

Steve Chiswell
Unidata User Support



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_pl16.tar.gz

The current tar file is patched through patch level 16.

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.

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.

For case studies, you generally will set environmental variables for
SAT, GEMDATA, HDS, and NTRANS_META to point to the particular
case directories rather than realtime data directories. By using the 
environmental
variables, multiple sets of case studies can be accessed simply by
reconfiguring your csh environment. Once the Environmental variables are
set, launchinh Garp from the ntl launcher bar will obtain all the directory 
locations
inherited by the variables.


Steve Chiswell