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 indicated in the section MESSy Citation Rules of the MESSy License description. 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.
Examples:

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).
Examples: The model version is only valid for code without modifications! In other cases it is a modified version.
In the case of a model system, each component may have its individual version number.

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:

model mode of operation:

A model mode of operation is a subset of the model setup (i.e., determined at run-time), which describes a specific characteristic that can be combined with other characteristics.
Examples:

BaseModel Layer (BML):

The Base Model Layer (BML) ultimately consists only of a central clock and run-time control, currently however, typically of a general circulation model (GCM) or a box model.

BaseModel Interface Layer (BMIL):

The Base Model Interface Layer (BMIL) comprises the basemodel specific implementation of the MESSy infrastructure; it can be regarded as a multiple socket outlet for the communication between the basemodel and the submodels.

SubModel Interface Layer (SMIL):

The submodel interface layer (SMIL) represents the connector of a specific process to the infrastructure (BMIL).

SubModel Core Layer (SMCL):

And last but not least, the submodel core layer (SMCL) comprises the basemodel independent implementation of a specific process in the Earth System, or of a diagnostic tool of the model system. It can be regarded as an operator using the data provided via its SMIL and providing data back via its SMIL to other submodels and/or the basemodel.
This page was last modified on 30 Jul 2015.
If you have comments or suggestions, e-mail me at Patrick.Joeckel@dlr.de  !