PowerFlow-PhasorDynamics Interface

Open
#466 0 comments 0 reactions 1 assignee View on GitHub

Maintainers usually reply within 1 day

@lukelowry is already working on this.

Since Oct 2, 2026.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
35/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Quiet
Tech stack
cpp
Domain
backend

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.

Description

enhancement new solver
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

Dominant language
C++
Stars
27
Forks
11
Avg merge
2d 21h
Merged PRs (30d)
15

Getting set up

Open in Codespaces

Starts the project's dev container in your browser, under your own GitHub account.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from ORNL/GridKit

All issues in ORNL/GridKit

Similar issues

More C++ issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.