-
Notifications
You must be signed in to change notification settings - Fork 7
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 OFCC triggered after any outage #1078
Conversation
Signed-off-by: Thomas Bouquet <[email protected]>
Signed-off-by: Thomas Bouquet <[email protected]>
@@ -249,7 +249,7 @@ public Set<NetworkAction> getActivatedNetworkActions() { | |||
TopoAutomatonSimulationResult simulateTopologicalAutomatons(State automatonState, Network network, PrePerimeterSensitivityAnalysis preAutoPstOptimizationSensitivityAnalysis) { | |||
// -- Apply network actions | |||
// -- First get forced network actions | |||
Set<FlowCnec> flowCnecs = crac.getFlowCnecs(); | |||
Set<FlowCnec> flowCnecs = crac.getFlowCnecs(automatonState); |
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.
should we also check the curative cnecs on the same contingency?
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.
(to check with Sebastien)
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.
It is a good question... I would say no, but still have to check
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.
preparing for a release this afternoon or tomorrow morning, shall we include this fix?
Please check if the PR fulfills these requirements
What kind of change does this PR introduce?
A bug was reported from the SWE CC process where an OnFlowConstraintInCountry auto remedial action with no contingency defined was systematically triggered after all outages whereas only some of them were actually creating an overload in the given country.
What is the new behavior (if this is a feature change)?
The CNECs retrieved in the automaton simulator were not filtered on the state so this was corrected. Two Cucumber tests were added (one for ARA one for CRA) to ensure the problem is fixed.