The PARAMESH package is distributed in a compressed tar file. If, for example, this file is untared in a directory called AMRDIR, makefiles will be placed in AMRDIR, and the package source code and headers files will be placed in sub-directories. You will also some test programs in other sub-directories. The users manual is packaged in a separate tar file for convenience.
The following list explains the distribution within the source file.
AMRDIR - a selection of makefile templates.
AMRDIR/source - the amr packages f90 source files, except those
which call MPI routines directly.
AMRDIR/mpi_source - the amr packages f90 source routines which
implement MPI messaging.
AMRDIR/headers - the amr packages fortran header files.
AMRDIR/templates - templates for routines which the user needs
to supply.
AMRDIR/utilities - utilities packages which add various, different functionality to
the basic PARAMESH package. These include different, parallel i/o routines,
i/o for the Chombovis graphics package, different interpolation routines,
support for multigrid algorithms, and a script for reordering the indices of the
main PARAMESH arrays (unk, facevar*, unk_e_*, and unk_n).
AMRDIR/Tests - some test programs and their makefiles.
You will need to have MPI installed on your system. In addition the version of MPI you are using must be configured to support Fortran 90 or 95 and C with whatever local compiler(s) you wish to use. The compiler should also have a C preprocessor option. If your Fortran compiler does not have a preprocessor option you will have to process all the Fortran source files through a C preprocessor before compiling.
In this section we give some guidance on strategies for compiling paramesh and linking it with your application files.
The example that we provide is a set of gmakefiles which we put together in order to illustrate the full list of paramesh source files, header files and user modified paramesh template files, and their relative dependencies. Compiling and linking with gmake.
In its normal usage, PARAMESH needs to be recompiled if you choose to modify any variables associated with the file PARAMESH_PREPROCESSOR.FH. You no longer need to do this. You have the option of compiling once to create the paramesh libraries described above and then linking your applcation to them. See How to Install and Compile PARAMESH as a Library.
You can write your application source code in either fixed (ie 72
column)
or free format. The PARAMESH header files which are required to be
included
in your source files should work for both cases.
The PARAMESH source files themselves are written using free
format. You may need to provide different compiler options
depending on which type of file you are using. Normally this is
not the case, but in our experience at least one compiler (xlf) does
require special compiler options to handel free format Fortran 90
source files.
The test programs in AMRDIR/Tests are not designed to be user friendly. Rather, we have included them so that if a user contacts us to report a bug, we can step them through some of these tests so we can verify that the package has been properly installed.