1. Page 1© Crown copyright 2004 FLUME Metadata Steve Mullerworth 3 rd -4 th October May 2006

2. Page 2© Crown copyright 2004 What is FLUME? FLUME Metadata overview D C CD metadata manipulation Definitions and selections grids FLUME vs. Curator NMM

3. Page 3© Crown copyright 2004 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

4. Page 4© Crown copyright 2004 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

5. Page 5© Crown copyright 2004 Meta-data and D c CD  D c CD. 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

6. types of FLUME Metadata machines data grids resources roles groups users administration “models” scientific modelstransformer modelsdiagnostic modelscomposite models configurationcompositiondeployment modified during definition grids modified during configuration modified during composition modified during deployment definitions selections nonspecific information model-specific information job-specific information constraints

7. Page 7© Crown copyright 2004 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 done  Prototype generation of control code for running FLUME models implemented  Solution beginning to align itself with BFG2 schema developed at Manchester University

8. Page 8© Crown copyright 2004 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:

9. Page 9© Crown copyright 2004 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)

10. Page 10© Crown copyright 2004 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 NMM Either: Or:

11. Page 11© Crown copyright 2004 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.  Descriptions  No detailed typing of configurable values  Also, no detailed coupling information. Just a reference to a PMIOD.

12. Page 12© Crown copyright 2004 The end Credits: Allyn Treshansky, Irina Linova-Pavlova, Mick Carter (Met Office) Graham Riley, Rupert Ford (Manchester University)

13. Page 13© Crown copyright 2004 configuration schema (I)

14. Page 14© Crown copyright 2004 configuration schema (II)

15. Page 15© Crown copyright 2004 composition schema

16. Page 16© Crown copyright 2004 deployment schema

17. Page 17© Crown copyright 2004 uninstantiated grid schema