-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fictive load on isolated bus keeps hvdc isolated #1120
Merged
Merged
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,
SylvestreSakti and
Hadrien-Godard
November 14, 2024 11:28
vidaldid-rte
changed the title
[WIP] fictive load on isolated bus keeps hvdc isolated
fictive load on isolated bus keeps hvdc isolated
Nov 15, 2024
geofjamg
reviewed
Nov 19, 2024
src/main/java/com/powsybl/openloadflow/network/impl/HvdcConverterStations.java
Show resolved
Hide resolved
vidaldid-rte
force-pushed
the
hvdc_isolate_if_fictive_load
branch
from
November 22, 2024 08:56
eae1053
to
203f616
Compare
src/main/java/com/powsybl/openloadflow/network/impl/HvdcConverterStations.java
Show resolved
Hide resolved
src/main/java/com/powsybl/openloadflow/network/impl/HvdcConverterStations.java
Outdated
Show resolved
Hide resolved
SylvestreSakti
approved these changes
Dec 2, 2024
Signed-off-by: Didier Vidal <didier.vidal_externe@rte-france.com>
Signed-off-by: Didier Vidal <didier.vidal_externe@rte-france.com>
Signed-off-by: Didier Vidal <didier.vidal_externe@rte-france.com>
Signed-off-by: Didier Vidal <didier.vidal_externe@rte-france.com>
Signed-off-by: Didier Vidal <didier.vidal_externe@rte-france.com>
vidaldid-rte
force-pushed
the
hvdc_isolate_if_fictive_load
branch
from
December 2, 2024 12:49
3e53873
to
a847544
Compare
Quality Gate passedIssues Measures |
vidaldid-rte
added a commit
that referenced
this pull request
Dec 11, 2024
Signed-off-by: Didier Vidal <didier.vidal_externe@rte-france.com>
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?
No
What kind of change does this PR introduce?
In #965 a simple criteria was added to detect an HVDC disconnection on one side :
A station is isolated if its merged bus is not connected to any other bus neither to a load or a group.
This criteria was meant to detect quickly contingencies that disconnect a line, while allowing simple models where one side is merely simplified as a group or a load.
But in real networks it happens that a fictive load is added to a station.
This fix considers that if an HVDC's stations contains only fictive loads it is still considered isolated.
NOTE that this criteria for automatic HVDC disconnection in a contingncy is not documented at this time. There is currently no good place to document how contingenices are propagated, when the propagation is not obvious.
What is the current behavior?
If a contingency isolates a bus that is connected to a fictive load and an HVDC station, the HVDC is considered working.
What is the new behavior (if this is a feature change)?
If a contingency isolates a bus that is connected to a fictive load and an HVDC station, the HVDC is is stopped.
Does this PR introduce a breaking change or deprecate an API?
If yes, please check if the following requirements are fulfilled
What changes might users need to make in their application due to this PR? (migration steps)
Other information: