Repository navigation
Run me_cs FMUs with OMSimulator CS CVODE and Euler too - #379
Merged
Merged
Conversation
The FMI job builds every FMU once as me_cs and simulates it four ways: OMSimulator and FMPy through Model Exchange as before, and OMSimulator through Co-Simulation with CVODE and with Euler, filling <branch>-fmi-cs-cvode and <branch>-fmi-cs-euler. The C runtime reads its Co-Simulation solver from resources/<prefix>_flags.json when the FMU is instantiated, so switching solver needs no new build: an entry of fmi-simulators.json with fmiFlags runs a copy of the FMU whose flags file holds those flags. Asking for s:cvode in any entry builds the FMU with --fmiFlags=s:cvode, which is what links CVODE into it. Neither OMSimulator nor FMPy can be given an extracted FMU directory instead, OMSimulator always unzips it itself. An entry's interface is passed as OMSimulator --mode only for an me_cs FMU: OMSimulator defaults to Co-Simulation for those, and refuses --mode for an FMU exporting one interface, which the cs-fmu-cvode jobs build. Assisted-by: Claude Opus 5.5
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The FMI job builds every FMU once as me_cs and simulates it four ways: OMSimulator and FMPy through Model Exchange as before, and OMSimulator through Co-Simulation with CVODE and with Euler, filling -fmi-cs-cvode and -fmi-cs-euler.
The C runtime reads its Co-Simulation solver from
resources/_flags.json when the FMU is instantiated, so switching solver needs no new build: an entry of fmi-simulators.json with fmiFlags runs a copy of the FMU whose flags file holds those flags. Asking for s:cvode in any entry builds the FMU with --fmiFlags=s:cvode, which is what links CVODE into it. Neither OMSimulator nor FMPy can be given an extracted FMU directory instead, OMSimulator always unzips it itself.
An entry's interface is passed as OMSimulator --mode only for an me_cs FMU: OMSimulator defaults to Co-Simulation for those, and refuses --mode for an FMU exporting one interface, which the cs-fmu-cvode jobs build.
Assisted-by: Claude Opus 5.5