Add possibility to optimize curative perimeter if preventive perimeter is unsecure and preventive stop criterion is SECURE #988
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
…ventive stop criterion is SECURE and preventive state unsecure. May be interesting if we want to avoid post-contingency flows reported in RAO result to be sometimes quite far from optimal, and hide real preventive/curative constraints. Signed-off-by: Sébastien Murgey <sebastien.murgey@rte-france.com>
murgeyseb
force-pushed
the
optimize-curative-if-preventive-unsecure
branch
from
103030e to
db3d400
Compare
pet-mit
requested changes
Apr 29, 2024
...src/main/java/com/powsybl/openrao/searchtreerao/castor/algorithm/CastorFullOptimization.java
Outdated
Show resolved
Hide resolved
...src/main/java/com/powsybl/openrao/searchtreerao/castor/algorithm/CastorFullOptimization.java
Outdated
Show resolved
Hide resolved
pet-mit
approved these changes
Apr 29, 2024
MartinBelthle
pushed a commit
that referenced
this pull request
May 28, 2024
…r is unsecure and preventive stop criterion is SECURE (#988) Signed-off-by: belthlemar <martin.belthle@rte-france.com>
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?
New feature
What is the new behavior (if this is a feature change)?
Add a new parameter to allow to run curative optimization even if preventive stop criterion is SECURE and preventive state unsecure. May be interesting if we want to avoid post-contingency flows reported in RAO result to be sometimes quite far from optimal, and hide real preventive/curative constraints.
Does this PR introduce a breaking change or deprecate an API?