Fix DC Load Flow running slack distribution for epsilon mismatch#1389
Open
jeandemanged wants to merge 1 commit intomainfrom
Open
Fix DC Load Flow running slack distribution for epsilon mismatch#1389jeandemanged wants to merge 1 commit intomainfrom
jeandemanged wants to merge 1 commit intomainfrom
Conversation
Signed-off-by: Damien Jeandemange <damien.jeandemange@artelys.com>
|
jeandemanged
commented
Apr 24, 2026
|
|
||
| LoadFlowParameters loadFlowParameters = new LoadFlowParameters() | ||
| .setDc(true) | ||
| .setHvdcAcEmulation(false); |
Member
Author
There was a problem hiding this comment.
to not have the outerloop in the report, but probably a fix to do in another PR to not create the outerloop if no HVDC in DC emulation in the network
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
1 participant
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
What is the current behavior?
In DC Load Flow slack distribution is always performed.
If the mismatch is epsilonesque (lower than P_RESIDUE_EPS=1e-3 MW) this is an unnecessary slack distribution and generates slack distribution reports + logs.
Especially annoying in DC security analysis where each and every contingency not causing an injection loss issues a report+ log showing zero or near zero mismatch distributions.
What is the new behavior (if this is a feature change)?
DC Load Flow slack distribution is executed only if mismatch is above epsilon (P_RESIDUE_EPS).
Does this PR introduce a breaking change or deprecate an API?