Please check if the PR fulfills these requirements
[X] The commit message follows our guidelines
[X] Tests for the changes have been added (for bug fixes / features)
[ ] Docs have been added / updated (for bug fixes / features)
Does this PR already have an issue describing the problem?
No. We have:
A dangling line (paired or unpaired)
May have a generation part or not.
Has zero impedance (X = 0, R = 0).
What kind of change does this PR introduce?
Bug fix
What is the current behavior?
Values at boundary are not calculated correctly when dangling lines have zero impedance.
What is the new behavior (if this is a feature change)?
Calculations of boundary magnitudes in IIDM boundary implementation and DanglingLineData now have support for zero impedance.
Zero impedance check for dangling lines is kept at DanglingLineData.
Zero impedance paired dangling lines (inside tie lines) are also calculated correctly.
Does this PR introduce a breaking change or deprecate an API?
[ ] Yes
[X] No
If yes, please check if the following requirements are fulfilled
[ ] The Breaking Change or Deprecated label has been added
[ ] The migration steps are described in the following section
What changes might users need to make in their application due to this PR? (migration steps)
Please check if the PR fulfills these requirements
Does this PR already have an issue describing the problem?
No. We have:
What kind of change does this PR introduce?
Bug fix
What is the current behavior?
Values at boundary are not calculated correctly when dangling lines have zero impedance.
What is the new behavior (if this is a feature change)? Calculations of boundary magnitudes in IIDM boundary implementation and
DanglingLineData
now have support for zero impedance. Zero impedance check for dangling lines is kept atDanglingLineData
. Zero impedance paired dangling lines (inside tie lines) are also calculated correctly.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: