Skip to content
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 5 commits into from
Dec 2, 2024

Conversation

vidaldid-rte
Copy link
Collaborator

@vidaldid-rte vidaldid-rte commented Nov 14, 2024

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?
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?

  • Yes
  • No

If yes, please check if the following requirements are fulfilled

  • The Breaking Change or Deprecated label has been added
  • The migration steps are described in the following section

What changes might users need to make in their application due to this PR? (migration steps)

Other information:

@vidaldid-rte 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
@vidaldid-rte vidaldid-rte force-pushed the hvdc_isolate_if_fictive_load branch from eae1053 to 203f616 Compare November 22, 2024 08:56
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 vidaldid-rte force-pushed the hvdc_isolate_if_fictive_load branch from 3e53873 to a847544 Compare December 2, 2024 12:49
@vidaldid-rte vidaldid-rte merged commit 613d726 into main Dec 2, 2024
7 checks passed
@vidaldid-rte vidaldid-rte deleted the hvdc_isolate_if_fictive_load branch December 2, 2024 12:55
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
Projects
Status: Done
Development

Successfully merging this pull request may close these issues.

3 participants