Add support for hierarchical modeling to the JSON format case file specifications
Maintainers usually reply within 1 day
Assessment
This issue has not been assessed yet.
Description
Summary
Expand the specs for JSON case file to include subsystems specifications and support hierarchical modeling. The spect should define subsystems as objects assembled from component models or other subsystems. Subsystems should connect to other subsystems through bus and signal ports.
@lukelowry @tsybinae @nkoukpaizan
Rationale
Hierarchical modeling is needed to support:
- Partitioned numerical integration schemes
- Coarse-grained paralelism
- Graphical user interface for analysis of large systems (> 100,000 buses) that cannot be visualized as whole to a necessary detail
Description
Approach 1: Suggested approach is to keep the current JSON format for case files and append subsystem information after all component models are specified. In such implementation, the subsystem declaration would specify component models belonging to each subsystem and identify connection ports that are external to subsystems. Assuming that component models are level-0, the subsystems described in this way would be level-1 subsystems. This approach can be extended by specifying level-2 subsystems, which are assembled from level-1 subsystems.
Approach 2: Instead of separate stanzas for component models, level-1 subsystems, level-2 subsystems, etc., one could first create a subsystem and then add specs to all components of that subsystem to the JSON value corresponding to the subsystem key. The JSON file would have the same hierarchical structure as the system model.
Approach 1 is easier to manipulate, especially when system repartitioning to different subsystems is needed. Approach 2 may have advantage in instances where the case specifications need to be split in separate files.
Additional information
No response
- 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
-
Separate Rosenbrock integrator interface to GridKit from the integrator implementation.May be free again @alexander-novo claimed this 33 days ago, and no pull request is open. Openenhancement new solver
ORNL/GridKit#618 · 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