-
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
Fix PTC action support and support of RTC action #862
Conversation
Signed-off-by: Hadrien <[email protected]>
Signed-off-by: Hadrien <[email protected]>
Signed-off-by: Hadrien <[email protected]>
Signed-off-by: Hadrien <[email protected]>
Signed-off-by: Hadrien <[email protected]>
Signed-off-by: Hadrien <[email protected]>
Signed-off-by: Hadrien <[email protected]>
Signed-off-by: Hadrien <[email protected]>
Signed-off-by: Hadrien <[email protected]>
Signed-off-by: Anne Tilloy <[email protected]>
Signed-off-by: Anne Tilloy <[email protected]>
src/main/java/com/powsybl/openloadflow/ac/AcloadFlowEngine.java
Outdated
Show resolved
Hide resolved
Signed-off-by: Hadrien <[email protected]>
Signed-off-by: Hadrien <[email protected]>
Signed-off-by: Hadrien <[email protected]>
Signed-off-by: Hadrien <[email protected]>
Signed-off-by: Anne Tilloy <[email protected]>
@@ -523,15 +524,15 @@ public static <T> List<LfNetwork> load(T network, LfNetworkLoader<T> networkLoad | |||
return load(network, networkLoader, parameters, Reporter.NO_OP); | |||
} | |||
|
|||
public static <T> List<LfNetwork> load(T network, LfNetworkLoader<T> networkLoader, SlackBusSelector slackBusSelector, Reporter reporter) { |
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.
This removal is okay for me, to be confirmed by @geofjamg
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.
yes
Signed-off-by: Anne Tilloy <[email protected]>
src/test/java/com/powsybl/openloadflow/sa/OpenSecurityAnalysisWithActionsTest.java
Outdated
Show resolved
Hide resolved
Signed-off-by: Anne Tilloy <[email protected]>
Signed-off-by: Anne Tilloy <[email protected]>
Signed-off-by: Anne Tilloy <[email protected]>
Signed-off-by: Anne Tilloy <[email protected]>
src/main/java/com/powsybl/openloadflow/network/LfNetworkLoader.java
Outdated
Show resolved
Hide resolved
@@ -22,6 +22,10 @@ public class LfTopoConfig { | |||
|
|||
private final Set<String> busIdsToLose = new HashSet<>(); | |||
|
|||
private final Set<String> branchIdsWithPtcToRetain = new HashSet<>(); |
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.
For later, but maybe we should find a better name for LfTopoConfig once this will be added?
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.
We can do it now, shunt compensator action is coming just after, what do you suggest ?
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.
Could be a LfNetworkLoadingParameters
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 think we can leave it like this and re-think about it with shunt compensator action.
src/main/java/com/powsybl/openloadflow/sa/AbstractSecurityAnalysis.java
Outdated
Show resolved
Hide resolved
src/main/java/com/powsybl/openloadflow/sa/AbstractSecurityAnalysis.java
Outdated
Show resolved
Hide resolved
Signed-off-by: Damien Jeandemange <[email protected]>
Signed-off-by: Damien Jeandemange <[email protected]>
Kudos, SonarCloud Quality Gate passed! |
Signed-off-by: Hadrien <[email protected]> Co-authored-by: Anne Tilloy <[email protected]> Co-authored-by: Damien Jeandemange <[email protected]>
Signed-off-by: Hadrien <[email protected]> Co-authored-by: Anne Tilloy <[email protected]> Co-authored-by: Damien Jeandemange <[email protected]>
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?
Bugfix
What is the current behavior?
Currently, PTC and RTC PI model does not include tap positions if regulation is deactivated. This is an issue if the PST or RTC is involved in operator strategies / actions.
What is the new behavior (if this is a feature change)?
This PR allows PTC and RTC to be retained also when they are involved in operator strategies / actions.
With this PR, PTC and RTC pimodel contains tap positions if the PTC and RTC is involved not only in regulation but also in at least one action in a security analysis run.
Does this PR introduce a breaking change or deprecate an API?
No
Other information:
none