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

V/Angle inconsistency between nodebreakertopology and busbreaker topology #3207

Open
jonenst opened this issue Nov 12, 2024 · 0 comments
Open
Labels

Comments

@jonenst
Copy link
Contributor

jonenst commented Nov 12, 2024

Describe the current behavior

In nodebreaker topology, V/angle is stored in each equipment
In busbreaker topology, V/angle is stored in each configured bus

This leads to inconsistencies:

  • not possible to set V on a bus with no equipment in node breaker topology
  • when using moveConnectable on an equipment in busbreaker toplogy, it changes it's V. For example getI() will return different results. (in nodebreaker topology, getI() is the same after a move to a different busbar). Note: getI() in busbreakertopology will return inconsistent results after a move, an intensity that never existed because it uses the old active power and the new voltage!

Describe the expected behavior

EIther document the different behaviors and why it's important that they exist
or make the behavior the same to avoid confusion

Describe the steps

No response

Environment

No response

Relevant Log Output

No response

Extra Information

No response

@jonenst jonenst added the bug label Nov 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant