Add configuration of reactive slacks repartition

[p-arvy]

…ode.

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?

20

What kind of change does this PR introduce?

The high limit on reactive slack variables is removed. Slacks are now at each node of the network.

What is the current behavior?

The reactive slack variables have upper bound = 500 MVar. Only buses without generator, vsc and svc have reactive slacks.

What is the new behavior (if this is a feature change)?

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

• [ ] The Breaking Change or Deprecated label has been added
• [ ] The migration guide has been updated in the github wiki (What changes might users need to make in their application due to this PR?)

Other information:

[sonarcloud[bot]]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

97.6% Coverage
0.0% Duplication