This page documents one possible approach to using O&M in metafor. It consists of two options. A first step, and then a revised step.

These options do not admit the concept of ISO19115-2 ... it remains to be seen whether it would be better or worse to do so.

Initial Step

Just specialise O&M in the simplest way, and map some of the other things using a "sympathetic approach" informed by experience with the questionnaire.

Proposed Activity Package (first step)

Proposed Software Package (first step)

Revised Step

Try and get the model configuratoin in the observation, rather than in the process, allowing the process to be reused.

Proposed Activity Package (revision)

Proposed Software Package (revision)

Disadvantages of this approach?

  • Simulation is the running of a configured model. We've blurred that. How could we find multiple simulations aparrt from via ensemble?
  • Connection to ISO19115 part 2? Where is the process step concept?
  • what would post processing look like?


A simulation uses a "configured model" which has been scientifically "configured" from a number of software options which embody an "unconfigured model" (which might have a default).

An unconfigured model has a set of scientific options which need to be set to turn it into a configured model. These options can be provided in a number of ways (runtime, ifdefs etc).

From a component point of view:

  • a component is a data processor (in and out)
  • it has an configuration/initialisation step (either via ifdefs or via a namelist)
  • it also has initialisation (in the reading data sense, but we can think of that as part of the data in/out)