Security analysis: monitored elements power threshold changed to absolute#3980
Merged
Conversation
…lute Signed-off-by: Damien Jeandemange <damien.jeandemange@artelys.com>
jeandemanged
requested review from
HugoKulesza,
SylvestreSakti and
olperr1
and removed request for
HugoKulesza
SylvestreSakti
approved these changes
Jun 26, 2026
|
olperr1
approved these changes
Jun 29, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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?
Related: #3903
What kind of change does this PR introduce?
Feature but only via documentation update.
As part of the current June 26 release,
powerModificationThresholdintroduced in #3903 is documented as a relative/percentage filter. After discussions in powsybl/powsybl-open-loadflow#1398 and implementing the filter, it was agreed to change the filter to be in absolute MW/MVAr, instead of a relative threshold.Actual usage of the parameter is only within security analysis implementations (e.g. OLF). Therefore this PR is a documentation only change for powsybl-core (readthedocs and javadoc).
What is the current behavior?
powerModificationThresholddocumented as being a relative filterWhat is the new behavior (if this is a feature change)?
powerModificationThresholddocumented as being an absolute MW/MVAr filter (readthedocs and javadoc)Does this PR introduce a breaking change or deprecate an API?
Other information:
The original doc had very long lines. I added line breaks but did not modify the content for the parts not relevant to this PR.