NAME
setup.csh, setup.sh - set up Antelope environment variables
SYNOPSIS
source setup.csh
. setup.sh
DESCRIPTION
The Antelope system requires setting some environment variables:
ANTELOPE,
PATH, and
MANPATH. These scripts
set up the environment for either csh-style shells or sh-style
shells.
Typically, the setup.csh file would be sourced from inside
a user's .cshrc or .tcshrc file, while the setup.sh file would
be sourced from the user's .profile or .bashrc.
ENVIRONMENT
setup.csh and
setup.sh set the following environment variables:
-
ANTELOPE
used by many routines to find data files relative to the installation
point.
-
ANTELOPEMAKE
points to a set of rules used by all standard Antelope make files.
-
MANPATH
used by man to find man pages.
-
MANSECT
This sets the order in which the man pages are searched. For instance,
programmers might prefer to see section 3 (programming interfaces) first, while others might
prefer to see section 1 (command line utilities).
-
PFPATH
Sets the order in which parameter files are read; the default is $ANTELOPE/data/pf,
then $ANTELOPE/local/data/pf, then ./pf, and finally ..
Note that all parameter files are read, and any parameters set in the final parameter
file read override the values in earlier parameter files.
-
DATAPATH
Specifies the directories which are searched for data files by datafile(3) and datapath(3).
These are typically static files which contain data used by an interface. Travel
time curves and map data are good examples.
setup.csh also sets the shell variables antelope and antelopemake as
a convenience.
DIAGNOSTICS
These setup files also run
check_antelope_installation(1), which may
complain about
improper installations.
SEE ALSO
antelopeenv(5)
check_antelope_installation(1)
BUGS AND CAVEATS
There are other Antelope environment variables which are not set
by
setup.csh and
setup.sh.
The user setting such variables must change them
when changing to a different release -- i.e., changing from
/opt/antelope/4.9 to
/opt/antelope/4.10. Failure to
update such variables may have confusing and unpredictable
results. However, by using \$ANTELOPE rather than $ANTELOPE -- explicitly
having the sigil (dollar sign) in the environment variable --
the user may avoid such problems. For example,
% setenv PFPATH '$ANTELOPE/data/pf:~/pf:.'
rather than
% setenv PFPATH $ANTELOPE/data/pf:~/pf:.
AUTHOR
Daniel Quinlan
Boulder Real Time Technologies, Inc.