-
Notifications
You must be signed in to change notification settings - Fork 91
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
Buggy PF Switch Solutions #279
Comments
Hi Sergio! I am precisely working on this stuff. Currently if you download the The thing is that switches need to be eliminated from the equation before simulating. |
BTW, you could help contributing a reconfiguration module using the already existing genetic algorithms coupled with this. See this. Should be easy ;) |
Check this out. |
Great. Thanks a lot. Go ahead and use the case for what you need. For the investing example, I am getting this error with the
For some reason, the rest of the content of the |
Could you please paste the complete trace? that way I can see the files and line causing trouble. |
Hi @sergio-dorado, I've just published 5.1.9, where the topology processing is improved. |
Hi. I am exploring the capabilities of GridCal for transmission reconfiguration studies. Are the switch models to be used inside power flow computations? My toy example is a three-bus system, shown below.
I change the model of substation 3 to a node breaker using a double-breaker double-bus configuration.
The reference parameters are from the
pglib
repository here. I created the node-breaker version of the case by hand, adding breakers in a double-bus double-breaker configuration. When I close all the breakers or close them to have an ordinary bus bar at bus 3, I get strange power flow results that do not match the bus branch case. For quick reference, here are the power flow results with the bus branch model:And these are the ones with the node-breaker model:
I have also conducted my experiments with
pandapower
, and the results match (up to numerical error). What might be causing this behavior?The text was updated successfully, but these errors were encountered: