-
Notifications
You must be signed in to change notification settings - Fork 8
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
Switch contingency support #501
Conversation
Signed-off-by: Geoffroy Jamgotchian <[email protected]>
# Conflicts: # pom.xml
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What about the impact on sensitivity analysis? As we are in bus view for sensitivity analysis (right?), we will fall in the exception?
I have to test it. For DC sensitivity analysis it is same issue as for contingency propagation: so it is an ongoing topic. |
Signed-off-by: Anne Tilloy <[email protected]>
…ysis Signed-off-by: Geoffroy Jamgotchian <[email protected]>
Signed-off-by: Geoffroy Jamgotchian <[email protected]>
I just threw an exception in case of sensitivity analysis. As calculation is done on bus/view (breakers = false in DC and in AC), there is a LOT a work to make it working for sensitivity analysis and not sure somebody needs it. So let's see that later. |
Kudos, SonarCloud Quality Gate passed! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, later for sensitivity analysis !
Signed-off-by: Geoffroy Jamgotchian [email protected]
Please check if the PR fulfills these requirements (please use
'[x]'
to check the checkboxes, or submit the PR and then click the checkboxes)Does this PR already have an issue describing the problem ? If so, link to this issue using
'#XXX'
and skip the restWhat kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
What is the current behavior? (You can also link to an open issue here)
What is the new behavior (if this is a feature change)?
Does this PR introduce a breaking change or deprecate an API? If yes, check the following:
Other information:
(if any of the questions/checkboxes don't apply, please delete them entirely)