Skip to content
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

Merged
merged 4 commits into from
Jul 12, 2024
Merged

Conversation

bqth29
Copy link
Collaborator

@bqth29 bqth29 commented Jul 5, 2024

Please check if the PR fulfills these requirements

  • The commit message follows our guidelines
  • Tests for the changes have been added (for bug fixes / features)
  • Docs have been added / updated (for bug fixes / features)

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.

@bqth29 bqth29 added bug Something isn't working PR: waiting-for-review This PR is waiting to be reviewed labels Jul 5, 2024
@bqth29 bqth29 requested review from phiedw and murgeyseb July 5, 2024 07:30
@bqth29 bqth29 requested a review from pet-mit July 5, 2024 08:04
@@ -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);
Copy link
Collaborator

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?

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

(to check with Sebastien)

Copy link
Collaborator

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

Copy link
Collaborator

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?

@pet-mit pet-mit added the next-release This issue or pull request should be resolved before next release label Jul 9, 2024
@pet-mit pet-mit merged commit cadc5f1 into main Jul 12, 2024
10 checks passed
@pet-mit pet-mit deleted the fix/ofcc-triggered-after-all-outages branch July 12, 2024 08:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working next-release This issue or pull request should be resolved before next release PR: waiting-for-review This PR is waiting to be reviewed
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants