
DIFFERENCES and ADDITIONS BETWEEN V3.2 and PREVIOUS VERSIONS
Version 3.2 is not a major revision. It adds some optimizations for
MPI execution, fixes some minor bugs which have been reported to us,
and adds some additional features.
With this version of PARAMESH we have not continued to update the
'shmem' version of the code. We still distribute it and will answer
questions regarding its use, but please be aware that none of the
features described below will work with this version. Also, we no
longer test the 'shmem' version. Therefore, WE STRONGLY URGE PEOPLE
TO UPGRADE TO THE MPI VERSION OF PARAMESH AND USE IT HENCEFORTH !!!.
The new featurs in PARAMESH 3.2 are,
-
Users now have the option of compiling PARAMESH as a library and
linking to it when they compile their application. In this mode all
the parameters which were previously set in the
'paramesh_preprocessor.fh' file can now be set at runtime by providing
a file called 'amr_runtime_parameters' without recompiling PARAMESH.
Note that this version is backwards compatible and if you prefer, you
can still use PARAMESH in its old mode and set everything as you
previously did in 'paramesh_preprocessor.fh'. For more information see
HOW TO INSTALL & COMPILE PARAMESH AS
A
LIBRARY.
-
In previous versions, by setting the arrays interp_mask_unk,
interp_mask_work, inter_mask_fc, interp_mask_nc, or interp_mask_ec, a
user could control the order of the interpolating polynomial which is
used during the prolongation operation. Now, these arrays also
control the restriction operation. As a result, guardcell filling
will use a polynomial of the order selected in the interp_mask_*
arrays since internally it uses both the prolongation and restriction
operations. For more information see
The Users' Guide section on interpolation.
-
Users now have the option of selecting a directory or filesystem to
which
all paramesh output (including checkpoint files) will be redirected.
This is set in paramesh_preprocessor.fh using the preprocessor
variable OUTPUT_DIR. Alternatively, if the library feature described
above is used, the directory is specified in the runtime parameter
file 'amr_runtime_parameters'.
Return to Main Page.