Minimal support of limit reductions for security analysis #1011
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: Anne Tilloy <anne.tilloy@rte-france.com>
Signed-off-by: Anne Tilloy <anne.tilloy@rte-france.com>
Signed-off-by: Anne Tilloy <anne.tilloy@rte-france.com>
olperr1
requested changes
Apr 11, 2024
src/main/java/com/powsybl/openloadflow/network/impl/LfSwitch.java
Outdated
Show resolved
Hide resolved
src/main/java/com/powsybl/openloadflow/network/impl/LfDanglingLineBranch.java
Outdated
Show resolved
Hide resolved
src/main/java/com/powsybl/openloadflow/sa/LimitReductionManager.java
Outdated
Show resolved
Hide resolved
src/main/java/com/powsybl/openloadflow/network/impl/LfBranchImpl.java
Outdated
Show resolved
Hide resolved
…tions Signed-off-by: Olivier Perrin <olivier.perrin@rte-france.com>
Signed-off-by: Olivier Perrin <olivier.perrin@rte-france.com>
Signed-off-by: Olivier Perrin <olivier.perrin@rte-france.com>
Signed-off-by: Olivier Perrin <olivier.perrin@rte-france.com>
Signed-off-by: Olivier Perrin <olivier.perrin@rte-france.com>
Signed-off-by: Olivier Perrin <olivier.perrin@rte-france.com>
olperr1
force-pushed
the
limit-reductions
branch
from
4bdbba1
to
213a6e1
Compare
Signed-off-by: Olivier Perrin <olivier.perrin@rte-france.com>
olperr1
reviewed
Apr 25, 2024
src/main/java/com/powsybl/openloadflow/sa/LimitReductionManager.java
Outdated
Show resolved
Hide resolved
Co-authored-by: Olivier Perrin <olivier.perrin@rte-france.com> Signed-off-by: Anne Tilloy <48123713+annetill@users.noreply.github.com>
Signed-off-by: Olivier Perrin <olivier.perrin@rte-france.com>
rosiereflo
requested changes
Apr 30, 2024
src/main/java/com/powsybl/openloadflow/network/impl/AbstractLfBranch.java
Outdated
Show resolved
Hide resolved
src/main/java/com/powsybl/openloadflow/network/impl/AbstractLfBranch.java
Outdated
Show resolved
Hide resolved
src/main/java/com/powsybl/openloadflow/sa/LimitReductionManager.java
Outdated
Show resolved
Hide resolved
Signed-off-by: Olivier Perrin <olivier.perrin@rte-france.com>
rosiereflo
approved these changes
May 6, 2024
# Conflicts: # src/main/java/com/powsybl/openloadflow/network/LfBranch.java # src/main/java/com/powsybl/openloadflow/network/impl/LfDanglingLineBranch.java # src/main/java/com/powsybl/openloadflow/network/impl/LfLegBranch.java # src/main/java/com/powsybl/openloadflow/network/impl/LfTieLineBranch.java # src/main/java/com/powsybl/openloadflow/sa/AbstractSecurityAnalysis.java # src/test/java/com/powsybl/openloadflow/sa/OpenSecurityAnalysisTest.java
|
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, it is the support of a new feature from
powsybl-core 6.3.0. In that PR, we only support a minimal feature, without relying on utility methods available in core. But we can imagine testing this approach and with utility methods in order to compare results and performances (on core side, could be a problem).What kind of change does this PR introduce?
What is the current behavior?
What is the new behavior (if this is a feature change)?
Does this PR introduce a breaking change or deprecate an API?
If yes, please check if the following requirements are fulfilled
What changes might users need to make in their application due to this PR? (migration steps)
Other information: