-
Notifications
You must be signed in to change notification settings - Fork 7
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
Rao parameters use unit from is dc #1140
base: rao_parameters_remove_curative_stop_criterion
Are you sure you want to change the base?
Rao parameters use unit from is dc #1140
Conversation
22ef4cf
to
30c511d
Compare
5ce3d76
to
1706a08
Compare
30c511d
to
443782c
Compare
1706a08
to
7f7e969
Compare
dcc85bc
to
7d68245
Compare
b65e806
to
54aa50a
Compare
@@ -5,21 +5,21 @@ | |||
|
|||
Feature: US 10.1: Linear RAO with relative margin | |||
|
|||
@fast @rao @mock @ac @preventive-only @relative | |||
@fast @rao @mock @dc @preventive-only @relative |
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.
Is there a reason you moved from AC to DC? I am affraid this will change the LF results which could alter the test's results
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.
The same question goes for all the other tests, I would rather convert by hand the objective value from MW to A instead of changing the LF computation mode
what do you think @phiedw?
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 dev will be replaced by a separate unit parameter in rao parameter, then no change in tests behavior is expected.
… acceptable) Signed-off-by: Pauline Jean-Marie <pauline.jean-marie@artelys.com>
Signed-off-by: Pauline Jean-Marie <pauline.jean-marie@artelys.com>
…nsecure' and partially replace them by 'enforce curative security' NB. Curative min objective does no longer exist and is replaced by Curative have the same objective than the Preventive results Signed-off-by: Pauline Jean-Marie <pauline.jean-marie@artelys.com>
7d68245
to
9ad0337
Compare
…n 'is DC' otherwise AMPERE from load flow sensitivity parameters Signed-off-by: Pauline Jean-Marie <pauline.jean-marie@artelys.com>
…eters Signed-off-by: Philippe Edwards <philippe.edwards@rte-france.com>
…ect Unit Signed-off-by: Pauline Jean-Marie <pauline.jean-marie@artelys.com>
54aa50a
to
802f70b
Compare
43b027a
to
78c32dc
Compare
78c32dc
to
4371fee
Compare
replaced by: #1197 |
4371fee
to
d726fbb
Compare
Please check if the PR fulfills these requirements
Does this PR already have an issue describing the problem?
What kind of change does this PR introduce?
What is the current behavior?
What is the new behavior (if this is a feature change)?
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)
MAX_MIN_MARGIN_IN_MEGAWATT and MAX_MIN_MARGIN_IN_AMPERE are now MAX_MIN_MARGIN
MAX_MIN_RELATIVE_MARGIN_IN_MEGAWATT and MAX_MIN_RELATIVE_MARGIN_IN_AMPERE are now MAX_MIN_RELATIVE_MARGIN
the unit is computed from load-flow-and-sensitivity-computation -> sensitivity-parameters -> load-flow-parameters -> dc
if dc true we have MEGAWATT if false we have AMPERE
Other information: