24 |
the steps below: |
the steps below: |
25 |
|
|
26 |
1. Extract MITgcmUV from the downloadable archive |
1. Extract MITgcmUV from the downloadable archive |
27 |
tar -xvf checkpoint12.tar |
tar -xvf cNN.tar |
28 |
|
|
29 |
2. Create platform specific make file |
2. Create platform specific make file |
30 |
For example on a Digital UNIX machine the script "genmake.dec" can |
For example on a Digital UNIX machine the script "genmake" can |
31 |
be used as shown below |
be used as shown below |
32 |
|
|
33 |
cd bin |
cd bin |
40 |
4. Compile code |
4. Compile code |
41 |
make |
make |
42 |
|
|
43 |
5. Copy input files |
5. To run the model with example data see the "README" in each of |
44 |
cp ../verification/exp2/[a-z]* ../verification/exp2/*bin . |
the example experiments in ../verification/exp*/ |
45 |
|
e.g. ../verification/exp2/README |
46 |
|
|
|
6. Run baseline test case |
|
|
setenv PARALLEL 1 |
|
|
dmpirun -np 2 ../exe/mitgcmuv ( Under Digital UNIX ) |
|
|
mpirun.p4shmem ../exe/mitgcmuv -np 2 ( Under Solaris + mpich) |
|
|
|
|
|
|
|
|
This runs a 4 degree global ocean climatological simulation. |
|
|
By default this code is set to use two porcessors splitting |
|
|
the model domain along the equator. Textual output is written |
|
|
to files STDOUT.* and STDERR.* with one file for each process. |
|
|
Model fileds are written to files suffixed .data and .meta |
|
|
These files are written on a per process basis. The .meta |
|
|
file indicates the location and shape of the subdomain in |
|
|
each .data file. |
|
47 |
|
|
48 |
o Running |
o Running |
49 |
|
|
60 |
|
|
61 |
- Serial execution |
- Serial execution |
62 |
|
|
63 |
|
- Parallel execution. MPI |
64 |
|
mPx, nPy |
65 |
|
dmpirun |
66 |
|
|
67 |
- Parallel execution. Threads |
- Parallel execution. Threads |
68 |
nSx, nSy |
nSx, nSy |
69 |
setenv PARALLEL n |
setenv PARALLEL n |
70 |
nTx=2, nTy=2 |
nTx=2, nTy=2 |
71 |
|
|
|
- Parallel execution. MPI |
|
|
mPx, nPy |
|
|
dmpirun |
|
|
|
|
72 |
- Parallel execution. Hybrid |
- Parallel execution. Hybrid |
73 |
|
|
74 |
|
o Cutomising the code |
75 |
|
|
76 |
|
Model structure |
77 |
|
=============== |
78 |
|
The "numerical" model is contained within a execution |
79 |
|
environment support wrapper. This wrapper is designed |
80 |
|
to provide a general framework for grid-point models. |
81 |
|
MITgcmUV is a specific numerical model that uses the |
82 |
|
framework. |
83 |
|
Under this structure the model is split into |
84 |
|
execution environment support code and conventional |
85 |
|
numerical model code. The execution environment |
86 |
|
support code is held under the "eesupp" directory. |
87 |
|
The grid point model code is held under the |
88 |
|
"model" directory. |
89 |
|
Code execution actually starts in the eesupp |
90 |
|
routines and not in the model routines. For this |
91 |
|
reason the top level main.F is in the eesupp/src |
92 |
|
directory. End-users should not need to worry about |
93 |
|
this level. The top-level routine for the numerical |
94 |
|
part of the code is in model/src/the_model_main.F. |
95 |
|
|
96 |
|
|
97 |
o References |
o References |
98 |
Web sites - HP |
Web sites - HP |
99 |
for doc Digital |
for doc Digital |