Generator reference priorities

[jeandemanged]

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)

Does this PR already have an issue describing the problem?

No

What kind of change does this PR introduce?

Feature

What is the current behavior?

Angle reference bus is always the (first) slack bus.

What is the new behavior (if this is a feature change)?
Leverage powsybl/powsybl-core#2763

• Only for generator terminals as a first step
• Only in LoadFlow, not used in SA nor sensi
• new OLF parameters:
  • referenceBusSelectionMode with possible values
    • FIRST_SLACK (default, =current behavior): angle reference bus selected as the first slack bus among potentially multiple slacks
    • GENERATOR_REFERENCE_PRIORITY: angle reference bus selected from generator reference priorities
  • writeReferenceTerminals boolean to have reference generator(s) terminals written to the ReferenceTerminals iIDM extension

Does this PR introduce a breaking change or deprecate an API?
No

Other information:

[sonarqubecloud]

Quality Gate passed

Kudos, no new issues were introduced!

0 New issues
0 Security Hotspots
93.5% Coverage on New Code
0.4% Duplication on New Code

See analysis details on SonarCloud

[geofjamg]

@jeandemanged we can see in your PR that this feature is implemented for generators. It would be feasible to do it also for any injections and busbar sections but very hard for branches and probably useless. Why not in that case, restrict IIDM extension ReferencePriority and ReferenceTerminal to only terminal types that we want to support?

[jeandemanged]

@jeandemanged we can see in your PR that this feature is implemented for generators. It would be feasible to do it also for any injections and busbar sections but very hard for branches and probably useless. Why not in that case, restrict IIDM extension ReferencePriority and ReferenceTerminal to only terminal types that we want to support?

Fully agree, we can indeed restrict in core