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
{{ message }}
This repository has been archived by the owner on Feb 10, 2022. It is now read-only.
According to recent discussion/clarification on standard interpretation, CS-FMUs must be able to handle "doStep()" calls gracefully, even if t+h > tEnd. This may happen due to rounding errors for both fixed and variable step FMUs. See also discussion in ticket modelica/fmi-standard#575
Currently, there are a few FMUs in the cross-check repo, that fail the last step when end time is exceeded. Importing tools cannot comply with those test cases, unless they ignore the "constant step size" property and adjust the last step manually. Therefore it may be meaningful to update these FMUs and in the mean time mark them 'notCompliantWithLatestRules'.
Here's a list of tools that export FMUs with strict end-time checking:
According to recent discussion/clarification on standard interpretation, CS-FMUs must be able to handle "doStep()" calls gracefully, even if
t+h > tEnd
. This may happen due to rounding errors for both fixed and variable step FMUs. See also discussion in ticket modelica/fmi-standard#575Currently, there are a few FMUs in the cross-check repo, that fail the last step when end time is exceeded. Importing tools cannot comply with those test cases, unless they ignore the "constant step size" property and adjust the last step manually. Therefore it may be meaningful to update these FMUs and in the mean time mark them 'notCompliantWithLatestRules'.
Here's a list of tools that export FMUs with strict end-time checking:
fmus/2.0/cs/linux64/JModelica.org/1.15/CoupledClutches
)(not complete, yet)
The text was updated successfully, but these errors were encountered: