This page is devoted to describing the SimDB data model (SimDB/DM from now on).

TODO

• OK on approach?
  • analysis(conceptual)->logical->physical
  • TAP+XML
• Identify main issues of model
  • sufficiently detailed resources?
  • characterisation
  • normalisation (problem for XML, little for TAP)
  • "queriability" (problem for TAP)
  • missing semantic vocabularies
  • quantities/units
• Clean up
  • documentation in the UML
  • Description of model in Note
• finalise the serialisation to TAP
  • which OR mapping approaches
• finalise the serialisation to XML schema
  • multiple packages
  • identifiers
• reuseby other specs
  • SimDAP
  • S3

Some scattered notes and remarks

for historical purposes

Current model

As described here all development can be followed on Volute. Particularly relevant for the discussion on this page is the data model in uml/SimDB_DM.xml. The previous versions as well as later working versions can be found in the history of this file, as well as its direct predecessor version r902.

see also It is meant to reflect the proposal and incorporate conclusions from the discussions page.

Examples of Protocols

For discussion purposes it will be good to have a list of real protocols, i.e. simulation and post-processing codes and algorithms.

Examples of protocols:

Simulators:

• Gadget (http://www.mpa-garching.mpg.de/gadget/)
• Enzo ...
• Flash ...
• Nemo ...
• Ramses ...
• L-Galaxies (MPA semi-analytical (SAM) galaxy formation code)
• GalForm (Durham SAM code)
• GalICS (Horizon SAM)
• ...

Pure post-processors: cluster finders

• FOF cluster finders (various implementations)
• SUBFIND cluster finder (Springel etal 2001, ADS)
• ...

others