Add support for hierarchical modeling to the JSON format case file specifications

Aperta
#619 8 commenti 0 reazioni 1 assegnatario Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

@abirchfield ci sta già lavorando.

Dal 13/10/2026.

  • #653 di @nkoukpaizan — aperta

Valutazione

Questa issue non è ancora stata valutata.

Descrizione

documentation enhancement new case question
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

Lingua principale
C++
Stelle
27
Fork
11
Merge medio
2g 21h
PR unite (30g)
15

Preparare l'ambiente

Apri in Codespaces

Avvia il container di sviluppo del progetto nel browser, con il tuo account GitHub.

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di ORNL/GridKit

Tutte le issue di ORNL/GridKit

Issue simili

Altre issue su C++

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.