-
Notifications
You must be signed in to change notification settings - Fork 50
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
Add some stats on SSP model executions #913
Comments
@jph-tavella I also think those stats would be useful. Stay tuned 😀 |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Maybe could be attached to future OMSimulator work plan being defined between EDF & OSMC? |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
@lochel: on 26 Feb 2021 you commented these stats would be useful. Do you have any target date for delivering them in the tools? |
WIP |
When the user runs a SSP model containing several FMUs, some stats on this execution should be interesting for him/her to tune the model.
According to the FMI standard, some states are defined in the state machine of the FMI for Co-Simulation.
Main states are:
It should be interesting to calculate and report the time spent on each of these states, at least for all FMUs (possibly for each FMU too).
In addition for the stepping state, the number of doStep() and the number of rollbacks should be also helpful (peraphs also the minimum and maximum step size too).
The text was updated successfully, but these errors were encountered: