Static SystemConfig
SystemConfig files are optional. They describe static configurations of agents and are therefore an alternative to the dynamic sampling of an agent during runtime. The schema is the same as for the SystemConfigBlueprint.
SSP
One usecase for the static SystemConfig is System Structure and Parameterization (SSP). We use SSP to chain multiple FMUs together, which transfer data between them during one time step. SSP is added to the SystemConfig like any other Component. It requires the following parameters:
Tag |
Description |
Mandatory |
---|---|---|
id |
Id should be set to “SspPath” |
yes |
type |
type should be string |
yes |
unit |
not used |
no |
value |
relative path to the ssp file relative to the configuration path |
yes |
Example
<component doc="SSP">
<id>SSP1</id>
<schedule>
<priority>50</priority>
<offset>0</offset>
<cycle>100</cycle>
<response>0</response>
</schedule>
<library>Algorithm_SspWrapper</library>
<parameters>
<parameter>
<id>SspPath</id>
<type>string</type>
<unit/>
<value>ConnectionTest.ssp</value>
</parameter>
</parameters>
</component>
Connecting SSP with OpenPass
During OpenPass Simulation, information is communicated via osi messages between the Simulation Core and SSP. Like any other component communication, these connections need to be explicitly declared as connections in the SystemConfig. One connection is defined with the following attributes:
Tag |
Description |
Mandatory |
---|---|---|
id |
unique identifier for connection |
yes |
source |
pair of sending agent component and local link id |
yes |
target |
pair of receiving agent component and local link id |
yes |
Example
<connection doc="SSP">
<id>502</id>
<source>
<component>SSP1</component>
<output>0</output>
</source>
<target>
<component>PrioritizerDynamics</component>
<input>1</input>
</target>
</connection>