Component Awareness of System MVA Base

Open
#296 0 comments 1 reaction 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
45/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
cpp
Domain
backend

Research direction

Start by locating the Component class and the code that reads the input JSON and constructs component models. Trace how mva_system_base_ is initialized and propagated, then verify that it uses the input system base rather than assuming 100 MVA for power and current conversions.

Written by the indexing model from the issue text.

Description

enhancement
Summary

Each component needs access to the global MVA base to perform base conversions for quantities such as power and current correctly.

Rationale

At the time of writing this, the PhasorDynamics module assumes a priori that the system base is 100 MVA. In #286 , we implemented the machine model MVA base conversion, but the models must assume the system base is 100 MVA. This may not be true for all cases.

Description

The Component class protected variable mva_system_base_ should reflect what is specified in the input JSON file. This system-level information needs to be provided to all component models.

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.