Fix Security Analysis exception contingency on half-connected non-impedance branch #1339
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?
Bug fix
What is the current behavior?
With
lowImpedanceBranchModeset toREPLACE_BY_ZERO_IMPEDANCE_LINE, contingencies on non-impedant branches that are connected only at one side cause an exception, in both AC and DC.What is the new behavior (if this is a feature change)?
The fix consists in adding a check that both buses of the branch are non-null when updating non-impedant branches equations. (Because non-impedant branches equations are created only if both buses of the branch are non-null).
Does this PR introduce a breaking change or deprecate an API?
Other information:
The issue was first observed on a three-windings transformer with one side disconnected (if this matters), but can be reproduced on a simple line.