Support having multiple active operational limits group #1345
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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?
powsybl-core PR powsybl/powsybl-core#3735 will introduce multiple operational limits groups. This current PR aims at supporting this new functionnality.
What is the current behavior?
Only one operational limits group can be selected
What is the new behavior (if this is a feature change)?
Multiple operational limits group can be selected. A new class LfLimitsGroup (which only contains a list of LfLimit objects) has been introduced to avoid using nested lists.
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)
For custom open-loadflow implementation using LfNetwork, the LfBranch API has been modified :
getLimits1()andgetLimits2()return now aList<LfLimitsGroup>instead of aList<LfLimit>Other information: