You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/1___overview.adoc
+1-2Lines changed: 1 addition & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -4,7 +4,7 @@ SSP is a tool-independent format for the description, packaging and exchange of
4
4
The standard is comprised of a set of XML-based formats to describe a network of component models with their signal flow and parametrization, as well as a ZIP-based packaging format for efficient distribution of entire systems, including any referenced models and other resources.
5
5
This description is tool neutral and is intended to be used primarly as an exchange format of simulation system descriptions between different tools.
6
6
7
-
SSP can be seen as an extension to the FMI (Functional Mockup Interface) standard [FMI20].
7
+
SSP can be seen as an extension to the FMI (Functional Mockup Interface) standard [FMI30].
8
8
FMI describes a tool independent standard to exchange single simulation models.
9
9
Using SSP, complete systems consisting of multiple interconnected simulation models can be defined with the desired signal flow and also with the wanted parameterization of each single model as well as the parameters for the complete system.
10
10
This system topology can include hierarchies of sub-systems for proper structuring of the overall system.
@@ -52,7 +52,6 @@ From a simulation perspective, each component has to be described with its input
52
52
This can be done using SSP by defining the wrapper of this component with an empty Component element comprising the connectors for the inputs and outputs and the component's parameters.
53
53
54
54
The interaction of the components is defined by the connections.
55
-
Connections in SSP are always causal.
56
55
Connections can be made directly between components or via signal dictionaries.
57
56
A signal dictionary is a collection of signals similar to a bus concept (e.g. like a CAN bus).
58
57
During the design phase of a system, a signal dictionary can be a good way to predefine the available signal connections.
Copy file name to clipboardExpand all lines: docs/4___common_content.adoc
+8-6Lines changed: 8 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -136,7 +136,7 @@ The following XML child elements are specified for the Unit element:
136
136
===== BaseUnit
137
137
138
138
This element defines the base unit of the given unit in SI units.
139
-
This is completely aligned with the specification of base units in section 2.2.2 of the FMI 2.0 standard [FMI20].
139
+
This is completely aligned with the specification of base units in section 2.4.3 of the FMI 3.0 standard [FMI30] and section 2.2.2 of the FMI 2.0 standard [FMI20].
This type specifies that the connector in question represents a length-terminated binary data type, like the binary type defined for the FMI 3.0 standard, or substitute types like the binary type defined via the OSI Sensor Model Packaging specification [OSMP120].
315
+
This type specifies that the connector in question represents a length-terminated binary data type, like the binary type defined for the FMI 3.0 standard, or substitute types like the binary type defined via the OSI Sensor Model Packaging specification [OSMP150].
316
316
317
317
[width="100%",cols="28%,72%",options="header",]
318
318
|===
@@ -466,13 +466,15 @@ This attribute references another connector by name, that gives the size of this
This element contains information of a default simulation setup that is supplied with the system definition for informational purposes.
44
44
45
-
{empty}[ _Note that in contrast to FMI 2.0 only start and stop time are specified here, since values like step size or tolerance depend on the specific solver or master algorithms employed and are hence not specified in this global element._
45
+
{empty}[ _Note that in contrast to FMI 2.0/3.0 only start and stop time are specified here, since values like step size or tolerance depend on the specific solver or master algorithms employed and are hence not specified in this global element._
46
46
_Additional solver or master algorithm specific information can be supplied through the annotation mechanism, or using a future layered standard._ ]
47
47
48
48
{empty}[ _The handling of systems comprising components with differing units for the independent variable depends on the implementation._
This optional element specifies the set of connectors of this model element, which represent the interface of the model element to the outside world.
94
-
For components the set of connectors *MUST* match variables/ports of the underlying component implementation, e.g., for referenced FMI 2.0 FMUs, the name of a connector has to match the name attribute of the corresponding <ScalarVariable> element; for referenced FMUs that follow the OSI Sensor Model Packaging specification [OSMP120], the name of a connector of type Binary has to match the name attribute of the corresponding <osmp:osmp-binary-variable>.
94
+
For components the set of connectors *MUST* match variables/ports of the underlying component implementation, e.g., for referenced FMI 2.0 FMUs, the name of a connector has to match the name attribute of the corresponding <ScalarVariable> element; for referenced FMUs that follow the OSI Sensor Model Packaging specification [OSMP150], the name of a connector of type Binary has to match the name attribute of the corresponding <osmp:osmp-binary-variable>.
95
95
For FMI 3.0 FMUs, the connector name has to match either the name of the corresponding variable element, or one of its <Alias> elements.
96
96
97
97
Names of variable elements of an FMU might follow the “Variable Naming Conventions” specification as defined by the FMI standard.
98
-
Hence, several ScalarVariables might be grouped as a structure or an array.
99
-
However, the name of a connector *MUST* match the name of a single <ScalarVariable>.
98
+
Hence, several variables might be grouped as a structure or an array.
99
+
However, the name of a connector *MUST* match the name of a single variable.
100
100
101
101
Note that there is no requirement that connectors have to be present for all variables/ports of an underlying component implementation.
102
102
At least those connectors *MUST* be present which are referenced in connections inside the SSD.
@@ -410,7 +410,7 @@ For structural parameters it is assumed that the parameterization is applied in
410
410
This means that variables eligible for parameterization are those with:
411
411
412
412
* either causality = "input" or a start value for FMI 1.0
413
-
* variability != "constant" and initial = "exact" or "approx" for FMI 2.0
413
+
* variability != "constant" and initial = "exact" or "approx" for FMI 2.0/3.0
414
414
415
415
All kinds of system connectors can be parameterized.
416
416
In case the system level connectors are connected to FMU components, the parameterization *MUST* be compatible with the variable in the connected FMU.
0 commit comments