Add optimization tests for OpenReac indicators and bounds #88
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
Signed-off-by: p-arvy <pierre.arvy@artelys.com>
Signed-off-by: p-arvy <pierre.arvy@artelys.com>
Signed-off-by: p-arvy <pierre.arvy@artelys.com>
Signed-off-by: p-arvy <pierre.arvy@artelys.com>
Signed-off-by: p-arvy <pierre.arvy@artelys.com>
Signed-off-by: p-arvy <pierre.arvy@artelys.com>
|
Just changed the branch base temporarily, to facilitate the review, until the PR #83 is merged. |
p-arvy
force-pushed
the
add-optimization-tests
branch
from
b7a6d08 to
a87f58a
Compare
p-arvy
changed the base branch from
refactor-open-reac-tests
to
computer-and-time-as-debug-indicators
p-arvy
force-pushed
the
add-optimization-tests
branch
from
786bef7 to
be08608
Compare
So-Fras
requested changes
Dec 20, 2024
open-reac/src/test/java/com/powsybl/openreac/optimization/OpecReacOptimizationBoundsTest.java
Show resolved
Hide resolved
...reac/src/test/java/com/powsybl/openreac/optimization/OpenReacOptimizationIndicatorsTest.java
Show resolved
Hide resolved
...reac/src/test/java/com/powsybl/openreac/optimization/OpenReacOptimizationIndicatorsTest.java
Show resolved
Hide resolved
...reac/src/test/java/com/powsybl/openreac/optimization/OpenReacOptimizationIndicatorsTest.java
Show resolved
Hide resolved
...reac/src/test/java/com/powsybl/openreac/optimization/OpenReacOptimizationIndicatorsTest.java
Outdated
Show resolved
Hide resolved
7 tasks
|
Please retry analysis of this Pull-Request directly on SonarQube Cloud |
1 similar comment
|
Please retry analysis of this Pull-Request directly on SonarQube Cloud |
Signed-off-by: p-arvy <pierre.arvy@artelys.com>
p-arvy
force-pushed
the
computer-and-time-as-debug-indicators
branch
from
ef4ffb5 to
abfc91b
Compare
Signed-off-by: p-arvy <pierre.arvy@artelys.com>
Signed-off-by: p-arvy <pierre.arvy@artelys.com>
Signed-off-by: p-arvy <pierre.arvy@artelys.com>
Signed-off-by: p-arvy <pierre.arvy@artelys.com>
Signed-off-by: p-arvy <pierre.arvy@artelys.com>
Signed-off-by: p-arvy <pierre.arvy@artelys.com>
p-arvy
force-pushed
the
add-optimization-tests
branch
from
f3b46d9 to
f5149f3
Compare
So-Fras
approved these changes
Jan 6, 2025
Signed-off-by: p-arvy <pierre.arvy@artelys.com>
Signed-off-by: p-arvy <pierre.arvy@artelys.com>
Signed-off-by: p-arvy <pierre.arvy@artelys.com>
Signed-off-by: p-arvy <pierre.arvy@artelys.com>
Signed-off-by: p-arvy <pierre.arvy@artelys.com>
Signed-off-by: p-arvy <pierre.arvy@artelys.com>
So-Fras
changed the base branch from
computer-and-time-as-debug-indicators
to
main
Signed-off-by: Sophie Frasnedo <93923177+So-Fras@users.noreply.github.com>
|
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?
No.
What kind of change does this PR introduce?
New TUs are added, to test OpenReac indicators and generator bounds management in ACOPF.
What is the current behavior?
No such test exists.
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: