page 1© crown copyright 2004 flume metadata steve mullerworth 3 rd -4 th october may 2006

© Crown copyright 2004

FLUME Metadata

Steve Mullerworth

3rd-4th October May 2006


• What is FLUME?

• FLUME Metadata overview

• DCCD metadata manipulation

• Definitions and selections

• grids

• FLUME vs. Curator NMM


Introducing FLUME

The Flexible Unified Modelling Environment is a project to replace the Unified Model system

More Flexible Modelling components can be added with fewer constraints on how they are

developed

Coupling fields more easily changed

Flexible control of time step lengths and orders

More choices about running models sequentially or concurrently Remains a Unified Model. Great scientific benefits of a single “modelling”

system at the Met Office. A model good at climate and weather forecasting gains from the focus of both

development groups

There are constraints with regard to maintaining operational performance Is an Environment. Not a model, but an environment


FLUME

• FLUME models – now called components

• coupling framework, including adapters to external technologies such as PRISM

• user interface

• code generation

• metadata to tie everything together

Scope of FLUME


Meta-data and DcCD

DcCD. Definition, Configuration, Composition, Deployment: Definition: For a model to exist in FLUME, its interface needs

to be defined. Configuration: Some models’ interfaces are dependent on

user choices about their configuration switches. Composition: The user connects the inputs each model

requires to outputs from another – including transformers if required.

Deployment: The description of the composition is mapped onto executable code for specific hardware platforms communicating through specific protocols.

Information about each stage is captured by meta-data

types of FLUME Metadata

machines data grids

resources

roles groups users

administration

“models”

scientific models

transformer models

diagnostic models

composite models

configuration

composition

deployment

modified during definition

grids

modified during configuration

modified during composition

modified during deployment

definitions selections

nonspecific information

model-specific information

job-specific information

constraints


Status of FLUME metadata

Schema covering model definition, configuration and composition broadly complete.proof of concept conversion to PRISM metadata,

and creation of PRISM code donePrototype generation of control code for running

FLUME models implementedSolution beginning to align itself with BFG2 schema

developed at Manchester University


FLUME Metadata

• uninstantiated grids• a high-level generic schema that contains standard names, question / answer pairs, and a reference to a grid instantiator – including the specific member grids that it can produce (even though specific details about those grids cannot be known prior to instantiating the grid)

• grid instantiators• an algorithm written for a particular instance of a grid; takes the pre-instantiated grid answers as input and returns (a set of) instantiated grid(s) as output

• instantiated grids• a “complete” description of a specific grid capable of being incorporated into job code (for FLUME, PRISM, ESMF, etc.)

FUME grids include:


FLUME

FLUME & grids

• how grid information might flow through flume:

• configured grid data is used as data by a configured component; this data is passed directly to the component code (as subroutine arguments, for instance)

• algorithm instantiates the grid (into a gridspec) and the FLUME Framework reads that information directly (and uses it for coupling, for instance)


FLUME

• FLUME & Curator NMM compatible (same aims, similar methods)

• Pro: It will be easy to import/export components from one system to the other.

• Con: There will be 2 standards doing the same thing.

• FLUME & Curator NMM are incompatible (different aims & dissimilar methods)

• Pro: It is appropriate to have 2 standards if they are each doing something unique

• Con: It will be difficult – though still necessary for IPCC, etc. – to convert from one system to another

FLUME vs. Curator NMMEither:

Or:


FLUME vs. Curator NMM

We think:FLUME has more focus on technical information

required to build and run a job. Eg.Configurable model inputs have data types, units,

constraints.Detailed time-stepping info – coupling rates, lags.

Curator NMM currently focused on describing provenance of data from a range of models. ie.DescriptionsNo detailed typing of configurable valuesAlso, no detailed coupling information. Just a

reference to a PMIOD.


The end

Credits: Allyn Treshansky, Irina Linova-Pavlova, Mick Carter (Met Office)

Graham Riley, Rupert Ford (Manchester University)


configuration schema (I)


configuration schema (II)


composition schema


deployment schema


uninstantiated grid schema

page 1© crown copyright 2004 flume metadata steve mullerworth 3 rd -4 th october may 2006

Documents