Skip to content
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

Fix merging networks with a tie line and a dangling line of same pairing key #2740

Merged
merged 6 commits into from
Oct 6, 2023

Conversation

olperr1
Copy link
Member

@olperr1 olperr1 commented Oct 5, 2023

Please check if the PR fulfills these requirements

  • The commit message follows our guidelines
  • 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

What kind of change does this PR introduce?

Bug fix (+ logs)

What is the current behavior?

When merging a network having a tie line between 2 dangling lines of pairing key k with another network having a sole dangling line of pairing key k, we try to create a tie line between the 2 networks, which prevents the merging (an Exception is thrown).

+ Nothing indicates when dangling lines cannot be merged.

What is the new behavior (if this is a feature change)?
When merging a network having a tie line between 2 dangling lines of pairing key k with another network having a sole dangling line of pairing key k, we don't try to create a tie line between the 2 networks and the merge succeeds.

+ Logs are added when dangling lines cannot be merged.

Does this PR introduce a breaking change or deprecate an API?

  • The Breaking Change or Deprecated label has been added
  • The migration guide has been updated in the github wiki (What changes might users need to make in their application due to this PR?)

Other information:

This PR introduces a new method (TieLineUtil.findCandidateDanglingLines) to identify the dangling lines which are candidate to become tie lines when merging the network with another.

To limit the impact of this PR (to avoid breaking changes), which will be introduced in a bug fix release, we didn't refactor the whole dangling lines matching. This will be the object of another PR (see #2741).

annetill and others added 2 commits October 5, 2023 13:12
Signed-off-by: Anne Tilloy <anne.tilloy@rte-france.com>
Signed-off-by: Olivier Perrin <olivier.perrin@rte-france.com>
annetill and others added 3 commits October 5, 2023 14:17
Signed-off-by: Anne Tilloy <anne.tilloy@rte-france.com>
Signed-off-by: Anne Tilloy <anne.tilloy@rte-france.com>
Signed-off-by: Olivier Perrin <olivier.perrin@rte-france.com>
@olperr1 olperr1 changed the title Add logs on dangling line candidates selection Fix merging networks with a tie line and a dangling line of same pairing key Oct 5, 2023
@sonarcloud
Copy link

sonarcloud bot commented Oct 5, 2023

Kudos, SonarCloud Quality Gate passed!    Quality Gate passed

Bug A 0 Bugs
Vulnerability A 0 Vulnerabilities
Security Hotspot A 0 Security Hotspots
Code Smell A 2 Code Smells

93.8% 93.8% Coverage
0.0% 0.0% Duplication

@olperr1 olperr1 merged commit 60ed033 into main Oct 6, 2023
6 checks passed
@olperr1 olperr1 deleted the add_logs_on_dangling_line_candidates branch October 6, 2023 05:43
olperr1 added a commit that referenced this pull request Oct 6, 2023
…ing key (#2740)

* Add log during merging.
* Fix merging + add warning logs during dangling line candidates selection
* Add tests on the fixed merging problem

---------

Signed-off-by: Olivier Perrin <olivier.perrin@rte-france.com>
Signed-off-by: Anne Tilloy <anne.tilloy@rte-france.com>
Co-authored-by: Anne Tilloy <anne.tilloy@rte-france.com>
(cherry picked from commit 60ed033)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants