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

Loss of a VSC converter station after contingency #961

Merged
merged 7 commits into from
Jan 25, 2024
Merged

Conversation

annetill
Copy link
Member

@annetill annetill commented Jan 22, 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?

Yes, with #957. This PR follows the analysis made in that PR and extracts a smaller part. The aim of this current PR is to handle the loss of a VSC converter station. As there is no VSC converter station contingency, this happens when we loose a bus that contains a VSC converter station. Two cases:

  • The other converter station is not in the LfNetwork: the component with the lost VSC converter station is isolated (and not computed), so is the other side. This case if supported in main branch. Note that it could not be in AC emulation (both converter stations must be in the same LfNetwork).
  • The other converter station is also in the LfNetwork: this case is not supported well. 1) In case of an AC emulation operation, as one side bus is isolated (and not computed), we must disabled the AC emulation equations. 2) In case of a set point operation, in main branch, the other converter station continues to produce or consumes active power.

Solution proposal:

  1. We disable the AC emulation equations and apply a set point of zero on the hvdc line. The other converter station keeps its voltage control capabilities. Putting a set point to zero can be discuss.
  2. We put a set point of zero on the hvdc line. The other converter station keeps its voltage control capabilities. Putting a set point to zero can be discuss. Indeed, if the lost component is big enough with generators and loads, depending on rectifier and inverter configuration, active power flow can flow. Update: the simple criteria of loosing only one bus is kept.

Note that in that proposal, we change something important: if both VSC converter stations are in the LfNetwork at loading, we create a LfHvdc, even if not operated in AC emulation.

LCC converter stations are not supported in that fix.

N case, where for an hvdc line, both converter stations are not in the same synchronous/connected component is not handled. Active power flow is not fixed. Note that in that case, the criteria is not obvious.

Update: what is not supported is in case of bus contingency or bus bar section contingency in DC sensitivity analysis, in the case of the lost bus has a VSC converter station.

@annetill annetill requested a review from geofjamg January 22, 2024 08:09
# Conflicts:
#	src/test/java/com/powsybl/openloadflow/network/HvdcNetworkFactory.java
Signed-off-by: Geoffroy Jamgotchian <[email protected]>
@geofjamg geofjamg changed the title [WIP] Loss of a VSC converter station after contingency Loss of a VSC converter station after contingency Jan 24, 2024
Signed-off-by: Anne Tilloy <[email protected]>
Signed-off-by: Anne Tilloy <[email protected]>
Copy link

Quality Gate Passed Quality Gate passed

The SonarCloud Quality Gate passed, but some issues were introduced.

1 New issue
0 Security Hotspots
91.9% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarCloud

@annetill annetill merged commit c6a180a into main Jan 25, 2024
6 checks passed
@annetill annetill deleted the rework-hvdc branch January 25, 2024 09:49
@annetill annetill mentioned this pull request Feb 1, 2024
7 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants