User story: configure the continuity of service level

[xmirabel]

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

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	never stop the execution, even though any slave has a fatal error; in that case, it is automatically disabled; - production continuity of service: like it is today.
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.

  <OspSystemStructure [...]>
  ...
  <Simulators defaultContinuityOfService="full">
      <Simulator name="model1" familyContinuityOfService="production" source="model.fmu" stepSize="0.0005"/>
      <Simulator name="model2" source="model.fmu" stepSize="0.0005"/>
      ...
  </Simulators>
    ...
  </OspSystemStructure>