-
Notifications
You must be signed in to change notification settings - Fork 8
doc: add hvdc documentation #1537
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
Conversation
Signed-off-by: CHEN Roxane <[email protected]>
Signed-off-by: CHEN Roxane <[email protected]>
Signed-off-by: CHEN Roxane <[email protected]>
docs/input-data/crac/cse.md
Outdated
| ``` | ||
|
|
||
| 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). |
There was a problem hiding this comment.
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. |
There was a problem hiding this comment.
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.
There was a problem hiding this comment.
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 ?
Signed-off-by: CHEN Roxane <[email protected]>
Signed-off-by: CHEN Roxane <[email protected]>
Signed-off-by: CHEN Roxane <[email protected]>
Signed-off-by: CHEN Roxane <[email protected]>
Signed-off-by: CHEN Roxane <[email protected]>
Signed-off-by: CHEN Roxane <[email protected]>
Signed-off-by: CHEN Roxane <[email protected]>
Signed-off-by: CHEN Roxane <[email protected]>
Signed-off-by: Godelaine <[email protected]>
|
Please retry analysis of this Pull-Request directly on SonarQube Cloud |
|



Does this PR already have an issue describing the problem?
Fixes #1531