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 set on wrong bus in busbreakerview after view invalidation #3200

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

Comments

@jonenst
Copy link
Contributor

jonenst commented Nov 6, 2024

Describe the current behavior

    vl.getNodeBreakerView().newBusbarSection().setId("BBS1").setNode(1).add();
    vl.getNodeBreakerView().newBreaker().setId("BR1").setRetained(true).setOpen(false).setNode1(1).setNode2(2).add();
    System.out.println(vl.getBusBreakerView().getBus("VL_1").setV(123).getV());
    System.out.println(vl.getBusBreakerView().getBus("VL_2").getV());
    vl.getNodeBreakerView().getSwitch("BR1").setOpen(true);
    System.out.println(vl.getBusBreakerView().getBus("VL_1").setV(456).getV());
    System.out.println(vl.getBusBreakerView().getBus("VL_2").getV());

123.0
123.0
456.0
456.0

When we setV(456), the switch is open so VL_2 should not be set to 456

This is because there is no equipment associated with the bus, so to get a terminal to store the voltage/angle we findEquivalentTerminal but findEquivalementTerminal doesn't stop at retained switch so the equivalent terminal of vl2 is the one from the busbarsection of vl1 (because the switch is closed when the findEquivalementTerminal happens). Then we open the switch but because it is retained we don't invalidate the busbreakerbuses (normal because toggling retained switch should not affect busbreakerview buses because they should stop at retained switch anyway !) and so we keep the old equivalent terminal but now it's no longer equivalent

Describe the expected behavior

should print
123.0
123.0
456.0
123.0

Describe the steps

No response

Environment

No response

Relevant Log Output

No response

Extra Information

No response

@jonenst jonenst added the bug label Nov 6, 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