11. Requirements for use

You must have access to either a Sun running Solaris 2.x, an SGI running IRIX 5.x, a DEC Alpha running OSF1, an IBM RS6000 running AIX 4.x, an HP running HP-UX 9.x, a PC running Linux, or a PC running Windows NT/XP/2000 with Interix (aka Microsoft Services for Unix) installed. Note that PAVE will also work on higher versions of most of the operating systems specified here.

You must have your input datasets in Models-3 IO/API (netCDF) UAM-IV, or UAM-V formatted data files.

PAVE can be displayed on most X displays with at least 8 bits of color. Using X windows software on a PC or Macintosh, you should be able to to display PAVE output from any of the above Unix platforms.

(OPTIONAL - READ THE REST OF THIS SECTION THIS ONLY IF YOU WANT TO ACCESS REMOTE DATA)

PAVE uses several optional files in your home directory when starting up, and writes over them with each PAVE session termination. These are used to maintain a snapshot of the current formulas, datasets, and aliases being used within PAVE:

        ~/.edss_rlogin_rc       # you may need to create if using remote data
        ~/.edss_exec_rc         # PAVE will create if not already there
        ~/.pave_history_rc      # PAVE will set this up automatically
        ~/.pave.alias           # PAVE will set this up automatically
        ~/.pave.AA.cases        # PAVE will set this up automatically
        ~/.pave.AA.formula      # PAVE will set this up automatically
The only one that really matters is ~/.edss_rlogin_rc, which is used for setting up remote data accessibility. Here are the contents of an example ~/.edss_rlogin_rc file, which you can borrow from to create your own. Also note the instructions for setting up remote .rhosts files and paths to the visd and busd daemons.
# ~/.edss_rlogin_rc
#
# -------------------------------------------
# If you want to use PAVE to read remote data:
# -------------------------------------------
# This file will need to be used by PAVE to launch a
# daemon on any remote machine(s).  The daemon(s) actually
# read the data and ship it back to your local machine.
#
# Copy this file to *your* ~/.edss_rlogin_rc and modify
# it appropriately
#
# On each machine you will need to set up a ~/.rhosts
# file that allows THIS machine to rsh to it.  On most machines
# a .rhosts file is a list of machine and login name pairs
# found in your home directory (e.g. sirrocco smith).  Make sure
# that this file is readable only by you for security reasons.
# 
# Suppose you are running PAVE on sirocco, and you want to use it 
# to read data that is sitting on sequoia.  Test to see that your
# .rhosts file on sequoia works by making sure the following
# commands on sirocco:
#
#   rsh sequoia.nesc.epa.gov -l <YOUR sequoia USERID> which visd
#   rsh sequoia.nesc.epa.gov -l <YOUR sequoia USERID> which busd
#
# successfully execute and tell you the paths to the visd and busd
# daemons on the remote sirocco machine.  The visd and busd daemons
# are in <pave installation dir>/<platform type>/bin/OPTIMIZE/
# for each platform type; on remote machines you may just wish to
# copy them to your home directory if it makes it easier for you.
# These daemons are used to read remote data; until they are in your
# remote path, you won't be able to read any data on that remote 
# machine.
#
# Any line in this file with a # in it is ignored.
#
####################################################################
# $HOME/.edss_rlogin_rc file contains the userids for remote machine
# names.  If remote userid is same as local, you don't need to list it.
# Lines preceded by a '#' are ignored.
# The format of the contents in the file are:
# <machine-name><space><userid>
# The machine name can be the entire name or without the domain name
# (eg. nox, rain)
####################################################################
#mary.jane.doe doe
sequoia.nesc.epa.gov tsr
t90.ncsc.org demo_t90
The other files will be set up for you automatically whenever PAVE executes.

12. Quick PAVE Jumpstart

This section can be used to guide you through an example PAVE session. If you are a new user, it can help you become familiar with most of PAVE's features. Once you have satisfied the Requirements for use section above, then:

Next Chapter: Known bugs and workarounds

Return To Table of Contents