Skip to content

Conversation

@RoxaneChen02
Copy link
Collaborator

Does this PR already have an issue describing the problem?

Fixes #1531

Signed-off-by: CHEN Roxane <[email protected]>
Signed-off-by: CHEN Roxane <[email protected]>
Signed-off-by: CHEN Roxane <[email protected]>
```

For now the only VariationType handled by OpenRAO is "ABSOLUTE" : the min/max admissible set-points of the HVDC.
**An HVDC Range Action is modelled by an Injection range Action** (the HVDC line is disconnected and replaced by two injections, one on each side of the line, with opposite keys of 1 and -1).
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is not even a part of the code that you modified, but I noticed that it is not precise enough: the HVDC line is not disconnected, the reality is that an HVDC line cannot be modeled in UCTE format, so an equivalent model is used: the HVDC is represented through two injections (and other elements, cf GridCapa doc), this is whoy the HVDC range action is modelled by an Injection Range actions.


**Implication:**

An HVDC Range Action moves the active setpoint field of the HVDC line. When a line is in AC Emulation mode, applying an **HVDC Range Action** has no effect because the line cannot be directly controlled via its active power setpoint.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would rephrase this, to clarify if you are talking about an "HVDC Range Action" in OpenRAO (which is an action that doesn't work on a line in AC emulation), or a general "HVDC Range Action" (which is a theoretical element, that could also contain implicitly the switch from AC emulation to fixed setpoint mode).
My concern here is that in the beginning of the page, the reader might feel that it is impossible to use a remedial action that optimises the setpoint on an HVDC line in AC emulation - which is not true, as explained later on the page.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I tried adding something to clarify this point. What do you think ?

@Godelaine Godelaine added the PR: waiting-for-correction This PR is waiting to be corrected by its author label Nov 7, 2025
Signed-off-by: CHEN Roxane <[email protected]>
Signed-off-by: CHEN Roxane <[email protected]>
@RoxaneChen02 RoxaneChen02 added PR: ready-to-be-merged This PR is waiting to be merged and removed PR: waiting-for-correction This PR is waiting to be corrected by its author labels Nov 10, 2025
Signed-off-by: CHEN Roxane <[email protected]>
Signed-off-by: CHEN Roxane <[email protected]>
Signed-off-by: CHEN Roxane <[email protected]>
@Godelaine Godelaine added next-release This issue or pull request should be resolved before next release and removed Release 12/2025 labels Nov 24, 2025
@sonarqubecloud
Copy link

Please retry analysis of this Pull-Request directly on SonarQube Cloud

@sonarqubecloud
Copy link

@Godelaine Godelaine merged commit 9f341de into main Nov 28, 2025
19 checks passed
@Godelaine Godelaine deleted the doc/hvdc_page branch November 28, 2025 09:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

next-release This issue or pull request should be resolved before next release PR: ready-to-be-merged This PR is waiting to be merged

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Write more detailed doc on how we handle hvdc range action in the RAO

5 participants