SNAP data model, online docThis page gives the Wiki version of the | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Changed: | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
< < | documentation for the model and wil supplant that document. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
> > | documentation for the model and wil supplant that document. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
See the following links for
Table of Contents
1 SummaryThis document presents a model for describing certain types of numerical computer simulations and certain types of simulation post-processing products. The model is to be used in the query part of the Simple Numerical Access Protocol (SNAP, TBD think of better name?], and in discovery of interesting SNAP services in the first place. We only consider simulations for systems that represent a space-time sub-volume of the universe and (part of) its material contents. In general these simulations will evolve this system forward in time and are able to produce snapshots, representing the state of the system at a number of consecutive times. These direct, raw results of simulations we call Level-0 products, following similar terminology for observations. SNAP also covers Level-1 products, which consist of the results of certain types of post-processing of simulations, namely those products that in some form represent a spatial sub-volume of the universe. We do not make any restrictions on the type of systems being simulated, or the size of the simulation, or the way the system is represented in the simulation code and results. We also make no restrictions on the type of “observables” produced by the simulations. The SNAP protocol includes online services that process level-0 or level-1 results and produce (by definition) other level-1 results. The allowed services deal with selecting the results in a sub-volume of the complete result, projections onto a 2-dimensional mesh, ... [TBC]2 Use cases, scenarios, requirementsWe have assembled a list of explicit use cases and scenarios from which we derive requirements for the current model and the SNAP protocol. Scientific goals and corresponding questions to a repository of simulations:
3 Modelling simulations and related data productsFor the purpose of this specification we consider a simulation as the execution of software that produces a representation of a spatial system, and possibly follows its evolution form one state to the next by approximating the true physical processes acting on the system with numerical algorithms. A description of such a simulation can be provided by giving the representation of the state of the system at each point of time, of the physics being modelled as differential equations and the way these act on the representation variables. It requires initial condirtions and parameters describing the physics as well as numerical approximations. For discovery purposes it is also important to be able provide summarising information about the results. To think about the appropriate structure of the model it is useful to think about the steps a user might go through when querying a database system in various “drilling down” steps. For example the following questions might be asked :
4 Documentation UML diagram | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Changed: | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
< < | The process shortly described in the previous sections has led first to an analysis, or domain model which we will not describe here (see here). That model in combination with the particular application specific requirements have led us to design a logical model for describing simulations and how this is to be used in the discovery and query phases in SNAP. The diagrams on this page show the UML version of that model and give the MagicDraw version of it. We now proceed to describe this model in detail, first the Class-es (orange), then the Datatype-s, which includes Enumerations, colored grey. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
> > | The process shortly described in the previous sections has led first to an analysis, or domain model which we will not describe here (see here). That model in combination with the particular application specific requirements have led us to design a logical model for describing simulations and how this is to be used in the discovery and query phases in SNAP. The diagrams on this page show the UML version of that model and give the MagicDraw version of it. We now proceed to describe this model in detail, first the Class-es (orange), then the Datatype-s, which includes Enumerations, colored grey. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Below we list all the classes in the UML diagram. We use the definitions in this page Template table for documenting child elements
class SNAPResource...
class SNAPProtocol extends SNAPResourceThe 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.
class SNAPSimulator extends SNAPProtocolclass InputParameter
class SNAPExperiment extends SNAPResource | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Changed: | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
< < | The base class for those kinds of experiments that can produce representations of a part of the universe. It is an experiment in the sense as defined in the analysis model and in the original domain model. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
> > | The base class for those kinds of experiments that can produce representations of a part of the universe. It is an experiment in the sense as defined in the analysis model and in the original domain model. | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
class SNAPSimulation extends SNAPExperimentclass SNAPPostProcessing extends SNAPExperimentclass SNAPProject extends SNAPResourceclass ObjectTypeclass TargetObjectType extends ObjectTypeclass RepresentationObjectType extends ObjectTypeclass Algorithm |
SNAP data model, online docThis page gives the Wiki version of the documentation for the model and wil supplant that document. See the following links for Table of Contents
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Changed: | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
< < | * 1 Summary | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
> > | 1 Summary | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
This document presents a model for describing certain types of numerical computer simulations and certain types of simulation post-processing products. The model is to be used in the query part of the Simple Numerical Access Protocol (SNAP, TBD think of better name?], and in discovery of interesting SNAP services in the first place.
We only consider simulations for systems that represent a space-time sub-volume of the universe and (part of) its material contents. In general these simulations will evolve this system forward in time and are able to produce snapshots, representing the state of the system at a number of consecutive times. These direct, raw results of simulations we call Level-0 products, following similar terminology for observations.
SNAP also covers Level-1 products, which consist of the results of certain types of post-processing of simulations, namely those products that in some form represent a spatial sub-volume of the universe.
We do not make any restrictions on the type of systems being simulated, or the size of the simulation, or the way the system is represented in the simulation code and results. We also make no restrictions on the type of “observables” produced by the simulations. The SNAP protocol includes online services that process level-0 or level-1 results and produce (by definition) other level-1 results. The allowed services deal with selecting the results in a sub-volume of the complete result, projections onto a 2-dimensional mesh, ... [TBC]
2 Use cases, scenarios, requirementsWe have assembled a list of explicit use cases and scenarios from which we derive requirements for the current model and the SNAP protocol. Scientific goals and corresponding questions to a repository of simulations:
3 Modelling simulations and related data productsFor the purpose of this specification we consider a simulation as the execution of software that produces a representation of a spatial system, and possibly follows its evolution form one state to the next by approximating the true physical processes acting on the system with numerical algorithms. A description of such a simulation can be provided by giving the representation of the state of the system at each point of time, of the physics being modelled as differential equations and the way these act on the representation variables. It requires initial condirtions and parameters describing the physics as well as numerical approximations. For discovery purposes it is also important to be able provide summarising information about the results. To think about the appropriate structure of the model it is useful to think about the steps a user might go through when querying a database system in various “drilling down” steps. For example the following questions might be asked :
4 Documentation UML diagramThe process shortly described in the previous sections has led first to an analysis, or domain model which we will not describe here (see here). That model in combination with the particular application specific requirements have led us to design a logical model for describing simulations and how this is to be used in the discovery and query phases in SNAP. The diagrams on this page show the UML version of that model and give the MagicDraw version of it. We now proceed to describe this model in detail, first the Class-es (orange), then the Datatype-s, which includes Enumerations, colored grey. Below we list all the classes in the UML diagram.We use the definitions in this page Template table for documenting child elements
class SNAPResource...
class SNAPProtocol extends SNAPResourceThe 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.
class SNAPSimulator extends SNAPProtocolclass InputParameter
class SNAPExperiment extends SNAPResourceThe base class for those kinds of experiments that can produce representations of a part of the universe. It is an experiment in the sense as defined in the analysis model and in the original domain model.
class SNAPSimulation extends SNAPExperimentclass SNAPPostProcessing extends SNAPExperimentclass SNAPProject extends SNAPResourceclass ObjectTypeclass TargetObjectType extends ObjectTypeclass RepresentationObjectType extends ObjectTypeclass Algorithm<--
|
SNAP data model, online docThis page gives the Wiki version of the documentation for the model and wil supplant that document. See the following links for Table of Contents
| |||||||||||||||||||||||||||||||||||
Changed: | |||||||||||||||||||||||||||||||||||
< < | 1 Summary | ||||||||||||||||||||||||||||||||||
> > | * 1 Summary | ||||||||||||||||||||||||||||||||||
This document presents a model for describing certain types of numerical computer simulations and certain types of simulation post-processing products. The model is to be used in the query part of the Simple Numerical Access Protocol (SNAP, TBD think of better name?], and in discovery of interesting SNAP services in the first place.
We only consider simulations for systems that represent a space-time sub-volume of the universe and (part of) its material contents. In general these simulations will evolve this system forward in time and are able to produce snapshots, representing the state of the system at a number of consecutive times. These direct, raw results of simulations we call Level-0 products, following similar terminology for observations.
SNAP also covers Level-1 products, which consist of the results of certain types of post-processing of simulations, namely those products that in some form represent a spatial sub-volume of the universe.
We do not make any restrictions on the type of systems being simulated, or the size of the simulation, or the way the system is represented in the simulation code and results. We also make no restrictions on the type of “observables” produced by the simulations. The SNAP protocol includes online services that process level-0 or level-1 results and produce (by definition) other level-1 results. The allowed services deal with selecting the results in a sub-volume of the complete result, projections onto a 2-dimensional mesh, ... [TBC]
2 Use cases, scenarios, requirementsWe have assembled a list of explicit use cases and scenarios from which we derive requirements for the current model and the SNAP protocol. Scientific goals and corresponding questions to a repository of simulations:
3 Modelling simulations and related data productsFor the purpose of this specification we consider a simulation as the execution of software that produces a representation of a spatial system, and possibly follows its evolution form one state to the next by approximating the true physical processes acting on the system with numerical algorithms. A description of such a simulation can be provided by giving the representation of the state of the system at each point of time, of the physics being modelled as differential equations and the way these act on the representation variables. It requires initial condirtions and parameters describing the physics as well as numerical approximations. For discovery purposes it is also important to be able provide summarising information about the results. To think about the appropriate structure of the model it is useful to think about the steps a user might go through when querying a database system in various “drilling down” steps. For example the following questions might be asked :
4 Documentation UML diagramThe process shortly described in the previous sections has led first to an analysis, or domain model which we will not describe here (see here). That model in combination with the particular application specific requirements have led us to design a logical model for describing simulations and how this is to be used in the discovery and query phases in SNAP. The diagrams on this page show the UML version of that model and give the MagicDraw version of it. We now proceed to describe this model in detail, first the Class-es (orange), then the Datatype-s, which includes Enumerations, colored grey. Below we list all the classes in the UML diagram.We use the definitions in this page Template table for documenting child elements
| |||||||||||||||||||||||||||||||||||
Changed: | |||||||||||||||||||||||||||||||||||
< < | class SNAPResource | ||||||||||||||||||||||||||||||||||
> > | class SNAPResource | ||||||||||||||||||||||||||||||||||
...
| |||||||||||||||||||||||||||||||||||
Changed: | |||||||||||||||||||||||||||||||||||
< < | class SNAPProtocol extends SNAPResource | ||||||||||||||||||||||||||||||||||
> > | class SNAPProtocol extends SNAPResource | ||||||||||||||||||||||||||||||||||
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.
| |||||||||||||||||||||||||||||||||||
Added: | |||||||||||||||||||||||||||||||||||
> > |
| ||||||||||||||||||||||||||||||||||
Changed: | |||||||||||||||||||||||||||||||||||
< < | class SNAPSimulator extends SNAPProtocol | ||||||||||||||||||||||||||||||||||
> > | class SNAPSimulator extends SNAPProtocol | ||||||||||||||||||||||||||||||||||
Added: | |||||||||||||||||||||||||||||||||||
> > |
class InputParameter
| ||||||||||||||||||||||||||||||||||
Changed: | |||||||||||||||||||||||||||||||||||
< < | class SNAPExperiment extends SNAPResource | ||||||||||||||||||||||||||||||||||
> > | class SNAPExperiment extends SNAPResource | ||||||||||||||||||||||||||||||||||
The base class for those kinds of experiments that can produce representations of a part of the universe. It is an experiment in the sense as defined in the analysis model and in the original domain model.
| |||||||||||||||||||||||||||||||||||
Changed: | |||||||||||||||||||||||||||||||||||
< < | class SNAPSimulation extends SNAPExperiment | ||||||||||||||||||||||||||||||||||
> > | class SNAPSimulation extends SNAPExperiment | ||||||||||||||||||||||||||||||||||
Changed: | |||||||||||||||||||||||||||||||||||
< < | class SNAPPostProcessing extends SNAPExperiment | ||||||||||||||||||||||||||||||||||
> > | class SNAPPostProcessing extends SNAPExperiment | ||||||||||||||||||||||||||||||||||
Changed: | |||||||||||||||||||||||||||||||||||
< < | class SNAPProject extends SNAPResource | ||||||||||||||||||||||||||||||||||
> > | class SNAPProject extends SNAPResource | ||||||||||||||||||||||||||||||||||
Added: | |||||||||||||||||||||||||||||||||||
> > |
class ObjectTypeclass TargetObjectType extends ObjectTypeclass RepresentationObjectType extends ObjectTypeclass Algorithm | ||||||||||||||||||||||||||||||||||
<--
|
SNAP data model, online docThis page gives the Wiki version of the documentation for the model and wil supplant that document. See the following links for | |||||||||||||||||||||||||||||||||||
Deleted: | |||||||||||||||||||||||||||||||||||
< < | and | ||||||||||||||||||||||||||||||||||
Changed: | |||||||||||||||||||||||||||||||||||
< < | Below we list all the classes in the UML diagram. We use the definitions in this page | ||||||||||||||||||||||||||||||||||
> > | Table of Contents
| ||||||||||||||||||||||||||||||||||
Added: | |||||||||||||||||||||||||||||||||||
> > | 1 SummaryThis document presents a model for describing certain types of numerical computer simulations and certain types of simulation post-processing products. The model is to be used in the query part of the Simple Numerical Access Protocol (SNAP, TBD think of better name?], and in discovery of interesting SNAP services in the first place. We only consider simulations for systems that represent a space-time sub-volume of the universe and (part of) its material contents. In general these simulations will evolve this system forward in time and are able to produce snapshots, representing the state of the system at a number of consecutive times. These direct, raw results of simulations we call Level-0 products, following similar terminology for observations. SNAP also covers Level-1 products, which consist of the results of certain types of post-processing of simulations, namely those products that in some form represent a spatial sub-volume of the universe. We do not make any restrictions on the type of systems being simulated, or the size of the simulation, or the way the system is represented in the simulation code and results. We also make no restrictions on the type of “observables” produced by the simulations. The SNAP protocol includes online services that process level-0 or level-1 results and produce (by definition) other level-1 results. The allowed services deal with selecting the results in a sub-volume of the complete result, projections onto a 2-dimensional mesh, ... [TBC] | ||||||||||||||||||||||||||||||||||
Deleted: | |||||||||||||||||||||||||||||||||||
< < | Table of Contents for classes[TBD Order Alphabetically] | ||||||||||||||||||||||||||||||||||
Changed: | |||||||||||||||||||||||||||||||||||
< < |
| ||||||||||||||||||||||||||||||||||
> > | 2 Use cases, scenarios, requirements | ||||||||||||||||||||||||||||||||||
Added: | |||||||||||||||||||||||||||||||||||
> > | We have assembled a list of explicit use cases and scenarios from which we derive requirements for the current model and the SNAP protocol. | ||||||||||||||||||||||||||||||||||
Changed: | |||||||||||||||||||||||||||||||||||
< < | Template table | ||||||||||||||||||||||||||||||||||
> > | Scientific goals and corresponding questions to a repository of simulations: | ||||||||||||||||||||||||||||||||||
Added: | |||||||||||||||||||||||||||||||||||
> > |
3 Modelling simulations and related data productsFor the purpose of this specification we consider a simulation as the execution of software that produces a representation of a spatial system, and possibly follows its evolution form one state to the next by approximating the true physical processes acting on the system with numerical algorithms. A description of such a simulation can be provided by giving the representation of the state of the system at each point of time, of the physics being modelled as differential equations and the way these act on the representation variables. It requires initial condirtions and parameters describing the physics as well as numerical approximations. For discovery purposes it is also important to be able provide summarising information about the results. To think about the appropriate structure of the model it is useful to think about the steps a user might go through when querying a database system in various “drilling down” steps. For example the following questions might be asked :
4 Documentation UML diagramThe process shortly described in the previous sections has led first to an analysis, or domain model which we will not describe here (see here). That model in combination with the particular application specific requirements have led us to design a logical model for describing simulations and how this is to be used in the discovery and query phases in SNAP. The diagrams on this page show the UML version of that model and give the MagicDraw version of it. We now proceed to describe this model in detail, first the Class-es (orange), then the Datatype-s, which includes Enumerations, colored grey. Below we list all the classes in the UML diagram.We use the definitions in this page Template table for documenting child elements | ||||||||||||||||||||||||||||||||||
| |||||||||||||||||||||||||||||||||||
Changed: | |||||||||||||||||||||||||||||||||||
< < | The following namespace prefixes are used to refere to other models | ||||||||||||||||||||||||||||||||||
> > | The following namespace prefixes are used to refer to other models | ||||||||||||||||||||||||||||||||||
class SNAPResource | |||||||||||||||||||||||||||||||||||
Changed: | |||||||||||||||||||||||||||||||||||
< < | blabla | ||||||||||||||||||||||||||||||||||
> > | ... | ||||||||||||||||||||||||||||||||||
class SNAPProtocol extends SNAPResource | |||||||||||||||||||||||||||||||||||
Added: | |||||||||||||||||||||||||||||||||||
> > | 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. | ||||||||||||||||||||||||||||||||||
class SNAPSimulator extends SNAPProtocolclass SNAPExperiment extends SNAPResource | |||||||||||||||||||||||||||||||||||
Changed: | |||||||||||||||||||||||||||||||||||
< < | ... | ||||||||||||||||||||||||||||||||||
> > | The base class for those kinds of experiments that can produce representations of a part of the universe. It is an experiment in the sense as defined in the analysis model and in the original domain model. | ||||||||||||||||||||||||||||||||||
Added: | |||||||||||||||||||||||||||||||||||
> > | |||||||||||||||||||||||||||||||||||
class SNAPSimulation extends SNAPExperimentclass SNAPPostProcessing extends SNAPExperimentclass SNAPProject extends SNAPResource<--
|
SNAP data model, online docThis page gives the Wiki version of the documentation for the model and wil supplant that document. See the following links for and Below we list all the classes in the UML diagram. We use the definitions in this pageTable of Contents for classes[TBD Order Alphabetically]
| |||||||||||||||||||||||||||||
Changed: | |||||||||||||||||||||||||||||
< < |
| ||||||||||||||||||||||||||||
> > |
| ||||||||||||||||||||||||||||
The following namespace prefixes are used to refere to other models
class SNAPResourceblabla | |||||||||||||||||||||||||||||
Changed: | |||||||||||||||||||||||||||||
< < |
| ||||||||||||||||||||||||||||
> > |
| ||||||||||||||||||||||||||||
Added: | |||||||||||||||||||||||||||||
> > |
| ||||||||||||||||||||||||||||
class SNAPProtocol extends SNAPResource | |||||||||||||||||||||||||||||
Changed: | |||||||||||||||||||||||||||||
< < |
| ||||||||||||||||||||||||||||
> > |
| ||||||||||||||||||||||||||||
Added: | |||||||||||||||||||||||||||||
> > |
| ||||||||||||||||||||||||||||
Changed: | |||||||||||||||||||||||||||||
< < | class SNAPSimulator extendsSNAPProtocol | ||||||||||||||||||||||||||||
> > | class SNAPSimulator extends SNAPProtocol | ||||||||||||||||||||||||||||
Changed: | |||||||||||||||||||||||||||||
< < | class SNAPExperiment extendsSNAPResource | ||||||||||||||||||||||||||||
> > | class SNAPExperiment extends SNAPResource | ||||||||||||||||||||||||||||
... | |||||||||||||||||||||||||||||
Changed: | |||||||||||||||||||||||||||||
< < |
| ||||||||||||||||||||||||||||
> > |
| ||||||||||||||||||||||||||||
Added: | |||||||||||||||||||||||||||||
> > |
| ||||||||||||||||||||||||||||
Changed: | |||||||||||||||||||||||||||||
< < | class SNAPSimulation extendsSNAPExperiment | ||||||||||||||||||||||||||||
> > | class SNAPSimulation extends SNAPExperiment | ||||||||||||||||||||||||||||
Changed: | |||||||||||||||||||||||||||||
< < | class SNAPPostProcessing extendsSNAPExperiment | ||||||||||||||||||||||||||||
> > | class SNAPPostProcessing extends SNAPExperiment | ||||||||||||||||||||||||||||
Changed: | |||||||||||||||||||||||||||||
< < | class SNAPProject extendsSNAPResource | ||||||||||||||||||||||||||||
> > | class SNAPProject extends SNAPResource | ||||||||||||||||||||||||||||
<--
|
SNAP data model, online doc | |||||||||||||||||||||||||||||
Changed: | |||||||||||||||||||||||||||||
< < | This page gives the Wiki version of the documentation for the model. See the following links for latest UML version and latest XML schema document | ||||||||||||||||||||||||||||
> > | This page gives the Wiki version of the documentation for the model and wil supplant that document. | ||||||||||||||||||||||||||||
Added: | |||||||||||||||||||||||||||||
> > | See the following links for and | ||||||||||||||||||||||||||||
Below we list all the classes in the UML diagram.
We use the definitions in this page
Table of Contents for classes[TBD Order Alphabetically]
| |||||||||||||||||||||||||||||
Changed: | |||||||||||||||||||||||||||||
< < | SNAPResource | ||||||||||||||||||||||||||||
> > | Template table
| ||||||||||||||||||||||||||||
Added: | |||||||||||||||||||||||||||||
> > |
| ||||||||||||||||||||||||||||
Changed: | |||||||||||||||||||||||||||||
< < | SNAPProtocol extends SNAPResource | ||||||||||||||||||||||||||||
> > | The following namespace prefixes are used to refere to other models
| ||||||||||||||||||||||||||||
Added: | |||||||||||||||||||||||||||||
> > |
| ||||||||||||||||||||||||||||
Deleted: | |||||||||||||||||||||||||||||
< < | SNAPSimulator extends SNAPProtocol | ||||||||||||||||||||||||||||
Changed: | |||||||||||||||||||||||||||||
< < | SNAPExperiment extends SNAPResource | ||||||||||||||||||||||||||||
> > |
class SNAPResource | ||||||||||||||||||||||||||||
Added: | |||||||||||||||||||||||||||||
> > | blabla | ||||||||||||||||||||||||||||
Changed: | |||||||||||||||||||||||||||||
< < | SNAPSimulation extends SNAPExperiment | ||||||||||||||||||||||||||||
> > |
| ||||||||||||||||||||||||||||
Added: | |||||||||||||||||||||||||||||
> > |
| ||||||||||||||||||||||||||||
Changed: | |||||||||||||||||||||||||||||
< < | SNAPPostProcessing extends SNAPExperiment | ||||||||||||||||||||||||||||
> > |
class SNAPProtocol extends SNAPResource | ||||||||||||||||||||||||||||
Added: | |||||||||||||||||||||||||||||
> > |
| ||||||||||||||||||||||||||||
Changed: | |||||||||||||||||||||||||||||
< < | SNAPProject extends SNAPResource | ||||||||||||||||||||||||||||
> > |
class SNAPSimulator extendsSNAPProtocol | ||||||||||||||||||||||||||||
Added: | |||||||||||||||||||||||||||||
> > |
class SNAPExperiment extendsSNAPResource...
class SNAPSimulation extendsSNAPExperimentclass SNAPPostProcessing extendsSNAPExperimentclass SNAPProject extendsSNAPResource | ||||||||||||||||||||||||||||
<--
|
SNAP data model, online docThis page gives the Wiki version of the documentation for the model.<--
|