7.4.1 Introduction

About

Installation

Tutorials

Documentation

1.1 Introduction

1.3 Continuous equations in `r' coordinates

2. Discretization and Algorithm

4. Software Architecture

5. Automatic Differentiation

6. Physical Parameterization and Packages

7. Diagnostics and tools

8. Interface with ECCO

Browse Code

PDF file (9Mb)

PS file (7Mb)

Next: 7.4.2 Using Monitor Up: 7.4 Monitor: Simulation state Previous: 7.4 Monitor: Simulation state Contents

7.4.1 Introduction

The monitor package is primarily intended as a convenient method for calculating and writing the following statistics:

minimum, maximum, mean, and standard deviation

for spatially distributed fields. By default, monitor output is sent to the ``standard output'' channel where it appears as ASCII text containing a %MON string such as this example:

     (PID.TID 0000.0001) %MON time_tsnumber      =                     3
     (PID.TID 0000.0001) %MON time_secondsf      =   3.6000000000000E+03
     (PID.TID 0000.0001) %MON dynstat_eta_max    =   1.0025466645951E-03
     (PID.TID 0000.0001) %MON dynstat_eta_min    =  -1.0008899950901E-03
     (PID.TID 0000.0001) %MON dynstat_eta_mean   =   2.1037438449350E-14
     (PID.TID 0000.0001) %MON dynstat_eta_sd     =   5.0985228723396E-04
     (PID.TID 0000.0001) %MON dynstat_eta_del2   =   3.5216706549525E-07
     (PID.TID 0000.0001) %MON dynstat_uvel_max   =   3.7594045977254E-05
     (PID.TID 0000.0001) %MON dynstat_uvel_min   =  -2.8264287531564E-05
     (PID.TID 0000.0001) %MON dynstat_uvel_mean  =   9.1369201945671E-06
     (PID.TID 0000.0001) %MON dynstat_uvel_sd    =   1.6868439193567E-05
     (PID.TID 0000.0001) %MON dynstat_uvel_del2  =   8.4315445301916E-08

The monitor text can be readily parsed by the testreport script to determine, somewhat crudely but quickly, how similar the output from two experiments are when run on different platforms or before/after code changes.

The monitor output can also be useful for quickly diagnosing practical problems such as CFL limitations, model progress (through iteration counts), and behavior within some packages that use it.

mitgcm-support@mitgcm.org

Last update 2011-01-09