New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Reset eventInfo only on entering event mode #959
Reset eventInfo only on entering event mode #959
Conversation
I added a test that validates the results with the FMUComplianceChecker for BouncingBall example. |
c9019cb
to
7bfcd3c
Compare
@sjoelund |
I'm not sure why you needed to create an additional stage for this. It's quite expensive to install all libraries and unstash a whole omc installation for one test. Make it part of the other stage instead. Also, the syntax of the Jenkinsfile is invalid. I gave you write access to the repository so Jenkins will trust your changes to the Jenkinsfile. |
Fix for ticket 5367. - `fmi2EnterEventMode` will reset `eventInfo`. Then the FMU integrator will set `newDiscreteStatesNeeded=fmi2True`. Inside fmi2NewDiscreteStates value for `valuesOfContinuousStatesChanged` will stay true if it becomes true at some point. - `valuesOfContinuousStatesChanged` can't trigger another call to `fmi2EventUpdate` any more. Would lead to infinit loop.
d9da06d
to
2e4c783
Compare
- Simulate bouncing ball model with fmuCheck and validate results. - Added test to cross-build-fmu in Jenkinsfile
b737e35
to
32a1985
Compare
I validated that my test is working with the new BouncingBall test: Can be merged 😀 |
Fix for ticket 5367.
fmi2EnterEventMode
will reseteventInfo
. Then the FMU integrator will setnewDiscreteStatesNeeded=fmi2True
.Inside fmi2NewDiscreteStates value for
valuesOfContinuousStatesChanged
will stay true if it becomes true at some point.valuesOfContinuousStatesChanged
can't trigger another call tofmi2EventUpdate
any more. Would lead to infinit loop.