Corrected stimulus preparation and update for cosimulator.py#672
Open
Corrected stimulus preparation and update for cosimulator.py#672
Conversation
…tep-1 instead of step-(current_step+1)
dionperd
changed the title
Member
|
hi @dionperd, I'm a bit late for this one. still relevant for merging? will you rebase as Lia suggested? |
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
3 participants
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.
I moved the _prepare_stimulus() method call to the configuration of the CoSimulator, because during co-simulation the simulation_length is modified and equalized with the synchronization_time, leading to an erroneous reconfiguration of the stimulus in time.
I added an _current_stimulus property to the CoSimulator, in order to keep the stimulus between calles to call() method.
I also overwrote the _loop_update_stimulus method to use
stim_step=step-1
instead of stim_step=step-(current_step+1)
because current_step is updated evey synchronization time at each call().