Fix second preventive scenario #874
Merged
Conversation
This file contains 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
Signed-off-by: belthlemar <[email protected]>
Signed-off-by: Philippe Edwards <[email protected]>
Signed-off-by: Peter Mitri <[email protected]>
pet-mit
added
bug
phiedw
approved these changes
Jan 25, 2024
MartinBelthle
pushed a commit
that referenced
this pull request
May 28, 2024
Fix second preventive scenario Signed-off-by: belthlemar <[email protected]>
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.
Please check if the PR fulfills these requirements
What kind of change does this PR introduce?
Bug fix
What is the current behavior?
The fixes in #866 reset the network used in 2nd preventive RAO to initial state before last load flow computation. However, if the 2nd preventive is not global, this makes it lose PST taps that were copied from the 1st preventive result.
What is the new behavior (if this is a feature change)?
Now the network is reset to the situation before 2nd PRAO, which contains 1st PRAO PST taps.
Does this PR introduce a breaking change or deprecate an API?