Adding automatic pause option to SimulationArgs#144
Merged
poorva1209 merged 1 commit intoGRIDAPPSD:developfrom May 1, 2024
Merged
Adding automatic pause option to SimulationArgs#144poorva1209 merged 1 commit intoGRIDAPPSD:developfrom
poorva1209 merged 1 commit intoGRIDAPPSD:developfrom
Conversation
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.
This change provides a solution for application testing issues when running against simulations running faster than real time.
To test and use in application testing:
The latest develop of the gridappsd platform must be used.
At a minimum create a Simulation class whose SimulationArgs.run_realtime=False and SimulationArgs.pause_after_measurements=True. The simulation should enter the paused state after each time it publishes measurements. When application testing, after receiving a measurements message from the Simulation instance Simulation.resume() will need to be called to move the simulation forward.