Climate forcing

PISM has a well-defined separation of climate forcing from ice dynamics. This manual is about the climate forcing interface.

By contrast, most options documented in the PISM User’s Manual control the ice dynamics part. The User’s Manual does, however, give an overview of PISM’s surface (atmosphere) and ocean (sub-shelf) interfaces. At these interfaces the surface mass and energy balances are determined and/or passed to the ice dynamics code.

To get started with climate forcing usage we need to introduce some language to describe parts of PISM. In this manual a component is a piece of PISM code, usually a C++ class. A combination of components (or, in some cases, one component) makes up a “model” — an implementation of a physical/mathematical description of a system.

PISM’s climate forcing code has two kinds of components.

Model components and modifiers can be chained as shown in Fig. 16. For example,

-ocean constant,delta_T -ocean_delta_T_file

combines the component providing constant (both in space and time) ocean boundary conditions with a modifier that applies scalar temperature offsets. This combination one of the many ocean models that can be chosen using components as building blocks.

Section Examples and corresponding options gives examples of combining components to choose models. Before that we address how PISM handles model time (Section Managing model time).

Summary of the main idea in using this manual

Setting up PISM’s climate interface requires selecting one surface and one ocean component. The surface component may use an atmosphere component also; see Fig. 16. Command-line options -atmosphere, -surface and -ocean each take a comma-separated list of keywords as an argument; the first keyword has to correspond to a model component, the rest can be “modifier” components. Any of these options can be omitted to use the default atmosphere, surface or ocean model components, but one has to explicitly choose a model component to use a modifier. Model components and modifiers are chained as in Fig. 16.

Previous Next