-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Slack distribution support for DC power flow #183
Conversation
Signed-off-by: Anne Tilloy <anne.tilloy@rte-france.com>
Signed-off-by: Geoffroy Jamgotchian <geoffroy.jamgotchian@gmail.com>
Signed-off-by: Geoffroy Jamgotchian <geoffroy.jamgotchian@gmail.com>
private void distributeSlack(LfNetwork network) { | ||
double mismatch = network.getActivePowerMismatch(); | ||
ActivePowerDistribution activePowerDistribution = ActivePowerDistribution.create(parameters.getBalanceType(), false); | ||
activePowerDistribution.run(network, -mismatch); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe we shoud invert the sign of Network.getActivePowerMismatch to avoid this minus anf be consistent everywhere?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I have changed the sign. Do you think that I need to perform a functional validation ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I should be ok
Signed-off-by: Anne Tilloy <anne.tilloy@rte-france.com>
Kudos, SonarCloud Quality Gate passed! |
Please check if the PR fulfills these requirements (please use
'[x]'
to check the checkboxes, or submit the PR and then click the checkboxes)Does this PR already have an issue describing the problem ? If so, link to this issue using
'#XXX'
and skip the restSlack distribution was not supported before for DC power flow. The slack was entirely put at the slack node.
What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
Slack distribution is now supported for balance type PROPORTIONAL_TO_LOAD, PROPORTIONAL_TO_P_MAX and PROPORTIONAL_TO_CONFORM_LOAD. The power factor of loads is ignored as we are in a DC approximation. Looses are neglected. I need to add unit tests. A refactoring is needed for pre-distribution of slack used here and in the security analysis.
What is the current behavior? (You can also link to an open issue here)
What is the new behavior (if this is a feature change)?
Does this PR introduce a breaking change or deprecate an API? If yes, check the following:
Other information:
(if any of the questions/checkboxes don't apply, please delete them entirely)