DIFFERENCES BETWEEN V2.0 and V1.0

Version 2.0 adds a number of new features to PARAMESH. The most important are,

• the ability to advance the solution at all refinement levels (V1.0 assumed the solution was only advanced on leaf nodes).
• elimination of the need to reserve permanent storage for guardcell data.
• bug fixes for all bugs which have been reported to us since the release of V1.0.

• marker flags for grid blocks - these flags are inherited by child blocks and so can be used to control application execution for selected spatial volumes.
• the ability to fill guardcells in a selected coordinate direction only.

It should be emphasized that V2.0 will support any applications which ran using V1.0, with almost no modification to the application source code. The required modifications, all of which are very minor, are summarized below.

Note: V2.0 will not improve performance on machines with high message latencies, (eg clustered PCs). We are currently working on a revision which will. V2.0 which has a significantly different internal structure to V1.0, was a vital preparatory step in this process.

Modification Steps

1.
The header files have been modified. You will have to repeat the process of setting parameters and pre-processor variables in these files. Any new parameters or pre-processor variables which you did not previously have are set to default values which will work for your application as it was configured with V1.0.

2.
Replace

include 'mpp/shmem.fh'

  

wherever it appears in your application files, with

#include "amr_shmem.fh"

  

A C shell script file called changes_v1_to_v2_script has been included which uses SED to make this change for all *.F, *.f and *.fh files in a given directory. Use this with care! Before trying it, backup all the files in the target directory. Then copy the files changes_v1_to_v2_script and sed_cmd_v1_to_v2, which is also provided, into the target directory. cd to that directory, add execute permission to the file changes_v1_to_v2_script, then type

                   changes_v1_to_v2_script

  

This should do it.

You must also add amr_shmem.fh and compiler.fh to the list of header files in any makefiles which you use in your application directories.

3.
Construct amr_1blk_bcset.F. This replaces the routine amr_bc_block.F which the user was required to supply in V1.0. Detailed information on how to construct amr_1blk_bcset.F appears in the User's Guide. A version of amr_bc_block.F which works by calling amr_1blk_bcset.F is included in AMRDIR/source, so codes written for V1.0 which include calls to amr_bc_block.F will still work.

4.
Add a fifth dimension to the WORK array wherever it appears in your application files.

Return to Main Page.