Join GitHub today
GitHub is home to over 31 million developers working together to host and review code, manage projects, and build software together.Sign up
Rework fmi3Discard mechanism for DoStep #535
As discussed in the design meeting on 2019-02-13:
The current definition of fmi3Discard only allows restarting of the calculation if full-fledged fmi3Get/SetFMUState support is present. Since fmi3SetFMUState can already be called in terminated/error state, fmi3Discard does not provide more of a potential mechanism for resuming than fmi3Error (except for the indication of the actual reason for the error).
However it is rather more likely that implementations can more easily support reseting the FMU state to the state when entering the fmi3DoStep on a failed step, than having full fledged fmi3SetFMUState support.
Therefore the definitions should be changed, so that:
To be decided: Add a new fmi3-Return Value to indicate that the failed fmi3DoStep is due to not being able to complete the step, and not some other error (e.g. fmi3StepFailed).
FMI Design Meeting in Regensburg:
The side effects have to be discussed in more detail.