-
Notifications
You must be signed in to change notification settings - Fork 150
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
Power flow calculation with distributed slack bus #136
Comments
For reference, richardkue#1 is the PR referred to above. Thanks for sketching this out. I'm a bit torn about how to respond. The approach looks fine if you need the capability right away, but honestly, I'm hesitant about promising it'll be included in a release. And it's not because there is anything wrong with it. I'm definitely interested in including distributed slack in MATPOWER's power flow, but I'm also well into what amounts to a massive MATPOWER re-design/re-write that will deprecate this code with the next release. My preference would be for you to work on implementing distributed slack in the new code (see MP-Element). It should be cleaner to implement there, but the downside is that the code is more of a moving target, is not well documented yet, and is still incomplete in certain areas. I'm happy to schedule a call to discuss if that would be helpful. We can coordinate by e-mail if interested. |
Thanks for your feedback. I understand your concerns about the design. I also see it as a bit of a code degradation. |
To the best of my knowledge there is no power flow calculation with a distributed slack bus in matpower. I am thinking about making a contribution in this regard. Is it enough to implement a power flow with distributed slack bus in only one algorithm (e.g. newton (power, polar))?
At my own fork of the matpower repository I created a pull request with a concept/idea on how to implement a power flow with a distributed slack bus. I would appreciate it if you have a quick look and give me some feedback.
The text was updated successfully, but these errors were encountered: