 |
 |
 |
||||||||||
 |
|
|||||||||||
 |
 |
 |
||||||||||
Next: 3.5.2 Looking at the Up: 3.5 Running MITgcm Previous: 3.5 Running MITgcm Contents Subsections 3.5.1 Output filesThe model produces various output files and, when using mnc, sometimes even directories. Depending upon the I/O package(s) selected at compile time (either mdsio or mnc or both as determined by code/packages.conf) and the run-time flags set (in input/data.pkg), the following output may appear.
3.5.1.1 MDSIO output filesThe ``traditional'' output files are generated by the mdsio package. At a minimum, the instantaneous ``state'' of the model is written out, which is made of the following files:
The chain 00000nIter consists of ten figures that specify the iteration number at which the output is written out. For example, U.0000000300 is the zonal velocity at iteration 300. In addition, a ``pickup'' or ``checkpoint'' file called:
is written out. This file represents the state of the model in a condensed form and is used for restarting the integration. If the C-D scheme is used, there is an additional ``pickup'' file:
containing the D-grid velocity data and that has to be written out as well in order to restart the integration. Rolling checkpoint files are the same as the pickup files but are named differently. Their name contain the chain ckptA or ckptB instead of 00000nIter. They can be used to restart the model but are overwritten every other time they are output to save disk space during long integrations.
3.5.1.2 MNC output filesUnlike the mdsio output, the mnc-generated output is usually (though not necessarily) placed within a subdirectory with a name such as mnc_test_$DATE_$SEQ.
Next: 3.5.2 Looking at the Up: 3.5 Running MITgcm Previous: 3.5 Running MITgcm Contents mitgcm-support@mitgcm.org
|
||||||
, atmosphere:
).
