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
Reported by beutlich on 5 Aug 2016 11:38 UTC
If a Modelica tool calls ModelicaStandardTables_CombiTimeTable_nextTimeEvent too often for a CombiTimeTable with periodic extrapolation, the internal states of the external table object (especially the offset and the event interval) are modified. Such a scenario happens e.g., for a restarted simulation of e.g., ModelicaTest.MultiBody.PlanarLoopWithMove). At the time of the table development (in spring 2013) the assumption was made that time is increasing only whereas a scenario of a restarted simulation was not considered. Hence, a restarted simulation can give wrong results for ModelicaStandardTables_CombiTimeTable_getValue.
beutlich
modified the milestones:
MSL_next-MINOR-version,
MSL_next-MAJOR-versionFeb 16, 2017
beutlich
changed the title
Restarted simulation of ComiTimeTable with periodic extrapolation can give wrong results
Restarted simulation of CombiTimeTable with periodic extrapolation can give wrong results
Apr 19, 2017
dietmarw
pushed a commit
to dietmarw/ModelicaStandardLibrary
that referenced
this issue
Oct 2, 2017
Reported by beutlich on 5 Aug 2016 11:38 UTC
If a Modelica tool calls
ModelicaStandardTables_CombiTimeTable_nextTimeEvent
too often for a CombiTimeTable with periodic extrapolation, the internal states of the external table object (especially the offset and the event interval) are modified. Such a scenario happens e.g., for a restarted simulation of e.g., ModelicaTest.MultiBody.PlanarLoopWithMove). At the time of the table development (in spring 2013) the assumption was made that time is increasing only whereas a scenario of a restarted simulation was not considered. Hence, a restarted simulation can give wrong results forModelicaStandardTables_CombiTimeTable_getValue
.Migrated-From: https://trac.modelica.org/Modelica/ticket/2040
The text was updated successfully, but these errors were encountered: