1 / 25

Eric Guilyardi and the Metafor team

Common Meta data for Climate Modelling Digital Repositories. Eric Guilyardi and the Metafor team. Metafor Dissemination Workshop Abingdon, 14 March 2011. Outline. Why Metafor Metafor goals How we are doing it What we have done Common Information Model (CIM) Controlled vocabulary

nell-morse
Download Presentation

Eric Guilyardi and the Metafor team

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. Common Metadata for Climate Modelling Digital Repositories Eric Guilyardi and the Metafor team Metafor Dissemination Workshop Abingdon, 14 March 2011

  2. Outline • Why Metafor • Metafor goals • How we are doing it • What we have done • Common Information Model (CIM) • Controlled vocabulary • CMIP5 support and questionnaire • Next steps

  3. Why Metafor Current issues (before Metafor): • Finding climate model data is hard • Understanding data is harder (esp. for non-experts) • Discriminating between two simulations/models is not easy • Documentation is “patchy” and specific to modelling centres • Documentation currently revolves around (at best) the runtime, but not the scientific detail and relevance of the model components • Little or no documentation of the “simulation context”, i.e. the whys and wherefores and issues associated with any particular simulation.

  4. Why Metafor Example: the CMIP5 documentation challenge • 20 modelling centres • 40+ models • 60 numerical experiments • 90,000 years of simulation • 2 million output datasets • Data to be available from “core-nodes” and “modelling-nodes” in a global federation (PetaBytes of data). • Users need to find datasets, and discriminate between models, and between simulation characteristics.

  5. Discovery, Documentation, Definition Why Metafor

  6. CF-NETCDF Metafor-CIM IS-ENES Metrics GEOSS Journal Paper Why Metafor Discovery, Documentation, Definition & examples

  7. Why Metafor “The main objective of Metafor is to develop a Common Information Model (CIM) to describe climate data and the models that produce it in a standard way, and to ensure the wide adoption of the CIM” • Requirements for success: • • Gather top field experts • • Engage with similar existing activities • • Work towards community adoption • • Capture wider community needs • • Ensure post-project governance

  8. Facts and Figures INFRA-2007-1.2.1 Scientific Digital Repositories 12 partners EU contribution of 2.2M€ Started March 2008, duration 3.5 years • NCAS, University of Reading, UK (Coordinator) • BADC, Science and Technology Facilities Council, UK • CERFACS, France • Models and Data, Max Planck Institute for Meteorology, Germany • Institute Pierre-Simon Laplace, CNRS, France • University of Manchester, UK • Met Office, UK • Administratia Nationala de Meterologie, Romania • Météo France, CNRM, France • CLIMPACT, France • CICS, Princeton University, USA • University of Cantabria, Spain

  9. METAFOR Year 1 meeting in Abingdon Feb. 2009

  10. IS-ENES IS-ENES, Metafor IS-ENES Metafor IS-ENES ENES coordination Where Metafor came from • PRISM project (FP5 2001-2004), ENES • PRISM Sustained Initiative (PSI) • Code coupling and I/O • Integration and modelling environments • Data processing and management • Meta-data standards (key !) • Computing issues

  11. Metafor organisation Metaforactivities and work packages (WP) map onto the I3 structure. Project management, training and dissemination are organised in WP1 and WP7.

  12. TheCIM • the CIM builds on existing metadata standards used internationally in climate research (CF, NMM, Curator, FLUME, ISO-standards, etc.) + new bits • the CIM defines a general structure over which a specific Controlled Vocabulary (CV) can be applied • a CV consists of the terms (and their relationships) used to build the content of CIM instances.

  13. The CIM “metamodel” • Lots of people talk about climate models and data; • Some people even agree about those things (“the yolk”); • We have a formal way of describing that (UML, CONCIM); • That UML is constrained to follow a particular meta-model... • ...so that it can be transformed into something usable (XSD, APPCIM) for particular users; • Metadata instances conform to an APPCIM

  14. The CONCIM Climate Modelling = an activity using a software to produce data on a grid to be archived in a repository.

  15. The CONCIM Grid Software Data CIM v 1.4 available on the Metafor website at: http://metaforclimate.eu/trac/browser/CIM Activity

  16. The CONCIM to APPCIM UML Conceptual Model Climate Modelling = an activity using a software to produce data on a grid to be archived in a repository. e.g. CIM XSD Application Model Application Model e.g. CMIP5 RDF XML Instance @ BADC An essential aim of Metaforis that the conceptual model is not changed by the manner in which it is used or applied. Instance @ IPSL Instance @ PCMDI More in Allyn’s presentation

  17. The Query and other CIM Tool(s) • building a search interface for CIM instances • building a CIM instance viewer • building a CIM instance comparer More in Mark’s presentation

  18. Using the CIM to support CMIP5 • The CMIP5 experimental archives will be ~500TB of model run data • We need to be able to capture all the details of these experiments (and the component models and platforms used) to allow users of the archive to differentiate between the experiments and the models. • To do this, Metafor has been tasked by WGCM/CMIP to define, collect and provide the CMIP5 model metadata.

  19. Controlled Vocabulary Novelty in community: Software CV Creating the CV mindmap Gathering a way of describing (in a community consistent way) the scientific properties of model subcomponents 570 controlled questions - hundred of choices !

  20. Ocean Lateral physics CV More in Sébastien’s presentation

  21. CMIP5 metadata collection CMIP5 Questionnaire @BADC More in Gerry’s presentation

  22. ESG Federation Architecturefor CMIP5

  23. How it all fits together Creating the CV mindmap CMIP5 Questionnaire @BADC Portals for user access (search & other tools) CIM+DOI database User perspective and access to data via ESGF

  24. Upcoming challenges • CMIP5 questionnaire support • Deployed since November 2010 • Growing use (20 groups) • Feedback on CIM concepts • Provide first CIM tools and services (WP4/5/6) • Articulate developments with IS-ENES and ESG • Community outreach and buy-in • Develop CIM for other uses (Charlotte’s presentation) • Set up long-term governance for CIM and CV • “standards committee” under WCRP

  25. A few quotes... “The open standard developed in Metafor will play a catalytic role in the way next generation climate data repositories, such as IPCC AR5, are organised, preserved and accessed” - METAFOR project proposal “METAFOR is now a major international focal point for earth system modelling metadata definition” - Karl Taylor, PCMDI “There is evidence of excellent teamwork” - EU review “The right people for the right project at the right time !” More on: http://metaforclimate.eu

More Related