Rao parameters forbid cost increase always true #1112
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
pjeanmarie
changed the title
7 tasks
pjeanmarie
force-pushed
the
rao_parameters_forbid_cost_increase_always_true
branch
3 times, most recently
from
59f6dd5 to
3a7b4bd
Compare
pjeanmarie
changed the title
pjeanmarie
force-pushed
the
rao_parameters_forbid_cost_increase_always_true
branch
2 times, most recently
from
43c2d26 to
3f5bef7
Compare
pjeanmarie
force-pushed
the
rao_parameters_forbid_cost_increase_always_true
branch
2 times, most recently
from
8576a0c to
c983910
Compare
pjeanmarie
force-pushed
the
rao_parameters_forbid_cost_increase_always_true
branch
from
c983910 to
6ef7c93
Compare
pjeanmarie
force-pushed
the
rao_parameters_forbid_cost_increase_always_true
branch
from
6ef7c93 to
00713a3
Compare
pjeanmarie
force-pushed
the
rao_parameters_forbid_cost_increase_always_true
branch
from
7fc9c43 to
6607c13
Compare
pjeanmarie
force-pushed
the
rao_parameters_forbid_cost_increase_always_true
branch
from
6607c13 to
b1a5757
Compare
pjeanmarie
force-pushed
the
rao_parameters_forbid_cost_increase_always_true
branch
from
82aacb6 to
f57fcdb
Compare
obrix
reviewed
Nov 26, 2024
| @@ -82,14 +82,9 @@ Feature: US 12.15: export different reason per perimeter in SWE CNE | |||
| Given crac creation parameters file is "epic12/CimCracCreationParameters_MonitorLeftSide.json" | |||
| Given configuration file is "epic12/raoParametersSweIDCC_minObjectiveDisabled2P.json" | |||
| When I launch search_tree_rao at "2021-04-02 05:00" | |||
| Then the calculation partially fails | |||
There was a problem hiding this comment.
Not sure why exactly all those tests are impacted in the same way. Maybe @phiedw it would be good to explicitly understand why.
added 2 commits
November 29, 2024 10:51
… acceptable) Signed-off-by: Pauline Jean-Marie <pauline.jean-marie@artelys.com>
Signed-off-by: Pauline Jean-Marie <pauline.jean-marie@artelys.com>
pjeanmarie
force-pushed
the
rao_parameters_forbid_cost_increase_always_true
branch
from
f57fcdb to
159c8e2
Compare
Signed-off-by: Philippe Edwards <philippe.edwards@rte-france.com>
…ps://github.com/powsybl/open-rao into rao_parameters_forbid_cost_increase_always_true Signed-off-by: Philippe Edwards <philippe.edwards@rte-france.com>
Signed-off-by: Philippe Edwards <philippe.edwards@rte-france.com>
Signed-off-by: Philippe Edwards <philippe.edwards@rte-france.com>
Signed-off-by: Philippe Edwards <philippe.edwards@rte-france.com>
* Remove curative stop criterion and 'optimize curative if preventive unsecure' and partially replace them by 'enforce curative security' * Move unit out of objective function type * Merge content of preventive stop criterion into type * Move implem specific rao parameters into extensions * The object multithreading parameters should be the same than its input, so it contains one parameter available-cpus * Upgrade rao parameters version to 3.0 * Separate previous extensions in business/search-tree as optional * Rename to avoid having same class name in rao parameters and its extension * Separate rao parameters doc in multiple pages * change python script to be able to do all the changes to parameters --------- Signed-off-by: Pauline Jean-Marie <pauline.jean-marie@artelys.com> Co-authored-by: Philippe Edwards <philippe.edwards@rte-france.com>
phiedw
approved these changes
Jan 31, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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)
The parameters were completely refactored.
A python script was created to update all parameter files in a folder.
Other information:
This PR includes multiple pull requests which were merged into each other (#1139, #1197, #1141, #1101, #1191)