1 / 17

FLUME Metadata

FLUME Metadata. Steve Mullerworth 3 rd -4 th October May 2006. What is FLUME? FLUME Metadata overview D C CD metadata manipulation Definitions and selections grids FLUME vs. Curator NMM. Introducing FLUME.

byuen
Download Presentation

FLUME Metadata

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. FLUME Metadata Steve Mullerworth 3rd-4th October May 2006

  2. What is FLUME? • FLUME Metadata overview • DCCD metadata manipulation • Definitions and selections • grids • FLUME vs. Curator NMM

  3. 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. FLUME Scope of 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

  5. 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

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

  7. 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. FLUME Metadata FUME grids include: • 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.)

  9. 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. FLUME FLUME vs. Curator NMM Either: • 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 Or:

  11. 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. Credits: Allyn Treshansky, Irina Linova-Pavlova, Mick Carter (Met Office) Graham Riley, Rupert Ford (Manchester University) The end

  13. configuration schema (I)

  14. configuration schema (II)

  15. composition schema

  16. deployment schema

  17. uninstantiated grid schema

More Related