Skip to content

Give OMSimulator a step size when stopTime=startTime - #397

Merged
sjoelund merged 1 commit into
masterfrom
fmi-stepsize-zero-interval
Nov 6, 2026
Merged

sjoelund merged 1 commit into
masterfrom
fmi-stepsize-zero-interval

Conversation

@sjoelund

@sjoelund sjoelund commented Nov 6, 2026

Copy link
Copy Markdown
Member

For a model with stopTime=startTime the step size is 0. The testing then does not pass --stepSize, and OMSimulator uses the stepSize of the DefaultExperiment of the FMU, which is also 0. OMSimulator v3 refuses it ("The stepSize must be greater than 0, but got 0.0"), so 104 rows of master-fmi-cs-cvode (and the same in master-fmi) failed before the simulation started. FMPy runs them.

There is no step in such a simulation, so give a step size of 1. Both OMSimulator and FMPy then write the result at startTime.

Assisted-by: Claude Opus 5.5

For a model with stopTime=startTime the step size is 0. The testing
then does not pass --stepSize, and OMSimulator uses the stepSize of the
DefaultExperiment of the FMU, which is also 0. OMSimulator v3 refuses
it ("The stepSize must be greater than 0, but got 0.0"), so 104 rows of
master-fmi-cs-cvode (and the same in master-fmi) failed before the
simulation started. FMPy runs them.

There is no step in such a simulation, so give a step size of 1. Both
OMSimulator and FMPy then write the result at startTime.

Assisted-by: Claude Opus 5.5
@sjoelund
sjoelund enabled auto-merge (squash) November 6, 2026 18:31
@sjoelund
sjoelund merged commit 68bc7e1 into master Nov 6, 2026
7 checks passed
@sjoelund
sjoelund deleted the fmi-stepsize-zero-interval branch November 6, 2026 19:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant