-
Notifications
You must be signed in to change notification settings - Fork 6
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: separate business from implementation specific #1101
Open
pjeanmarie
wants to merge
13
commits into
rao_parameters_merge_type_and_preventive_stop_criterion
Choose a base branch
from
rao_parameters_separate_business_and_implem_specific
base: rao_parameters_merge_type_and_preventive_stop_criterion
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Rao Parameters: separate business from implementation specific #1101
pjeanmarie
wants to merge
13
commits into
rao_parameters_merge_type_and_preventive_stop_criterion
from
rao_parameters_separate_business_and_implem_specific
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
Rao Parameters: separate business from implementation specific
WIP: Rao Parameters: separate business from implementation specific
Jul 31, 2024
pjeanmarie
force-pushed
the
rao_parameters_separate_business_and_implem_specific
branch
from
August 5, 2024 16:31
23e045e
to
f307d78
Compare
pjeanmarie
changed the title
WIP: Rao Parameters: separate business from implementation specific
[WIP] Rao Parameters: separate business from implementation specific
Aug 9, 2024
pjeanmarie
force-pushed
the
rao_parameters_separate_business_and_implem_specific
branch
2 times, most recently
from
September 25, 2024 13:29
27fdbce
to
06d212b
Compare
pjeanmarie
force-pushed
the
rao_parameters_separate_business_and_implem_specific
branch
3 times, most recently
from
October 8, 2024 14:35
f7a70a8
to
01ec4ab
Compare
pjeanmarie
force-pushed
the
rao_parameters_separate_business_and_implem_specific
branch
4 times, most recently
from
October 15, 2024 13:27
63fc61f
to
a24cff9
Compare
pjeanmarie
force-pushed
the
rao_parameters_separate_business_and_implem_specific
branch
4 times, most recently
from
October 23, 2024 16:26
5bee729
to
9a19a7c
Compare
pjeanmarie
force-pushed
the
rao_parameters_separate_business_and_implem_specific
branch
2 times, most recently
from
October 28, 2024 10:06
e2d19b0
to
b84b8ce
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>
…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>
Signed-off-by: Pauline Jean-Marie <pauline.jean-marie@artelys.com>
…one extension (to have a flat yml for platform config) Signed-off-by: Pauline Jean-Marie <pauline.jean-marie@artelys.com>
Signed-off-by: Pauline Jean-Marie <pauline.jean-marie@artelys.com>
Signed-off-by: Pauline Jean-Marie <pauline.jean-marie@artelys.com>
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_separate_business_and_implem_specific
branch
from
October 28, 2024 16:10
b84b8ce
to
66dc9dc
Compare
Signed-off-by: Pauline Jean-Marie <pauline.jean-marie@artelys.com>
pjeanmarie
force-pushed
the
rao_parameters_separate_business_and_implem_specific
branch
from
November 4, 2024 10:01
66dc9dc
to
c760e7a
Compare
pjeanmarie
changed the base branch from
main
to
rao_parameters_merge_type_and_preventive_stop_criterion
November 5, 2024 09:18
pjeanmarie
changed the title
[WIP] Rao Parameters: separate business from implementation specific
Rao Parameters: separate business from implementation specific
Nov 5, 2024
pjeanmarie
added
breaking-change
Changes could break users' code
PR : dont-merge-before-other
PR mustn't be merged before another (referenced in the description or in the comments)
labels
Nov 5, 2024
pjeanmarie
force-pushed
the
rao_parameters_merge_type_and_preventive_stop_criterion
branch
from
November 19, 2024 11:20
8810fed
to
4e59f6b
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
breaking-change
Changes could break users' code
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.
… acceptable)
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: