* OASES Version 2.1 README file *
Last Updated: 11. Feb. 2000
>>>>> OASES Installation <<<<<
The OASES export package is placed in the compressed tar files
oases.tar.Z <<<< Standard Unix compress oases.tar.gz <<<< gzip
Once you have transferred this file to your machine, you must first uncompress it:
> uncompress oases.tar.Z
or
> gunzip oases.tar.gz
You can now get a listing of the content by
> tar tf oases.tar
Now, move oases.tar to the root directory where you want the OASES directory tree to be placed, usually your HOME directory, and type
> tar xvf oases.tar
This creates the oases home directory Oases_clean. You may now rename the directory:
> mv Oases_clean Oases
Now go into the oases directory
> cd Oases
Here you will find the master makefile 'Makefile'. The version 2.1 Makefile uses the environmental parameter HOSTTYPE to determine which CPU you are installing on and sets the various compiler flags accordingly. It currently supports the following host types:
alpha DEC Alpha workstations decstation DEC 5000 RISC Workstations sun4 Sun Sparc Workstations iris4d Silicon Graphics Iris workstations i386-linux most PC Linux boxes i486-linux some PC Linux boxes
If you are installing on any of these platforms, and you are happy with the default setup of the oases directory tree, then simply type:
> make all
and the whole OASES package will be compiled and linked into binaries placed in the directory $HOME/Oases/bin/${HOSTTYPE}-${OSTYPE}, i.e. a platform-specific bin directory, allowing for a single Oases directory tree on mixed-platform networks. Otherwize edit the Makefile header to fit your desired setup. To add another host type, use one of the existing ones as a template. In most cases very few if any changes are necessary as OASES follows the FORTRAN-77 standard strictly.
LINUX USERS:
If you are installing OASES on a PC Linux box (i386-linux or i486-linux), you may have a choice of FORTRAN compiler. The default is the standard perl script fort77 (often attached by a symbolic link to the standard f77 command) which translates the code to C using f2c and then uses the GNU gcc compiler. Alternatively some i486-linux installations use the native GNU g77 compiler. Finally Linux users have the option of using the commercially available Absoft Fortran Compiler. All three compilers can be used for OASES, and the choice can be changed in the Makefile section on Linux definitions:
(Makefile)
.
.
.
##############################################################################
#
# PC HARDWARE RUNNING i486-linux
#
##############################################################################
#
# Compiler flags
#
#
# For the ABSOFT FORTRAN compiler, uncomment the following
# lines:
#
# FC.i486-linux-linux = f77 -f -s -N2 -N9 -N51
# LIB_MISC.i486-linux-linux = -lV77 -lU77
# MISC.i486-linux-linux =
#
# For the standard F2C FORTRAN compiler, uncomment the following
# lines:
#
# FC.i486-linux-linux = fort77
# LIB_MISC.i486-linux-linux = $(LIB)/libsysemu.a
# MISC.i486-linux-linux = misc.done
#
# For the native g77 FORTRAN compiler, uncomment out the following
# lines:
#
FC.i486-linux-linux = g77 LIB_MISC.i486-linux-linux = $(LIB)/libsysemu.a
MISC.i486-linux-linux = misc.done
#
CFLAGS.i486-linux-linux =
LFLAGS.i486-linux-linux = -L/usr/X11/lib
RANLIB.i486-linux-linux = ranlib
##############################################################################
.
.
.
>>>>> Post-Installation Setup <<<<<
After compiling and linking succesfully, put the bin directory BIN you have chosen into your PATH, and move all the command files shipped in oases/bin to this directory as well. To add the OASES bin directory to the path, use the statement (e.g. in your .cshrc file)
> setenv OASES_SH ${HOME}/Oases/bin
> setenv OASES_BIN ${HOME}/Oases/bin/${HOSTTYPE}-${OSTYPE}
> setenv OASES_LIB ${HOME}/Oases/lib/${HOSTTYPE}-${OSTYPE}
> set path = (OASES_SH OASES_BIN/$path)
If you are running under X-windows, answer x when MINDIS asks for the terminal type, or you may set the environmental variable in your .login file:
> setenv USRTERMTYPE x
Also, you have the option of using the default MINDIS plot package which is included in the OASES export package, or the public domain PLOTMTV graphics package.
To use PLOTMTV for color contour plots, issue the command:
> setenv CON_PACKGE MTV
Similarly to replace MINDIS with PLOTMTV for line plots, use the command
> setenv PLP_PACKGE MTV
Type rehash, and you are ready to go. You will find sample data files in Oases/tloss, Oases/pulse, and Oases/rcoef.
The documentation for OASES is available as a supplement to the SAFARI manual in LaTeX format in the file: Oases/doc/oases.tex
Good luck and have fun.
Henrik Schmidt