[WIP] Fix slack distribution failing when remaining mismatch is negligible #1303
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.
Please check if the PR fulfills these requirements
Does this PR already have an issue describing the problem?
No
What kind of change does this PR introduce?
Bug fix (WIP : For the moment, only the test case is implemented)
What is the current behavior?
When all generators are at maxP after slackDistribution, some rare situations can have a very small residual slack mismatch. If this mismatch is still above P_RESIDUE_EPS, the slack distribution result is defined as fail. (And a log message shows : "Failed to distribute slack bus active power mismatch, 0.00 MW remains")
What is the new behavior (if this is a feature change)?
If the remaining mismatch is under slackBusPMaxMismatch, the result of slack distribution should be a success.
Does this PR introduce a breaking change or deprecate an API?