Modular Earth Submodel System (MESSy)

Glossary


To make results reproducible and traceable, we kindly ask you to refer to the model system at least once in the text of each of your papers, presentations, proposals etc. as: " ... the atmospheric chemistry general circulation model ECHAM5/MESSy (version 1.5) ... in the T42L90MA resolution ... " or for other applied resolutions, (e.g. T31L29MA, T42L31ECMWF, T42L41DLR, etc.), as appropriate. You can then abbreviate it further for usage in figures, tables, etc., as " ... further denoted as E5/M1 ..." Some more suggestions for wording in publications, proposals, presentations, etc. can be found below.

model system:

A model system is a set of different models sharing the same infrastructure.
Example: ECHAM5/MESSy including the box-models and tools.

model:

A model is represented by one executable.
Examples: ECHAM5/MESSy (echam5.exe), the MECCA box-model (mecca.exe), ...

submodel:

A submodel is the implementation of one process according to the MESSy coding standard, i.e., split into the submodel core layer (SMCL) Fortran 90 module(s) and the submodel interface layer (SMIL) Fortran 90 module(s).

box-model:

A box-model represents one process in its smallest meaningful entity (e.g. box (0-D), or vertical column (1-D)) as a stand-alone executable.

model distribution:

A set of files representing a model or model system, usually archived as zip- or tar-file.
Example: echam5.3.01_messy_1.4_src.zip

model version:

The model version is indicated by the version-number(s) of the model distribution; and is also contained in the code and output to log-file(s).
Example: echam5.3.01_messy_1.4_src.zip
Notes:

submodel version:

The submodel version is indicated by the version number in the submodel core layer (SMCL) file of the submodel.
Example: CHARACTER(LEN=*), PARAMETER :: modver = '1.1.3b'

model configuration:

The model configuration is the scope of model characteristics selected at configuration-time or at compile-time, which cannot be changed during run-time, but which do not require manual code changes.
Examples:

model setup:

The model setup is the scope of model characteristics determined at run-time.
Examples:
This page was last modified on 14 Dec 2007.
If you have comments or suggestions, e-mail me at joeckel@mpch-mainz.mpg.de  !