-
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
[WIP] Rao parameters new objective function #1111
Closed
Closed
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
7 tasks
pjeanmarie
force-pushed
the
rao_parameters_new_objective_function
branch
2 times, most recently
from
August 14, 2024 14:30
ddbef67
to
3609782
Compare
pjeanmarie
added
the
PR : dont-merge-before-other
PR mustn't be merged before another (referenced in the description or in the comments)
label
Aug 14, 2024
come after: #1111 |
pjeanmarie
force-pushed
the
rao_parameters_new_objective_function
branch
2 times, most recently
from
September 10, 2024 12:52
1235091
to
55e2760
Compare
… 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>
Signed-off-by: Pauline Jean-Marie <pauline.jean-marie@artelys.com>
…n 'is DC' otherwise AMPERE from load flow sensitivity parameters
Signed-off-by: Pauline Jean-Marie <pauline.jean-marie@artelys.com>
…sts results expected Signed-off-by: Pauline Jean-Marie <pauline.jean-marie@artelys.com>
pjeanmarie
force-pushed
the
rao_parameters_new_objective_function
branch
from
September 17, 2024 15:58
55e2760
to
925df6e
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
PR : dont-merge-before-other
PR mustn't be merged before another (referenced in the description or in the comments)
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)
Other information: