/[volute]/trunk/projects/theory/snapdm/xsd/simdb/protocol.xsd
ViewVC logotype

Contents of /trunk/projects/theory/snapdm/xsd/simdb/protocol.xsd

Parent Directory Parent Directory | Revision Log Revision Log


Revision 633 - (show annotations)
Thu Jun 26 16:53:56 2008 UTC (12 years, 5 months ago) by bourges.laurent
File size: 12316 byte(s)
updated cardinalities (required / optional UML attributes)
1 <?xml version="1.0" encoding="UTF-8"?>
2 <xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema"
3 xmlns="http://www.ivoa.net/xml/SNAP/v0.1/simdb/protocol"
4 xmlns:base="http://www.ivoa.net/xml/dm/base/v0.1"
5 xmlns:p5="http://www.ivoa.net/xml/SNAP/v0.1/simdb"
6 xmlns:p6="http://www.ivoa.net/xml/SNAP/v0.1/simdb/object"
7 targetNamespace="http://www.ivoa.net/xml/SNAP/v0.1/simdb/protocol">
8 <xsd:annotation>
9 <xsd:documentation>Generated from UML-&gt;XMI-&gt;intermediate-&gt;XSD.</xsd:documentation>
10 </xsd:annotation>
11 <xsd:import namespace="http://www.ivoa.net/xml/SNAP/v0.1/simdb"
12 schemaLocation="http://volute.googlecode.com/svn/trunk/projects/theory/snapdm/xsd/simdb.xsd"/>
13 <xsd:import namespace="http://www.ivoa.net/xml/SNAP/v0.1/simdb/object"
14 schemaLocation="http://volute.googlecode.com/svn/trunk/projects/theory/snapdm/xsd/simdb/object.xsd"/>
15 <xsd:import namespace="http://www.ivoa.net/xml/dm/base/v0.1"
16 schemaLocation="http://volute.googlecode.com/svn/trunk/projects/theory/snapdm/xsd/base.xsd"/>
17 <xsd:complexType name="Physics">
18 <xsd:annotation>
19 <xsd:documentation>This class represents physical processes that are taken into account by a simulation. These may correspond to equations of motion evolving the simulated system from one state to the next, but also specifications of parameters describing initial conditions belong her.</xsd:documentation>
20 <xsd:appinfo>xmiid=_12_1_8e0028f_1173262198953_752563_1200</xsd:appinfo>
21 </xsd:annotation>
22 <xsd:complexContent>
23 <xsd:extension base="base:MetadataObject">
24 <xsd:sequence>
25 <xsd:element name="name" type="xsd:string"/>
26 <xsd:element name="description" type="xsd:string" minOccurs="0"/>
27 <xsd:element name="texForm" type="xsd:string" minOccurs="0"/>
28 <xsd:element name="physicslabel" type="xsd:string" minOccurs="0"/>
29 </xsd:sequence>
30 </xsd:extension>
31 </xsd:complexContent>
32 </xsd:complexType>
33
34 <xsd:complexType name="Simulator">
35 <xsd:annotation>
36 <xsd:documentation>This class represents the simulation software that is available to run a simulation.
37 We do not prescribe this model in great detail here [TBD should we?]. We only add the collection of physical processes that are available.
38
39 TODO one might argue we need a separate collection of numerical algorithms that implement the physical processes.
40
41 </xsd:documentation>
42 <xsd:appinfo>xmiid=_12_1_8e0028f_1173260371343_174540_519</xsd:appinfo>
43 </xsd:annotation>
44 <xsd:complexContent>
45 <xsd:extension base="Protocol">
46 <xsd:sequence>
47 <xsd:element name="physicalProcess" type="Physics" maxOccurs="unbounded"/>
48 </xsd:sequence>
49 </xsd:extension>
50 </xsd:complexContent>
51 </xsd:complexType>
52
53 <xsd:complexType name="Protocol" abstract="true">
54 <xsd:annotation>
55 <xsd:documentation>The base class of all protocols producing snapshots. These objects define how SNAP experiments can be performed, like a blue-print, template. For simulations the protocol will be the simulation code, here represented by SNAPSimulator. In the analysis model this class is more fully defined, but for the logical model for discovering SNAP experiments much of its components are moved to the SNAPExperiment itself</xsd:documentation>
56 <xsd:appinfo>xmiid=_12_1_8e0028f_1175789188406_755001_115</xsd:appinfo>
57 </xsd:annotation>
58 <xsd:complexContent>
59 <xsd:extension base="p5:Resource">
60 <xsd:sequence>
61 <xsd:element name="code" type="xsd:string"/>
62 <xsd:element name="version" type="xsd:string"/>
63 <xsd:element name="parameterGroup" type="ParameterGroup" minOccurs="0" maxOccurs="unbounded"/>
64 <xsd:element name="representation" type="RepresentationObjectType" minOccurs="0"
65 maxOccurs="unbounded"/>
66 <xsd:element name="parameter" type="InputParameter" minOccurs="0" maxOccurs="unbounded"/>
67 </xsd:sequence>
68 </xsd:extension>
69 </xsd:complexContent>
70 </xsd:complexType>
71
72 <xsd:complexType name="ClusterFinder">
73 <xsd:annotation>
74 <xsd:documentation>A cluster finder protocol.</xsd:documentation>
75 <xsd:appinfo>xmiid=_14_0_8e0028f_1202820488812_969868_2587</xsd:appinfo>
76 </xsd:annotation>
77 <xsd:complexContent>
78 <xsd:extension base="Protocol"/>
79 </xsd:complexContent>
80 </xsd:complexType>
81
82 <xsd:complexType name="Visualiser">
83 <xsd:annotation>
84 <xsd:documentation>A protocol for visualing results of other SimDB-type experiments.
85
86 TODO as this returns a non-SimDB-like result (i.e. NOT a representation of the 3+1D univers), does this belong in the model?</xsd:documentation>
87 <xsd:appinfo>xmiid=_12_1_8e0028f_1175790177281_251863_280</xsd:appinfo>
88 </xsd:annotation>
89 <xsd:complexContent>
90 <xsd:extension base="Protocol"/>
91 </xsd:complexContent>
92 </xsd:complexType>
93
94 <xsd:complexType name="ParameterGroup">
95 <xsd:annotation>
96 <xsd:documentation>Represents a (natural) grouping of input parameters.
97 Especially in protocols with large numbers of parameters it may be useful to group these
98 for browsing purposes for example. As browsing is likely an important mode of access to SimDB resources this possibility was introduced.</xsd:documentation>
99 <xsd:appinfo>xmiid=_14_0_8e0028f_1202835054703_251049_3232</xsd:appinfo>
100 </xsd:annotation>
101 <xsd:complexContent>
102 <xsd:extension base="base:MetadataObject">
103 <xsd:sequence>
104 <xsd:element name="name" type="xsd:string"/>
105 <xsd:element name="description" type="xsd:string" minOccurs="0"/>
106 <xsd:element name="member" type="ParameterGroupMember" maxOccurs="unbounded"/>
107 </xsd:sequence>
108 </xsd:extension>
109 </xsd:complexContent>
110 </xsd:complexType>
111
112 <xsd:complexType name="ParameterGroupMember">
113 <xsd:annotation>
114 <xsd:documentation>Associative class, representing a selection of a parameter in a parameter grouping.</xsd:documentation>
115 <xsd:appinfo>xmiid=_14_0_8e0028f_1202835113906_103077_3309</xsd:appinfo>
116 </xsd:annotation>
117 <xsd:complexContent>
118 <xsd:extension base="base:MetadataObject">
119 <xsd:sequence>
120 <xsd:element name="parameter" type="base:Reference">
121 <xsd:annotation>
122 <xsd:appinfo>xmiidref=_12_1_8e0028f_1213803387328_904148_265</xsd:appinfo>
123 </xsd:annotation>
124 </xsd:element>
125 </xsd:sequence>
126 </xsd:extension>
127 </xsd:complexContent>
128 </xsd:complexType>
129
130 <xsd:complexType name="SubvolumeExtractor">
131 <xsd:annotation>
132 <xsd:documentation>Protocol that extracts the representation objects in a sub-volume of an existing snapshot of another experiment.
133
134 TODO SimDAP should define whether this is the proper definition for this type of protocol.</xsd:documentation>
135 <xsd:appinfo>xmiid=_12_1_8e0028f_1175790195921_468870_325</xsd:appinfo>
136 </xsd:annotation>
137 <xsd:complexContent>
138 <xsd:extension base="Protocol"/>
139 </xsd:complexContent>
140 </xsd:complexType>
141
142 <xsd:complexType name="RepresentationObjectType">
143 <xsd:annotation>
144 <xsd:documentation>This class represents the smallest units from which a target system/object is built. It defines also the actual objects that the Snapshot-s contain. Examples are the particles in an N-body simulation, the cells in an adaptive mesh simulations, the halos in the result of a group finder</xsd:documentation>
145 <xsd:appinfo>xmiid=_12_1_8e0028f_1173260105000_913974_289</xsd:appinfo>
146 </xsd:annotation>
147 <xsd:complexContent>
148 <xsd:extension base="p6:ObjectType">
149 <xsd:sequence>
150 <xsd:element name="type" type="RepresentationObject"/>
151 <xsd:element name="label" type="xsd:string" minOccurs="0"/>
152 </xsd:sequence>
153 </xsd:extension>
154 </xsd:complexContent>
155 </xsd:complexType>
156
157 <xsd:complexType name="InputParameter">
158 <xsd:annotation>
159 <xsd:documentation>This class represent a parameter setting for a SNAP experiment. The parameter can be used in describing the physics (for example mass of a particle), in the initial conditions (for example cosmology), in the numerical implementation (for example mesh size)</xsd:documentation>
160 <xsd:appinfo>xmiid=_12_1_8e0028f_1213803387328_904148_265</xsd:appinfo>
161 </xsd:annotation>
162 <xsd:complexContent>
163 <xsd:extension base="p6:Field">
164 <xsd:sequence>
165 <xsd:element name="label" type="xsd:string" minOccurs="0"/>
166 </xsd:sequence>
167 </xsd:extension>
168 </xsd:complexContent>
169 </xsd:complexType>
170
171 <xsd:simpleType name="RepresentationObject">
172 <xsd:annotation>
173 <xsd:documentation>Represents a standard name for the objects that can be used to represent a snapshot of the universe in SNAP data products. Examples from simulations are “n-body particle”, “SPH particle”, “mesh cell”. But also simplified representations of astronomical objects could be used here, for example in halo catalogues or semi-analytical galaxy catalogues, both results of post-processing experiments
174
175 NB This should be transferred to an appropriate external ontology!</xsd:documentation>
176 <xsd:appinfo>xmiid=_12_1_8e0028f_1175855145890_581998_136</xsd:appinfo>
177 </xsd:annotation>
178 <xsd:restriction base="xsd:string">
179 <xsd:enumeration value="point particle">
180 <xsd:annotation>
181 <xsd:documentation>Represents the case where point particles are used to represent the simulated world.</xsd:documentation>
182 </xsd:annotation>
183 </xsd:enumeration>
184 <xsd:enumeration value="SPH particle">
185 <xsd:annotation>
186 <xsd:documentation>Represents the case where extended particles with hydro properties are used to represent the simulated world in an SPH simulation.</xsd:documentation>
187 </xsd:annotation>
188 </xsd:enumeration>
189 <xsd:enumeration value="extended particle">
190 <xsd:annotation>
191 <xsd:documentation>Represents the case whereextended particles are used to represent the simulated world.</xsd:documentation>
192 </xsd:annotation>
193 </xsd:enumeration>
194 <xsd:enumeration value="simple mesh cell">
195 <xsd:annotation>
196 <xsd:documentation>Represents the case where simple, non-structured/subdivided mesh cells are used to represent the simulated world in a regular grid.</xsd:documentation>
197 </xsd:annotation>
198 </xsd:enumeration>
199 <xsd:enumeration value="hierarchical mesh cell">
200 <xsd:annotation>
201 <xsd:documentation>Represents the case where mesh cells taht may be hierarchically subdivided are used to represent the simulated world in an adaptive mesh refinemenet simulation.</xsd:documentation>
202 </xsd:annotation>
203 </xsd:enumeration>
204 <xsd:enumeration value="model astro object">
205 <xsd:annotation>
206 <xsd:documentation>Represents the case where mock astronomical objects with their "physical" properties are used to represent the simulated world. Mainly found in results of post-processing. Examples are dark matter halos as the result of a cluster finder, synthetic galaxies as the result of semi-analytical simulations or halo occupation distributions algorithms.</xsd:documentation>
207 </xsd:annotation>
208 </xsd:enumeration>
209 <xsd:enumeration value="custom">
210 <xsd:annotation>
211 <xsd:documentation>Represents the case wherecustom objects, for which there is no existing term available in this enumeration, are used to represent the simulated world.
212 </xsd:documentation>
213 </xsd:annotation>
214 </xsd:enumeration>
215 </xsd:restriction>
216 </xsd:simpleType>
217
218 </xsd:schema>

msdemlei@ari.uni-heidelberg.de
ViewVC Help
Powered by ViewVC 1.1.26