Modular Earth Submodel System (MESSy)


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 ECHAM/MESSy Atmospheric Chemistry (EMAC) model is a numerical chemistry and climate simulation system that includes sub-models describing tropospheric and middle atmosphere processes and their interaction with oceans, land and human influences (Jöckel et al., 2006). It uses the first version of the Modular Earth Submodel System (MESSy1) to link multi-institutional computer codes. The core atmospheric model is the 5th generation European Centre Hamburg general circulation model (ECHAM5, Roeckner et al., 2006). For the present study we applied EMAC (ECHAM5 version 5.3.01, MESSy version 1.9) in the T42L90MA-resolution, i.e. with a spherical truncation of T42 (corresponding to a quadratic gaussian grid of approx. 2.8 by 2.8 degrees in latitude and longitude) with 90 vertical hybrid pressure levels up to 0.01 hPa. The applied model setup comprised the submodels ..." (other versions/resolutions as appropriate) followed by a list of submodels (with references, see MESSy Publications) with the following references
Througout the text and in your figures you can then use EMAC as abbreviation for "ECHAM/MESSy Atmospheric Chemistry model". 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.


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


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).


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.

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).

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.

model setup:

The model setup is the scope of model characteristics determined at run-time.
This page was last modified on 08 Jan 2010.
If you have comments or suggestions, e-mail me at  !