DC load contingency #362
Merged
DC load contingency #362
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: Hadrien <hadrien.godard@artelys.com>
Signed-off-by: Hadrien <hadrien.godard@artelys.com>
Signed-off-by: Hadrien <hadrien.godard@artelys.com>
Signed-off-by: Hadrien <hadrien.godard@artelys.com>
Signed-off-by: Hadrien <hadrien.godard@artelys.com>
annetill
reviewed
Oct 1, 2021
src/main/java/com/powsybl/openloadflow/network/impl/LfLoads.java
Outdated
Show resolved
Hide resolved
annetill
reviewed
Oct 1, 2021
src/main/java/com/powsybl/openloadflow/sensi/DcSensitivityAnalysis.java
Outdated
Show resolved
Hide resolved
Signed-off-by: Anne Tilloy <anne.tilloy@rte-france.com>
…ybl-open-loadflow into dc_load_contingency
Signed-off-by: Anne Tilloy <anne.tilloy@rte-france.com>
Signed-off-by: Hadrien <hadrien.godard@artelys.com>
PR is functionally correct, implementation improvements are needed Signed-off-by: Hadrien <hadrien.godard@artelys.com>
Signed-off-by: Hadrien <hadrien.godard@artelys.com>
annetill
reviewed
Oct 6, 2021
src/main/java/com/powsybl/openloadflow/sensi/DcSensitivityAnalysis.java
Outdated
Show resolved
Hide resolved
Signed-off-by: Anne Tilloy <anne.tilloy@rte-france.com>
annetill
reviewed
Oct 6, 2021
src/main/java/com/powsybl/openloadflow/sensi/DcSensitivityAnalysis.java
Outdated
Show resolved
Hide resolved
…n case of a slack distributed on loads Signed-off-by: Hadrien <hadrien.godard@artelys.com>
Signed-off-by: Anne Tilloy <anne.tilloy@rte-france.com>
|
Kudos, SonarCloud Quality Gate passed! |
phiedw
reviewed
Nov 9, 2021
| .collect(Collectors.toList()); | ||
| normalizeParticipationFactors(newParticipatingElements, "LfGenerators"); | ||
| } else { // slack distribution on loads. | ||
| newParticipatingElements = getParticipatingElements(lfNetwork.getBuses(), lfParameters, lfParametersExt); |
There was a problem hiding this comment.
Can we not simply call normalizeParticipationFactors here instead of recomputing the participating elements?
There was a problem hiding this comment.
As a participating element is a bus and not directly the element in contingency, it was easier this way. But it could work even if the bus is included with a load target P equals to zero. I am going to try!
|
Kudos, SonarCloud Quality Gate passed! |
annetill
approved these changes
Dec 3, 2021
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 (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 restWhat kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
This PR introduces contingency on load for DC sensitivity and reference flows computations
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)