Parallelization
<wikitex>
ROMS supports serial, OpenMP, and MPI computations, with the user choosing between them at compile time. The serial code can also take advantage of multiple small tiles which can be sized to fit in cache. All are accomplished through domain decomposition in the horizontal. All of the horizontal operations are explicit with a relatively small footprint, so the tiling is a logical choice. Some goals in the parallel design of ROMS were:
- Minimize code changes.
- Don't hard-code the number of processes.
- MPI and OpenMP share the same basic structure.
- Don't break the serial optimizations.
- Same result as serial code for any number of processes.
- Portability - able to run on any (Unix) system.
First, some C Preprocessor options. If we're compiling for MPI, the option -DMPI gets added to the argument list for cpp. Then, in globaldefs.h, we have:
#if defined MPI
# define DISTRIBUTE
#endifThe rest of the code uses DISTRIBUTE to identify distributed memory jobs. The OpenMP case is more straightforward, with -D_OPENMP getting passed to cpp and _OPENMP being the tag to check within ROMS.
The whole horizontal ROMS grid is shown here:
The computations are done over the cells inside the darker line; the cells are numbered 1 to Lm in the $\xi$-direction and 1 to Mm in the $\eta$-direction. Those looking ahead to running in parallel would be wise to include factors of two in their choice of Lm and Mm. ROMS will run in parallel with any values of Lm and Mm, but the computations might not be load-balanced. </wikitex>
ROMS internal numbers
<wikitex> </wikitex>
Other figures
