Skip to content

Support having multiple operational limits groups active at the same time #1356

@alicecaron

Description

@alicecaron

Describe the current behavior

Within a security analysis only one operational limits groups among the active ones is used to check for limit violations.

Describe the expected behavior

Within a security analysis all the active operational limits groups are used to check for limit violations.

Describe the motivation

Since issue core#3703 it is possible to have several active operational limits groups at the same time to check for limits violations, we want to be able to check for all the active groups not only one as before when only one "selected" operational limits group was possible.

Extra Information

  • is blocked by issue core#3703 that model the LimitReduction list of groups on which the reduction should be applied.
  • loop on the active operational limits groups when checking for limit violations in pre contingency, post contingencies and post contingencies after actions (in LimitViolationManager:detectViolations ?). Limit reductions are given in the 3 usages of the method

Metadata

Metadata

Assignees

No one assigned

    Projects

    Status

    TODO

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions