Reduce irrealistic voltage created by remote voltage control #1135
Conversation
This file contains 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
vidaldid-rte
requested review from
geofjamg,
jeandemanged and
SylvestreSakti
vidaldid-rte
force-pushed
the
robustify_remote_control
branch
from
684c430 to
e1cc301
Compare
Signed-off-by: Didier Vidal <[email protected]>
Signed-off-by: Didier Vidal <[email protected]>
Signed-off-by: Didier Vidal <[email protected]>
Signed-off-by: Didier Vidal <[email protected]>
Signed-off-by: Didier Vidal <[email protected]>
Signed-off-by: Didier Vidal <[email protected]>
Signed-off-by: Didier Vidal <[email protected]>
Signed-off-by: Didier Vidal <[email protected]>
Signed-off-by: Didier Vidal <[email protected]>
Signed-off-by: Didier Vidal <[email protected]>
Signed-off-by: Didier Vidal <[email protected]>
Signed-off-by: Didier Vidal <[email protected]>
vidaldid-rte
force-pushed
the
robustify_remote_control
branch
from
628a958 to
a02e70f
Compare
7 tasks
Signed-off-by: Didier Vidal <[email protected]>
vidaldid-rte
changed the title
Signed-off-by: PRABAKARAN Sylvestre <[email protected]>
src/main/java/com/powsybl/openloadflow/ac/AcloadFlowEngine.java
Outdated
Show resolved
Hide resolved
src/main/java/com/powsybl/openloadflow/ac/outerloop/ReactiveLimitsOuterLoop.java
Outdated
Show resolved
Hide resolved
src/main/java/com/powsybl/openloadflow/ac/outerloop/ReactiveLimitsOuterLoop.java
Show resolved
Hide resolved
src/main/java/com/powsybl/openloadflow/ac/outerloop/ReactiveLimitsOuterLoop.java
Outdated
Show resolved
Hide resolved
Signed-off-by: Didier Vidal <[email protected]>
Signed-off-by: PRABAKARAN Sylvestre <[email protected]>
|
SylvestreSakti
approved these changes
Jan 15, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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?
Fixes #1124
What kind of change does this PR introduce?
If the bus of a generator with remote voltage control on , and reactivie limits, is approaches the realistic voltage limit, the generator is moved to PQ and its reactive to QMin (if low voltage) or to QMac (if high voltage).
The enformcement of realistic voltage limit is performed only after the reactive limit outerloop is stabilized
What is the current behavior?
The Newton Raphson fails if a bus reaches a low voltage - a situation that can happen with remoted voltage control due to the PQV model.
What is the new behavior (if this is a feature change)?
The resolution if networks with stressed or inconsistent remote voltage targets is more robust.
Does this PR introduce a breaking change or deprecate an API?
This PR modifies the ACSolver API
If yes, please check if the following requirements are fulfilled
Implementers of an external AC Solver should adapt the run API. The API takes an additional argument that can disable realistic checks.
If the solver checks an unrealistic state, they should implement the new isStateUnrealisticForSolver method.
What changes might users need to make in their application due to this PR? (migration steps)
No change expected.