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
What kind of change does this PR introduce?
Feature
What is the current behavior?
Angle Monitoring uses CIM GLSK document to re-dipatch lost generation after stopping generators.
What is the new behavior (if this is a feature change)?
Now it should be able to use Scalable which is more generic.
Unfortunately, Scalable cannot be filtered like CimGLSKDocument: we need to exclude from the scaling generators that were stopped by the angle monitoring module when redispatching their production.
This requires the next release of powsybl that will add in scaling parameters a set of injections to ignore.
And also closes issue here: #890
Does this PR introduce a breaking change or deprecate an API?
What changes might users need to make in their application due to this PR? (migration steps)
AngleMonitoring API using CimGlskDocument is deprecated.
The users should convert the CimGlskDocument to a Scalable, using the Instant, and use the new API.