Version 6 (modified by lawrence, 14 years ago) (diff)


Numerical Simulation Discovery Metadata (aka NumSim)

Please note this page is changing rapidly as of early March, as we migrate the old tasks into trac

The DIF? describes datasets at the discovery level, but where simulations are involved, discovery metadata needs more information than is available in the existing schema.

A new schema which is being trialled at the British Atmospheric Data Centre can be found here. The proposed schema should be accessible to both DIF? and ISO19115? parent discovery schema (as it evolves), although at the moment it's rather standalone.

The schema is documented in a pdf file which you can download from here. See also example files: HadCM3 Beowulf 500 year run

Comments are welcome! Please note that this version has only just started to be trialled with data, so some changes are inevitable as described below.

You can either annotate this page, or join the mailing list at (mail the list at climate-model-doc@…). Or email bryan lawrence directly.


Two sets of email feedback on V005 have been received, and are documented on the NumSimFeedback page, and V006 is now the current release.

More responses welcome.

Technical Issues



Planned Changes

Tasks for milestone releases are listed below by milestone. However, note that not all the tickets listed below will definitely be done, you should look at the ticket status to be sure of what we currently are confirmed to do for each milestone.


Get latest NumSim code into SVN
Standardise Reference Format within NumSim
Change model related element to indicate nature of relationship
Should we use AnyURI without date qualification?
Need a script to format NumSim documents as XHTML.
Need a placeholder for model resolution
Decide on syntax of xml schema sequences
References for initial conditions
Model Component subtyping
Forecast and Analysis descriptions required in NumSim
[WG] [M] Numsim schema needed for NOCS MOLES

NumSim related tasks against other NDG major milestones

No results

Other Issues

Generally these are things that might be issues, that are not raised as tickets against any milestone (yet).

  1. Following response 2.3. Given that model has another understanding, in for example, geology, should we use a different word for model, e.g.: simulator?
  2. Should we suck any pages we link to down into the archive as copies? (This is a curation issue).
  • (Maybe) Follow up on Response 1.2, and consider whether ModelComponents such as "Atmosphere" need to be complex types, so that the software searching can distinguish between hydrostatic/non-hydrostatic and wet/dry, for example.
  • (Discussion) Should we have the initial conditions as attributes (subelements) of the Model rather than as attributes of the simulation. This would help in some regards, but might break the future ability to inherit model descriptions ... Note that Response 2.4 is unkeen on this.
    • How would we handle ensembles? For example, one could hold the entire SRESA2 ensemble, or an ensemble member. What discovery records should exist in the first case? What should the response to a search be?
      • Imagine a three member ensemble, should there be four records? At what point does the user see four? First response should be one surely?
      • Note that as it stands we need to make clear that an ensemble record which includes multiple initial condition members does not need repeated initial condition elements for each ensemble member. (There is an impossible sentence at the bottom of the simulated description that could be improved a lot to make this clearer).
  • (Discussion) We could support individual members of the climate prediction ensembles by adding to the model element an optional <perturbed> element which could be a list made up of arg param pairs. These would appear in ensemble member descriptions but not in grand ensemble descriptions. The usual issue of what level in the D heirarchy should be exposed to the wider world will arise.
  • (Probable) Conform to ISO19115 extension mechanism *


  • (Probable)  Earley Suite Convergence. What we want to be able to do is generate NumSim entries from Earley Suite descriptions. This may involve some interesting ontological jumps :-)
  • (Discuss)