1 / 19

Curator: Gap Analysis (from a schema perspective)

Curator: Gap Analysis (from a schema perspective). Rocky Dunlap Spencer Rugaber Georgia Tech. Deliverables. What do we want the outcome to be... At the end of this session today At the end of this year of Curator 3-5 years from now Let’s think in terms of tangible products.

benita
Download Presentation

Curator: Gap Analysis (from a schema perspective)

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. Curator: Gap Analysis (from a schema perspective) Rocky Dunlap Spencer Rugaber Georgia Tech

  2. Deliverables • What do we want the outcome to be... • At the end of this session today • At the end of this year of Curator • 3-5 years from now • Let’s think in terms of tangible products

  3. Expected outcomes from Curator one year from now • Schema side: • A coherent, upper-level metadata model for describing modeling components, configured and un-configured models, model-generated datasets, and other software resources such as modeling frameworks • But, what form does the product take? • Software side (CDP-Curator): • A prototype of an online repository of modeling resources, including a faceted search interface, download mechanism, and basic compatibility checking abilities

  4. Expected outcome at the end of this session

  5. Overview of Schemata • NMM Component • NMM Potential Model • NMM Model • Gridspec • Component Input and Output (CIAO) (was PMIOD) • NMM Application • Framework • ESG Ontology • FMS Runtime Environment (FRE) XML

  6. Other Schemata • NetCDF + CF • FLUME Metadata • PRISM Schemata • SMIOC (Specific Model Input Output Config.) • SCC • AD • Legacy Code Markup Language (LCML)

  7. Schemata Links • + Will be actively included in Curator • Will not be included as part of Curator • ? Extent of incorporation into Curator unknown

  8. NMM Component • Describes a single modeling component – not necessarily a complete or runnable model • Technical properties (compilers, platforms) • Scientific properties (parameterizations) • Numerical properties (grids, calendars) • Interface (coupling), inputs and outputs

  9. NMM Potential Model • Composition of NMM Components that could form an executable model, but is notconfigured • Basic info such as name, version, description, contact info, etc. • At its most basic level: just a list of component identifiers • Most “interesting” metadata still resides in NMM Component

  10. NMM Model • Describes a fully configured and executable model • Set of configured components (e.g., actual values used during a model run, or that could be used to perform a run) • Parameter settings, input files, output files, grid resolution • Pointer back to NMM Potential Model

  11. Gridspec • A standard description of the grids used to discretize model output • Proposal to add to CF • Mosaic made up of tiles • Tiles have properties: • Regularity • Uniformity • Coordinate system • Edges, vertices, angles, arc type • Exchange grid for moving data between grid tiles

  12. CIAO (Component Input and Output) • Describes coupling fields supported/used by a component • Basically: a list of fields, where each field has: • Local name, standard name • Units • Data type • I/O direction (Input, Output, In/Out) • Field dependencies

  13. NMM Application • “describe an application which ‘bins’ or ‘wraps’ several models into one, for example an ensemble” (NMM Website: http://ncas-cms.nerc.ac.uk/NMM/content/category/6/22/51/)

  14. Framework Schema • Description of a software framework used in Earth system modeling • Only basics: name, version, etc.

  15. Earth System Grid (ESG) Ontology • Class hierarchy used by ESG • Example classes: • Activity • ClimateModelExperiment, Ensemble, Simulation • Grid • LogicallyRectangular, PixelBased, Triangular, Unstruct. • ModelType • Atmopshere • Resource • Software, Dataset

  16. FMS Runtime Environment XML • XML configuration file used to assemble, compile, execute, and post-process an FMS model (used at GFDL) – workflow • Directory locations (CVS, output, temp) • Batch queues and commands • Experiment descriptions (regression tests, production runs, run lengths, number of processors, platforms) • Fortran namelists, parameter settings

  17. UML Package Diagram

  18. Conceptual Model of CDP-Curator RDF

More Related