-
Notifications
You must be signed in to change notification settings - Fork 0
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
BUG: Non-physical power flow solution returned when simulating MV/LV network #166
Comments
I've just tried with current develop branch, and the issue seems resolved : I get the same results, except for the lines 4, 5, 7, that are now coherents :
|
I could reproduce the bug, it was coming from an incorrect initial potentials propagation. The good results are now always returned, with sometimes even less iterations, so thanks for the report ! |
Thanks @Saelyos, this is very good news as this issue was affecting most of the MV/LV simulations I was trying to make. Will this fix be available in the next release ? |
Yes! :-) |
Describe the bug
When simulating a MV/LV network (MV feeder to which is connected a MV/LV transformer, a LV line and a constant power load), it seems that a non-physical power flow solution can be returned for specific combination of inputs.
To Reproduce
Minimal Working Example to understand the problem
The same simulation, but using CurrentLoad instead of PowerLoad yields coherent results :
The same simulation as the first one, but replacing the MV feeder by a voltage source also yields coherent results :
Expected behavior
In the first simulation, we can observe that the lowest voltage magnitude drops from 199 V to 32 V when increasing the load from 58 to 59 kW, while the voltage drop from 57 kW to 58 kW was only 0.6 V. The same happens for 60 kW and 62 kW. This voltage drop causes huge current (and thus losses) in the line, which translates into overloading of the transformer.
I expect the lowest voltage to be between 197 and 199 V for the 59 and 60 kW.
Version details
roseau-load-flow 0.6.0
The text was updated successfully, but these errors were encountered: