Add switch actions in Fast DC Security Analysis #1153
Conversation
Signed-off-by: p-arvy <pierre.arvy@artelys.com>
…ngine Signed-off-by: p-arvy <pierre.arvy@artelys.com>
Signed-off-by: p-arvy <pierre.arvy@artelys.com>
…rrent tap Signed-off-by: p-arvy <pierre.arvy@artelys.com>
# Conflicts: # src/main/java/com/powsybl/openloadflow/dc/fastdc/WoodburyEngine.java # src/main/java/com/powsybl/openloadflow/sa/WoodburyDcSecurityAnalysis.java
Signed-off-by: p-arvy <pierre.arvy@artelys.com>
Signed-off-by: p-arvy <pierre.arvy@artelys.com>
This comment was marked as resolved.
This comment was marked as resolved.
|
Signed-off-by: p-arvy <pierre.arvy@artelys.com>
Signed-off-by: p-arvy <pierre.arvy@artelys.com>
Signed-off-by: Hadrien <hadrien.godard@artelys.com>
src/main/java/com/powsybl/openloadflow/dc/fastdc/ConnectivityBreakAnalysis.java
Outdated
Show resolved
Hide resolved
Signed-off-by: p-arvy <pierre.arvy@artelys.com>
Signed-off-by: p-arvy <pierre.arvy@artelys.com>
Signed-off-by: Hadrien <hadrien.godard@artelys.com>
src/test/java/com/powsybl/openloadflow/sa/WoodburyDcSecurityAnalysisWithActionsTest.java
Outdated
Show resolved
Hide resolved
src/main/java/com/powsybl/openloadflow/dc/fastdc/ComputedSwitchBranchElement.java
Show resolved
Hide resolved
src/main/java/com/powsybl/openloadflow/dc/fastdc/ComputedSwitchBranchElement.java
Outdated
Show resolved
Hide resolved
src/main/java/com/powsybl/openloadflow/dc/fastdc/ConnectivityBreakAnalysis.java
Outdated
Show resolved
Hide resolved
src/main/java/com/powsybl/openloadflow/dc/fastdc/AbstractComputedElement.java
Outdated
Show resolved
Hide resolved
Signed-off-by: Hadrien <hadrien.godard@artelys.com>
| /** | ||
| * Returns true if the given contingency and operator strategy actions potentially break connectivity. | ||
| * This is determined with a "worst case" sensitivity-criterion. If the criterion is not verified, there is no connectivity break. | ||
| */ |
There was a problem hiding this comment.
What is exactly this "worst-case" sensitivity criterion ? I'm not sure what is meant here.
There was a problem hiding this comment.
Do you mean that isGroupOfElementsBreakingConnectivity is a heuristic that may return true when connectivity is not acutally broken, and to minimize this risk you should not provide switches that are going to be open ?
There was a problem hiding this comment.
It means that if the criterion is verified then there might be a connectivity break. If it is not verified then we are sure there is no connectivity break. It is a conservative approach. @p-arvy , if I am wrong on this point, correct me.
There was a problem hiding this comment.
Yes, that's exactly it @Hadrien-Godard.
Signed-off-by: Hadrien <hadrien.godard@artelys.com>
|
Please check if the PR fulfills these requirements
Does this PR already have an issue describing the 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: