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
It should be possible to avoid, by configuration, simulation experiment stopping because of a model fatal error, in order to be able to disengage the concerned model, debug it and then reengage it at the same point of the experiment.
DESCRIPTION
As a
OSP user
I want to
be able to configure the continuity of service level for the whole execution (the default one), or a given slave family. The choice is at least among: - full continuity of service
So that
a specific continuity of service level is applied to any slave family, when specified, or else, a default continuity of service level is applied to the others.
EXAMPLE OF CONFIGURATION SYNTAX
In the OspSystemStructure XML structure:
a new optional attribute of "Simulators" called "defaultContinuityOfService" should allow to choose between "production" (the default one) and "full" ;
a new optional attribute of "Simulator" called "familyContinuityOfService" should allow to choose between "production" (the default one) and "full": in this case, the simulator family (all instance of the same the fmu) is set ;
When familyContinuityOfService is specified for one instance of a family, it has priority under default value of the other instances of the family.
NEED
It should be possible to avoid, by configuration, simulation experiment stopping because of a model fatal error, in order to be able to disengage the concerned model, debug it and then reengage it at the same point of the experiment.
DESCRIPTION
EXAMPLE OF CONFIGURATION SYNTAX
In the OspSystemStructure XML structure:
When familyContinuityOfService is specified for one instance of a family, it has priority under default value of the other instances of the family.
The text was updated successfully, but these errors were encountered: