PowerFlow-PhasorDynamics Interface
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 27
- Forks
- 11
- Avg merge
- 3d 8h
- Merged PRs (30d)
- 23
Description
Summary
Tracking the steady state interface feature to solve the power flow
Rationale
Dependent on external solvers for PhasorDynamics until we can obtain a power flow solution from PowerFlow
Description
The translation of branches and generators is unproblematic. We need to resolve:
- PhasorDynamics data does not include Slack/PV bus labeling
- The LoadZ and LoadZIP models have power-flow dependent parameters
Additional information
Translation should happen at the *Data interface, not JSON
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start at the *Data interface, where the issue says translation should occur, and trace the existing branch and generator translation. Investigate how Slack/PV bus labels and the power-flow-dependent LoadZ and LoadZIP parameters are represented. Done means defining the steady-state interface needed to obtain a power-flow solution without relying on external PhasorDynamics solvers.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100