Work in progress!!!

Global physics fields

As you hopefully already know, GEM can run in parallel, using MPI and/or OpenMP. In the physics, when using MPI, the model domain gets horizontally divided into tiles, or rather cubes. Each MPI process is taking care of one of these cubes.

However, the physics do not see the whole "cube" at once but they are called for one "slab" (ni*nk) at the time. With ni being the number of points in x-direction of the particular tile and nk being the number of vertical levels, which can be atmospheric model levels, soil or ice levels or even "levels" for the different surface fractions.

Busses

Physics fields, that are used in different routines and also available for output, are organized in so called "busses". These busses are very veeeeery long 2-D arrays, filled with one field after the other. For each field there is one row per level, followed by the next field. The starting location of each field in a bus is defined in a variable.

There are 5 of these busses in the physics:

• entry bus (contains initial conditions - almost not used anymore in GEM5)
• dynamic bus (contains fields which get passed from and to the dynamics)
• volatile bus (contains physics fields of which the content is not needed to calculate the next timestep)
• permanent bus (contains physics fields of which the content is needed to calculate the next timestep)
• surface bus (contains only physics fields used by the surface schemes)

All fields that are in a bus need to get declared with the command "PHYVARnCx".

The syntax is:

Where :
    'n' is the "real" dimension of the field which can be:  2 (ni*nj), 3 (ni*nj*nk), or 4.
    'name' is the "name" by which the field can get addressed in the physics. This variable is actually an integer which contains the starting position of the field in the bus.
    'description' is a string containing a set of key words followed by a name, description or value. The different keys are separated by a semicolon ';'. These are the accepted keys:

    'condition' is the condition under which the field should get declared. For example, certain fields are only needed when certain schemes are used. So they only need to get declared when the respective scheme is used. Otherwise they should not get declared so they do not use memory space unnecessarily and do not get written in the restart files.

Entry and dynamic bus

As mentioned above, the entry bus is almost not used anymore.
If possible, do not add fields to the dynamic bus as this gets quite complicated.
For both, variables need to get declared in rpnphy/base/phyvar.hf. Variables from the entry bus need to get declared as "VB=e1", fields from the dynamic bus as "VB=d1".

Volatile and permanent bus

All physics fields that are NOT needed to calculate the next timestep should go in the volatile bus. These are, for example, precipitation rates or instantaneous radiation. However, their accumulators need to be in the permanent bus, since they usually get accumulated over several timesteps. The same goes for averages, minimum and maximum fields. But there are also instantaneous fields that need to be in the permanent but like snow depth or temperature fields, because they are needed for the next timestep.

Surface bus

If variable is in the rest of the physics
    base/phyvar.hf : variable declaration in physics bus
    surface/sfcbus_mod.F90 : copy variable from physics bus to surface bus
        SFCVAR(name_in_surface_bus, 'name_in_physics_bus')

Explain what a bus is: slab with just land points etc.

in class_main:
    declare variable as pointer with the correct dimension (1-D)
        all usually 2-D fields are 1-D because we only get one row
        all usually 3-D fields are 2-D because we only get one slab