Support Component Status + Enrich Branch Model
Maintainers usually reply within 1 day
Nobody has claimed this yet.
- #391 by @lukelowry — closed without merging
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-api-design
Research direction
Start by reviewing the system model and input format, then compare how Bus and existing branch models are represented. Determine how component status should be represented for inactive lines and generators, how branch categories should be organized, and how imported inactive elements should be preserved. Done means the model and file format have an agreed status representation that supports the proposed future Open/Close events.
Written by the indexing model from the issue text.
Description
Summary
Many power system cases come preconfigured with lines that are out of service. We need to support this and add a field to indicate whether, for example, a branch is open or closed, or whether a generator is in service.
Additionally, we might consider treating Branch as a special category, much like Bus is treated in the input format.
Rationale
This is a precursor to support a new event type Open/Close or something similarly named to indicate component status. This will also allow us to fully import case data without omitting inactive elements.
Regarding the second suggestion, there are quite a few branch models that are needed and should be completed before we push for more models, IMHO.
Description
The system model should compose and support a status field that takes a component out of service, in addition to a field in the file format that is standard and well-named to communicate intent
The branch model class in the input format could be like:
"buses": [
{ "class": "bus", ... },
{ "class": "infinite_bus",... }
],
"branches": [
{
"class": "xfmr",
"ports": [1, 2],
"name": "...",
"status": "active",
"init": {...},
"params": {...}
},
{
"class": "xfmrtertiary", // three-winding transformer
"ports": [4, 5, 6] ,
"name": "...",
"status:" "active",
"init": {...},
"params": {...}
},
{
"class": "hvdc",
"ports": [4, 5] ,
"name": "...",
"status": "active",
"init": {...},
"params": {...}
},
{
"class": "line",
"ports": [4, 5] ,
"name": "...",
"status": "active",
"init": {...},
"params": {...}
},
],
Additional information
(regarding status as a field) If this requires changing the system model's dimension at runtime, it should be noted.
- Dominant language
- C++
- Stars
- 27
- Forks
- 11
- Avg merge
- 2d 21h
- Merged PRs (30d)
- 15
Getting set up
Starts the project's dev container in your browser, under your own GitHub account.
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing 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.
More from ORNL/GridKit
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
ORNL/GridKit#587 · 1 reaction ·
Maintainers usually reply within 1 day
-
Companion OPF models for PD initialization constraintsPossibly taken @lukelowry claimed this 3 days ago. OpenIVP question
ORNL/GridKit#656 · 1 assignee ·
Maintainers usually reply within 1 day
-
Extract CommonMath functionsPossibly taken @amandeep25100-a11y claimed this 6 days ago. Opencleanup
Difficulty 4/5 3-5 days Newbie friendliness 54/100
ORNL/GridKit#642 · 1 comment ·
Maintainers usually reply within 1 day
-
enhancement question
Difficulty 5/5 Over a week Newbie friendliness 30/100
ORNL/GridKit#624 · 2 comments · 2 reactions ·
Maintainers usually reply within 1 day
-
Add support for hierarchical modeling to the JSON format case file specificationsPossibly taken @abirchfield claimed this 33 days ago. Opendocumentation enhancement new case question
ORNL/GridKit#619 · 8 comments · 1 assignee ·
Maintainers usually reply within 1 day
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
useless statementOpen
Difficulty 1/5 Under an hour Newbie friendliness 86/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
grizzlypeak3d/DJV#962 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day