Fix invalid factors in specific contingency context #837
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: Anne Tilloy <anne.tilloy@rte-france.com>
annetill
changed the title
Signed-off-by: Anne Tilloy <anne.tilloy@rte-france.com>
|
SonarCloud Quality Gate failed.
|
annetill
added
PR: next-release
PR: waiting-for-review
bug
Signed-off-by: Anne Tilloy <anne.tilloy@rte-france.com>
phiedw
approved these changes
Sep 27, 2023
|
SonarCloud Quality Gate failed.
|
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?
When we have an invalid factor, we write the results for pre-contingency state only. If the factor is also associated to a contingency, nothing is written for this contingency. But... we have now specific contingency context, so it means that for these factors, the pre contingency state is not asked. But we provide results for it.
What kind of change does this PR introduce?
For the moment, nothing. Two solutions:
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?
Other information: