This enumeration contains the possible values for the cardinality attribute of a Field definition.
simdm:meta.Cardinality
Corresponds to 'Optional element'
simdm:meta.Cardinality.OPTIONAL
Corresponds to 'Mandatory element'
simdm:meta.Cardinality.MANDATORY
Corresponds to 'Multiple but maybe Optional element'
simdm:meta.Cardinality.ZERO_MANY
Corresponds to 'Multiple with at least one element'
simdm:meta.Cardinality.ONE_MANY
The DataType enumeration lists the available values for the datatype attributes used in the definition of metadata fields such as Property and InputParameter.
The values represent rather abstract data types. For example no distinction is made between different representations of integer (short, int, long) or floating point (float, double) types. Instead the mathematical number fields integer and real are used, together with rational and complex.
Alternative representations or usages of this model might add such details.
simdm:meta.DataType
A standard boolean type, with values 'true' and 'false', possibly represented differently in physical representations of the model.
simdm:meta.DataType.boolean
A standard complex type. Here no limits on accuracy of constituent Re and Im parts is made, they are assumed to be real.
simdm:meta.DataType.complex
Represents an exact time on an exact, given date. No accuracy is assumed.
simdm:meta.DataType.datetime
A floating point datatype, without impied accuracy.
simdm:meta.DataType.real
An integer datatype, without implied accuracy.
simdm:meta.DataType.integer
A rational datatype, consisting of two integers representing the numerator and denominator.
simdm:meta.DataType.rational
A standard string datatype consisting of any type of character.
simdm:meta.DataType.string
Represents a generic field like object.
simdm:object.Field
the name of this parameter or property.
Ex: omegaLambda, particleMass, linking length
simdm:object.Field.name
the data type of this parameter or property
simdm:object.Field.datatype
The cardinality of this parameter or property
simdm:object.Field.cardinality
Short description of this parameter or property
simdm:object.Field.description
indicates if this parameter or property only accept values coming from a list of valid values defined by the validValue collection
simdm:object.Field.isEnumerated
This class represents and abstract object type, and can thus be seen as a meta-modelling construct.
It allows model instances that represent complex object definitions.
simdm:object.ObjectType
The name of this object type.
simdm:object.ObjectType.name
Short description of this object type.
simdm:object.ObjectType.description
The properties of an object. Similar to the FIELD in a VOTable
simdm:object.Property
The concept represented by this property. This concept should be narrower than the broadestSKOSConcept.
simdm:object.Property.label
This class represents a naturla grouping of properties on the object type.
Is used for presentation purposes in a browsing environment.
simdm:object.PropertyGroup
Name of this paarameter grouping.
simdm:object.PropertyGroup.name
Description of this group.
simdm:object.PropertyGroup.description
Assocuiative object that represents a member in a property group.
simdm:object.PropertyGroupMember
Reference to the actual property this class associates to a property group.
simdm:object.PropertyGroupMember.property
This class assists in the definition of an object hierarchy by associating different objects. The type of relationship is borrowed loosely from UML, and can represent a composition, aggregation or reference, as defined by the relationshipType attribute.
An example is the composition relationship between a image and its pixels, or the aggregation of a FOF group and its constituent particles.
simdm:object.Relationship
Name of the variable representing the relationship on the containing parent object type.
simdm:object.Relationship.name
Describes the relation between the parent and child object type.
simdm:object.Relationship.description
This attributes indicates the type of relaion between the parent and the related object.
simdm:object.Relationship.relationshipType
The cardinality/multiplicity of the child object in the containing object.
simdm:object.Relationship.cardinality
Reference to the ObjectType that is the child in the hierarchical parent-child relation.
simdm:object.Relationship.relatedObjectType
This represents a value for an enumerated parameter or property
simdm:object.ValidValue
the value as string : can be converted to the correct datatype of the asociated parameter or property
simdm:object.ValidValue.value
A description of this value.
simdm:object.ValidValue.description
Short name / alias for this value (useful in GUI)
simdm:object.ValidValue.title
Type of relationship between an ObjectType and the related object type.
simdm:object.RelationshipType
Represents the usual UML-like composition relation.
simdm:object.RelationshipType.composition
Represents a 0..1 relation between an object (the referree) and the related object (the reference). Indicates a general dependency. Example, relations between a galaxy and its descendant in a merger tree, or between a source catalogue and the image it was extracted from.
simdm:object.RelationshipType.reference
This class connects a Party to a resource.
It indicates the role the party plays on the resource, for example creator, owner or publisher.
simdm:resource.Contact
The role this contact plays in the Resource
simdm:resource.Contact.role
Reference to the Party that the Contact associates to the Resource.
simdm:resource.Contact.party
Information that describes a Party, that is a person/individual or possibly an organisation.
simdm:resource.Party
the name or title of the contact person.
This can be a person's name, e.g. "John P. Jones" or a group, "Archive Support Team".
simdm:resource.Party.name
the contact email address
simdm:resource.Party.email
the contact mailing address
All components of the mailing address are given in one string, e.g. "3700 San Martin Drive, Baltimore, MD 21218 USA".
simdm:resource.Party.address
the contact telephone number
Complete international dialing codes should be given, e.g. "+1-410-338-1234".
simdm:resource.Party.telephone
A SimDM/Project is an aggregation of SimDM/Resource-s that belong together, for example because they have been produced together in the course of a scientific project.
Examples are parameter studies where a large number of simulations is run with slightly varying parameter settings. But also a single large simulation with a number of post-processing results can be gathers in this way.
It is assumed that SimDM/Project are generally "big enough" to qualify to be represented as a full-fledged Registry/Resource in an IVOA Registry. This possibility was on of the reasons to add this concept to the model.
simdm:resource.Project
Associative class between a SimDM/Project and its constitutent SimDM/Resource-s.
simdm:resource.ProjectResource
Reference to another SimDM/Resource that is included in the containing SimDM/Project.
simdm:resource.ProjectResource.resource
This class represents the main resources defined by the Simulation Data Model in the same way as the Registry/Resource class represents resources in registries. It is the base class of specialisations SimDM/Protocol, SimDM/Experiment, SimDM/Project and SimDM/Service.
These resources are the root entities that would get registered in a Simulation Database for example. They are also represented by root element declarations in XML schema serialisations of the model.
This class is a thin copy of the Registry/Resource and borrows some of its elements. It *is-not-a* Registry Resource in the sense of inheritance. In particular a SimDM/Resource has a more refined and targeted content model. Also, SimDM/Resource-s are in general (much) more fine grained than Registry/Resource-s and would not qualify to be registered in an IVOA Registry.
It will howevere be possible to transform certain SimDM/Resource-s into Registry/Resource-s.
simdm:resource.Resource
For Protocol :
The name by which this simulator is commonly known.
Ex: Gadget, Flash
For Project :
the name of the project
For Experiment :
the name of this experiment
simdm:resource.Resource.name
A description of this resource.
simdm:resource.Resource.description
a URL to a web page describing the resource.
simdm:resource.Resource.referenceURL
The UTC date and time this resource was created in the real world.
simdm:resource.Resource.created
The UTC date and time this resource was updated in the real world.
simdm:resource.Resource.updated
a tag indicating whether this resource is believed to be still actively maintained.
simdm:resource.Resource.status
Represents the scientific goal associated to a SimDM/Resource. This can be the goal of an experiment or project, or the type of object that a particular protocol will always produce. Is made concrete by suclasses representing objects or processes. We model a Target as "being an" ObjectType, which allows one to give a more detailed representation of its properties. The target is important as it represents one of the main questions scientists will ask about an experiment: what kind of astrophysical object or system or process was being simulated or modelled.
simdm:resource.Target
This class represents the actual system that is being simulated. Instances of this object should correspond to physical objects and/or systems. They should be the answer to queries such as, “what does this simulation simulate?”
simdm:resource.TargetObjectType
Indication on how many objects of this type are being modelled.
simdm:resource.TargetObjectType.multiplicity
If the target object type referes to a real object, this attribute allows one to indicate which object. This is performed by a URI that should identify the object in the Ontology of SimbadIdentifiedNames
In some cases a real identified object in the universe is being modelled. If that is the case, this attribute allows that object to be identified. We assume a list of such objects may be provided through some means, embodied by the IdentifiedObject data type.
Ex: Galaxy, Antennae, M31.
simdm:resource.TargetObjectType.identityName
Represents a concept in a SKOS vocabulary of astronomical and astrophysical object types.
simdm:resource.TargetObjectType.label
This class represents the fact that some simulations are run with the goal (Target) to investigate physical processes, rather than simulation specific objects or systems. Instances of this class can be used to describe this. For example one may study "turbulence", or "gravitational cluster" or "galaxy formation".
simdm:resource.TargetProcess
A term from the AstroJournalSubjectKeywords ontology.
simdm:resource.TargetProcess.label
The ContactRole enumeration contains the different roles a SimDM/Party can play in the creation or publishing of a SimDM/Resource.
simdm:resource.ContactRole
Role indicating that a certain SimDM/Party owns the SimDM/Resource.
simdm:resource.ContactRole.owner
Role indicating that a certain SimDM/Party created the SimDM/Resource.
simdm:resource.ContactRole.creator
Role indicating that a certain SimDM/Party published the SimDM/Resource in a SimDB repository for example.
simdm:resource.ContactRole.publisher
Role indicating that a certain SimDM/Party made some otherwise unspecified contribution to the creation of the SimDM/Resource.
simdm:resource.ContactRole.contributor
The AccessibleResource class represents an association between the containing SimDM/Service and the SimDM/Resource-s that are being made accessible by that service.
simdm:resource.dal.AccessibleResource
Description of how the particular SimDM/Resource referenced by this object is made available by the parent SimDM/Service.
simdm:resource.dal.AccessibleResource.description
Direct URI for accessing the referenced SimDM/Resource using the parent service.
The parent service has a baseURL through which one can access the service interface. From there one may be able to browse through all SimDM/Resource-s that are made available, but a specific (data access) protocol to reach a given SimDM/Resource or how to browse these SimDM/Resource-s is not defined by this model. IF it is possible to access the SimDM/Resource directly through the SimDM/Service, for example to download or browse its contents, this attribute gives the corresponding URI.
simdm:resource.dal.AccessibleResource.accessURI
This reference points to the SimDM/Resource that this SimDM/AccessibleResource class associates to the SimDM/Service. The end point can be any SimDM/Resource.
simdm:resource.dal.AccessibleResource.resource
The CustomService class represents a custom SimDM/Service for accessing SimDM/Resource-s. It is not assumed that a predefined protocol is implemented. Its main role is to distinnguish it from SimDAL and other services implementing potential, future IVOA standards.
But many interesting custom services giving access to simulation results exist and can be reistered and discovered through this class.
simdm:resource.dal.CustomService
This class represents a web service that can be used to access SimDM/Resource-s registered in for example a SimDB. The precise way in which the web service gives access to these results not specified in detail. It includes simple downloads, and services implementing standards such as SimDAL.
SimDM/Service is related to SimDM/Resource and can be used for more general purposes than simply giving access to results of a single experiment. It may be a web service that can handle results of any experiment performed by a particular SimDM/Protocol, or give access to all resources in a SimDM/Project.
The main goal of introducing SimDM/Service in the model is so that users can find web services based on requests for specific tyes of simulations etc. For example users may wish to find web services giving access to hydro simulations of clusters of galaxies with particular properties.
.
It is assumed that web services registerd in a SimDB are also registered in a Registry which will store the more detailed capbilitieis and other service metadata. Therefore such details are not introduced here.
simdm:resource.dal.Service
The base URL of this SimDM/Service.
In case the web service implements a standard IVOA protocol such as SimDAL, this base URL can be used in the same way as other typical IVOA S*AP services. Parameters defined by the standard may be added to the base URL so that a proper HTTP GET request can be created for accessing the web service directly.
simdm:resource.dal.Service.baseURL
The IVO identifier by which this service is registered in an IVOA Resource Registry. Each SimDM/Service should be registered in such a registry and this identifier allows one to obtain the full description of this service as defined by the Registry standard.
simdm:resource.dal.Service.registryId
Represents a SimDM/Service conforming to a SimDAL protocol.
This is a place holder class that may in future version of the model be defined in more detail when SimDAL services themselves have been fully specified.
simdm:resource.dal.SimDALService
The AppliedAlgorithm class represents the application of a particular algorithm in an experiment.
Some simulation codes allow one to choose between different algorithms for representing a particular process. For example some N-Body codes allow one to choose between Tree-only or Tree+ParticleMesh codes.
To indicate which algorithms were actually used in an experiment one adds an instance of this AppliedAlgorithm class to the collection on the experiment.
simdm:resource.experiment.AppliedAlgorithm
Reference to the actual algorithm that is applied
simdm:resource.experiment.AppliedAlgorithm.algorithm
The AppliedPhysics class represents the association between a physical process on a Simulator and this class' parent Simulation.
Many simulation codes allow one to turn on or off modules corresponding to different physics. For example certain SPH codes allow one to turn off the hydrodynamics, leaving only gravity as the physical process being simulated.
simdm:resource.experiment.AppliedPhysics
Reference to the Simulator's Physcis module that is used in the Simulation.
simdm:resource.experiment.AppliedPhysics.physics
Represents an individual object of a given object type produced by an experiment. Is required if we want to represent object-object collection hierarchies. NB the name DataObject is used iso Object, as the latter may lead to name clashes in serialisations.
In this model any artefact produced by a Protocol can be represented by an appropriate ObjectType and relations can exist between them. Some of these relations are many-to-one, i.e. between object collections and parent ojects. If such relations must also be represented in the output of an Experiment, it must be possible to represent individual objects.
A typical example is a cosmological simulation produccing N > 1 snapshots. We may want to represent each individual snapshot in the result, together with statistical information about the collections of particles contained in each.
The object can give values to properties related to objects of its type.
In principlpe this model now would allow one to describe an experiment in all details, with each individual object listed. This is as should be for a conceptual model, but in particular applications we envision that limits be put on the size of results. For example it does not make sense to store the complete results of a large cosmolgical simulation in this way, as the storage of property values is inefficient.
simdm:resource.experiment.DataObject
The SimDM/Experiment represents the execution of a computer program represented by a SimDM/Protocol. It defines how the program was run by providing values to parameters for example. It describes the goal of the experiment in terms of the physical objects and processes that are being simulated and it contains the collection of results.
simdm:resource.experiment.Experiment
The date/time at which the experiment was completed
simdm:resource.experiment.Experiment.executionTime
Reference to the Protocol used in the exeuciton of this Experiment.
Subclasses of this Experiment will in general override/"subset" this reference to subclasses of Protocol.
simdm:resource.experiment.Experiment.protocol
Associates an individual Object to an InputDataSet.
Thus if for example only 3 individual snapshots out of a collection of N snapshots produced by a cosmological simulation are post-processed, the actual snapshots used can be indicated using this associative object.
simdm:resource.experiment.InputDataObject
Reference to an actual object that is being used in an experiment.
simdm:resource.experiment.InputDataObject.object
Many experiments require pre-existing data sets for their execution.
This class represents such an association for its parent SimDM/Experiment.
It is assumed to contain 1 or more objects of a specified SimDM/InputDataObjectType defined on the SimDM/Protocol used by the container SimDM/Experiment.
In those cases where the actual input data set is represented by a SimDM/OutputDataset, for example in a SimDB, we can represent the input data by a corresponding reference. Whereas that would be optimal, it may not always be practical. In cases where this is not so, this reference is replaced with an accessURL attribute on this class. This would allow a user to find out whether a product exists in the database with that same url, make the link indirect but arguably more correct.
simdm:resource.experiment.InputDataset
Describes the role that the input data set plays in the experiment.
simdm:resource.experiment.InputDataset.description
URL by which the input data set can be obtained.
simdm:resource.experiment.InputDataset.url
The SimDM/OutputDataset produced by an earlier SimDM/Experiment that is used as input data for the current one.
simdm:resource.experiment.InputDataset.product
Reference to the type definition for this SimDM/InputDataset. This must refer to a SimDM/InputDataObjectType defined on the SimDM/Protocol according to which the SimDM/Experiment is performed.
simdm:resource.experiment.InputDataset.type
Instance of a composition Relationship between an ObjectType and a collection of objects.
simdm:resource.experiment.ObjectCollection
TODO : Missing description : please, update your UML model asap.
simdm:resource.experiment.ObjectCollection.collection
reference to the relationship definition on the ObjectType that is represented by the ObjectCollection. The referenced Relationship MUST have relationshipType='composition'.
simdm:resource.experiment.ObjectCollection.collectionDefinition
Instance of a reference Relationship between two ObjectType-s.
simdm:resource.experiment.ObjectReference
The object referenced by the ObjectReference's parent DataObject.
simdm:resource.experiment.ObjectReference.object
Reference to the relationship definition on the ObjectType that is represented by the ObjectReference. The referenced Relationship MUST have relationshipType='reference'.
simdm:resource.experiment.ObjectReference.referenceDefinition
This class represents 1 or more instances of a single SimDM/OutputDataObjectType-s produced by an SimDM/Experiment.
No assumption is made how a SimDM/OutputDataset is represented in the real world. It may consist of one or multiple files, or possibly one or more tables in a database, or subsets thereof. The exact storage is not currently modelled.
The class represents an actual collection of objects without (necessarily) listing these all. Instead it is to be used to allow statistical summaries/characterisation of these products.
A special feature is that a SimDM/OutputDataset may define a dependency on another, 'parent' data set. This reflects to possibility in the SimDM/Protocol to model relationships between different SimDM/OutputDataObjectType-s.
This is implemented using two references, one to the parent SimDM/OutputDataset, the other to the SimDM/Relationship.
simdm:resource.experiment.OutputDataset
Gives the number of objects in this SimDM/OutputDataset
simdm:resource.experiment.OutputDataset.numberOfObjects
Represents an optional reference to a URL from which the SimDM/OutputDataset can be obtained. No statement is made on whether this should represent a simple file for download, or a link to a web page with information how to obtain it.
simdm:resource.experiment.OutputDataset.accessURL
This reference to SimDM/DataObjectType indicates the type of data object stored in this collection.
simdm:resource.experiment.OutputDataset.objectType
To run an Experiment, one usually needs to assign values to parameters defined on the corresponding Protocol. This class makes the association between the Experiment and the parameters, indicating which parameter is given what value.
Input parameters can be given any datatype from the DataType enumeration and hence it is in principle impossible to assign a single datatype to the value attribute storing the parameter setting in this model. Whereas we might use a generic string data type, this will in many implementations limit the use of query expressions that one might use for numerical values for example.
As a work around the current design has two attributes, one of type real, one of type string. The former should be used for numerical InputParanmeters, the latter for all others.
simdm:resource.experiment.ParameterSetting
Attribute that holds on to the actual parameter value in case the referenced input parameter is not a numerical type.
simdm:resource.experiment.ParameterSetting.stringValue
Attribute that holds on to the actual parameter value in case the referenced input parameter is a numerical type.
simdm:resource.experiment.ParameterSetting.numericValue
Reference to the actual input parameter whose value is being set.
simdm:resource.experiment.ParameterSetting.inputParameter
Represents an experiment that corresponds to the execution of a PostProcessor protocol. It manipulates a pre-existing result to produce new results, but without introducing new physics.
simdm:resource.experiment.PostProcessing
The primary experiment whose results are being post-processed by this PostProcessing step. Simplifies looking up the original experiments, but is in principle redundant with the inputData.
simdm:resource.experiment.PostProcessing.primaryExperiment
Assign a value to a property of a data object.
simdm:resource.experiment.PropertyValue
If the Property to which this value is assigned is not numeric, this attribute should be used to represent the value.
simdm:resource.experiment.PropertyValue.stringValue
It the property to which this value is assigned is numerical, use this attribute to represent the value.
simdm:resource.experiment.PropertyValue.numericValue
The property to which the value is assigned.
simdm:resource.experiment.PropertyValue.property
This class represents the execution of simulation codes. Its protocol is therefore a SimDM/Simulator iso a general SimDM/Protocol. It extends SimDM/Experiment by adding descriptions of the physical processes that were simulated
simdm:resource.experiment.Simulation
This class allows users to provide a statistical characterisation of a collection of objects in a specified SimDM/OutputDataset. It represents both 'a priori' and 'a posteriori' characterisations. With a priori characterisation we indicate possible and/or nominal [?] values the variable may take, it defines the possible range of values of the SimDM/Property. In contrast, an a posteriori characterisation of a property in an collection provides summarising, likely statistical, information on the values that were actually measured (i.e. observed, simulated) by the objects in the collection.
The a priori characterisation is most similar, in fact a generalisation of the Characterisation model of the IVOA Data Model working group.
In the current model we stick to simple (numerical) quantities for characterising a collection of objects. For example the equivalent value of a support from the CharacterisationDM is absent, as it is not terribly useful for discovery and querying, even more so of course for concepts equivalent to sensitivity.
simdm:resource.experiment.StatisticalSummary
This attribute indicates which statistic is used to statistically summarise the referenced SimDM/ObjectType's SimDM/Property.
simdm:resource.experiment.StatisticalSummary.statistic
If 'true', this attribute indicates that the statistical characterisation of a SimDM/Propertyis aPriori. That is it indicates that the value says something about what the publisher believes are the possible values the SimDM/Property can assume. An "p priori" characterisation is therefore a translation of the effects that the input configuration (SimDM/ParameterSetting, SimDM/InputDataset), the "provenance-of-the-actual-experiment" therefore) is EXPECTED to have on the final result, represented by the SimDM/OutputDataset-s and the SimDM/Property-s of their constituent objects.
Alternatively, if the value is "false", it indicates that the statistical charecterisation is 'a posteriori', i.e. it says something about the actual values that were assumed. This requires in general some level of post processing beyond simply storing the result, but in general using simple statistics such as mean and standard deviation that are not modelled as a separate SimDM/Experiment.
simdm:resource.experiment.StatisticalSummary.aPriori
Summarising value of a numerical SimDM/Property in a collection of objects
simdm:resource.experiment.StatisticalSummary.numericValue
In case a string-typed property is summarised this attribute should be used to give the value. This would likely be applicable to a restricted set of statistics such as nominal value.
simdm:resource.experiment.StatisticalSummary.stringValue
The SimDM/Property of the SimDM/ObjectType that is being characterised.
In the IVOA DM's characterisation model this is represented by specified objects, such as spatialaxis, timeaxis etc. Here we do not know in advance which kind of property is characterised, hence this explicit reference.
simdm:resource.experiment.StatisticalSummary.axis
This enumeration lists possible statistics that can be used to characterise a collection of Property-s in a result. The literals in this enumeration in general correspond to the result of simple statistical operation on this collection (when a posteriori) or on the corresponding operation on the a priori probability distribtion (assuming this can be defined) of its values.
There is overlap between this enumeration and the 'stat' family of UCDs in the UCD controlled vocabulary (http://www.ivoa.net/Documents/REC/UCD/UCDlist-20070402.html). Where this enumeration is used one might consider using a vocabulary based on those terms.
simdm:resource.experiment.Statistic
In case an output data set contains exactly 1 object, the value statistic should be used to indicate the actual property value.
simdm:resource.experiment.Statistic.value
A typical value, as judged by the publisher of the results. May not correspond to a predefined statistical operation such as mean or mode.
simdm:resource.experiment.Statistic.nominal
Represents the minimum ('possible' if a priori, 'attained' if a osteriori) value for the characterised property.
simdm:resource.experiment.Statistic.min
Represents the maximum ('possible' if a priori, 'attained' if a osteriori) value for the characterised property.
simdm:resource.experiment.Statistic.max
Represents the mode of the distribution ('expected' if a priori, 'attained' if a posteriori) for the characterised property.
simdm:resource.experiment.Statistic.mode
Represents the mean ('expected' if a priori, 'attained' if a posteriori) value for the characterised property.
simdm:resource.experiment.Statistic.mean
Represents the median of a distribution.
simdm:resource.experiment.Statistic.median
Represents the expected/attained standard deviation for the characterised property.
simdm:resource.experiment.Statistic.stdev
Represents the expected/attained variance for the characterised property.
simdm:resource.experiment.Statistic.variance
This class represents numerical algorithms available in a SimDM/Protocol.
In Simulators an algorithm may approximate a physical process. Examples from cosmological simulations are different algorithms to implement gravity: direct particle-particle interaction, particle-mesh, or various types of tree based algorithms.
In post-processors such as cluster finder this class can represent a partiular cluster definition such as friends-of-friends or spherical overdensity.
simdm:resource.protocol.Algorithm
A common name given to this algorithm.
simdm:resource.protocol.Algorithm.name
Short description of this algorithm.
simdm:resource.protocol.Algorithm.description
Short name by which this algorithm is known in the SKOS vocabulary of numerical algorithms.
simdm:resource.protocol.Algorithm.label
Type of data objects that the protocol needs in its execution.
simdm:resource.protocol.InputDataObjectType
Label indicating the type of data object represented by this InputDataObjectType through reference to a SKOS concept.
simdm:resource.protocol.InputDataObjectType.label
If not null, this reference provides the definition of the input data object type as being a predefined SimDM/OutputDataObjectType of another SimDM/Protocol.
It's implication is that the current SimDm/Protocol requires the results of another SimDM/Protocol for its execution.
If this reference is null the input data object type must be defined using the properties inherited from the base object type.
simdm:resource.protocol.InputDataObjectType.definition
This class represent an input parameter on a protocol.
In general,a simulation codes needs the user to set values to parameters that govern the running of the code. These may be parameters describing the physics in a simulation, or they may be numerical parameters governing the approximation of the process by a particular algorithm.
simdm:resource.protocol.InputParameter
A label to be given to this input parameter from an appropriate SKOS vocabulary.
simdm:resource.protocol.InputParameter.label
This class represents the type of data object that the container SimDM/Protocol can produce.
This concept includes any type of data object the protocol deals with.
It can range from the smallest data units such as individual N-Body particles or pixels in a synthetic spectrum, up to the largest which may be a collection of snapshots in an N-body simulation ,each of them containing collections of particles.
It defines also the actual SimDM/OutputDataset-s that a SimDM/Experiment's has produced.
Since a SimDM/OutputDataObjectType is-a SimDM/ObjectType, it can be related to other objects using SimDM/Relationship-s.
In this way a hierarchy of data types can be described.
For example a spectrum can be a such a data object and will be composed of pixels. A FOF group catalogue will be composed of FOF groups which are aggregations of particles.
simdm:resource.protocol.OutputDataObjectType
Name that this type of particle is given in an appropriate SKOS vocabulary.
simdm:resource.protocol.OutputDataObjectType.label
Represents a (natural) grouping of SimDM/InputParameters.
Especially in protocols with large numbers of parameters it may be useful to group these
for browsing purposes for example. As browsing is likely an important mode of access to SimDM/Resource-s stored in a SimDB for example, this possibility was introduced.
But the main use should be reserved for semantic groupings. For example all parameters together defining the cosmology a certain simulation is run in. Or the parameters setting "merely" numerical properties such as smoothing lengths.
simdm:resource.protocol.ParameterGroup
Name given to this group.
simdm:resource.protocol.ParameterGroup.name
Short description of the purpose of this group.
simdm:resource.protocol.ParameterGroup.description
Associative class, representing a selection of a parameter in a parameter grouping.
simdm:resource.protocol.ParameterGroupMember
Reference to the selected input parameter.
simdm:resource.protocol.ParameterGroupMember.parameter
This class represents a physical processes that is modelled in a simulation code.
Simulating a physical process generally corresponds to solving equations of motion numerically, evolving the simulated system from one state to the next.
simdm:resource.protocol.Physics
Name by which this physical process is represented in the simulator code
simdm:resource.protocol.Physics.name
Short description of the physical process represented by this class.
simdm:resource.protocol.Physics.description
The SKOS concept identifying this process in a standardised SKOS vocabulary.
simdm:resource.protocol.Physics.label
This concrete subclass of SimDM/Protocol represents protocols that deal with post-processing results of earlier experiments. We do not specify the details of this type much further. Main difference with eg the SimDM/Simulator type is that NO new physical processes are introduced/simulated in the processing of the previous results. Examples are cluster finders, visualisation tools etc.
simdm:resource.protocol.PostProcessor
A SimDM/Protocol represents software code that can be used to run astrophysical simulations or to post-process simulation results. A SimDM/Protocol defines the method by which SimDM/Experiment-s can be performed, like a blue-print, or template. The SimDM/Protocol concept is separated out from the execution of its code in SimDM/Experiment, which allows us to reuse it for all experiments using the same code.
The concept is a direct gemeralisation of the concept by the same name in Martin Fowler's book "Analysis Patterns: Reusable Object Models" (Addison-Wesley Professional, 1996).
simdm:resource.protocol.Protocol
link where the code can be downloaded, if available
simdm:resource.protocol.Protocol.code
the version of the simulator code that was used
simdm:resource.protocol.Protocol.version
This class represents the simulation software that one uses to run a simulation. It is a special case of a SimDM/Protocol.
It is different from other SimDM/Protocols in that it explicitly defines the physical processes that are (can be) simulated. This indeed is the defining characteristic of the SimDM/Simulator: it simulates/models physical processes. This in contrast to a "mere" SimDM/PostProcessor which takes the input data and analyses it without adding new physics. It does not imply that simulators can not use existing results. For example consider semi-analytical galaxy formation routines which work on existing halo (merger) catalogues.
simdm:resource.protocol.Simulator