As mentioned previously, there are four printout files corresponding to four test cases which were executed at GFDL on a CRAY T90. Results from CASE=0 are in file EXP/TEST_CASE/printout.0.gfdl, from CASE=1 are in file EXP/TEST_CASE/printout.1.gfdl, and so forth. These cases are not intended to be scientifically meaningful. Rather they are included as examples of how to use various types of surface boundary conditions and provide a means of checking that MOM is behaving as intended. The following is a brief tour of file printout.0.gfdl.
File EXP/TEST_CASE/printout.0.gfdl begins by listing various surface boundary condition names and units followed by the version number of MOM and the values of namelist variables. If any variable was not included in the run_mom script namelist section, then it retains its initialized value. Otherwise, the new value is given. Immediately below, there is the file sizes in megawords needed for two dimensional fields (kflds) and the three dimensional fields (latdisk1 and latdisk2) where the latitude rows reside. If option ramdisk is enabled, these files are actually stored in memory but behave as if stored on disk.
Next, there is output from the grids module detailing everything relevant to grid cells. All this is summarized by a checksum which is essentially a sum over all grid cell information. Following this is a summary of temperature and salinity ranges used to compute density coefficients and a checksum of the coefficients3.12. Afterwards, output from the topography module topog supplies information about the kmti,jrow field. Changes to the kmti,jrow field are best done in a stand alone mode using script run_topog. Checking for violations is done iteratively so this section rambles on for awhile. If everything is as it should be then some basic statistics relating to geometry and topography are given with a map of land masses and island perimeters followed by a map of kmti,jrow . Along with these maps is information on how to suppress their printing since they can take up lots of space. The section finishes with a checksum for the topography and geometry.
After constructing a checksum over initial conditions, various initializations are indicated. The time manager module tmngr gives details on the calendar and time at initial conditions as well as information on the reference time for diagnostic switches. This is followed by information on damping surface tracers back to data which is given when option restorst is enabled.
Since the test case is of global extent, filtering of latitude rows is enabled (by option fourfil or firfil) and information is given as to which latitudes are filtered and by how much. Refer to Chapter 27 for a discussion of filtering.
Next comes some statistics on regions which have been arbitrarily set for diagnostic purposes along with a map detailing where the regions are. A detailed listing of filtering indices is suppressed but may be switched on as indicated in the printout. The time step multipliers are all set to unity indicating that there is no timestep acceleration with depth.
If option time_averages has been enabled, information on the grid over which data will be time averaged is given and if option save_xbts is enabled, the XBT station locations are given. Depending on enabled options, other initializations may give output here after which a general consistency check is done involving all enabled options. Two levels of messages are given: error and warning checks. After all messages are listed, if one or more error messages is present the model will stop. Warning messages will not stop the model, but the researcher should be aware of them and convinced they are harmless before continuing.
The preliminary setup finishes with a summary of enabled options after which a breakdown of the number of time steps per ocean segment and number of segments per integration is given. This is of interest only when option coupled is enabled.
A heavy battery of diagnostics are enabled but only for illustrative purposes. They are fully described in Chapter 38 and the I/O control variables are set to save data to unformatted files with suffix .dta as well as formatted to the printout file. At the end of the integration, all files are listed and a timing analysis is given detailing times taken by various sections of MOM. This is useful but once the information is digested, the timing should be turned off by not enabling option timing.
The other printout files are very similar except for case #3 which has more output because option trace_coupled_fluxes has been enabled to show details of surface boundary conditions as they are being interpolated from ocean to atmosphere and visa versa.