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

Abierto
#619 8 comentarios 0 reacciones 1 asignado Ver en GitHub

Los mantenedores suelen responder en 1 día

@abirchfield ya está trabajando en esto.

Desde el 13/10/2026.

  • #653 de @nkoukpaizan — abierto

Evaluación

Este issue todavía no se ha evaluado.

Descripción

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

Lenguaje dominante
C++
Estrellas
27
Forks
11
Merge medio
2 d 21 h
PR fusionados (30 d)
15

Preparar el entorno

Abrir en Codespaces

Inicia el contenedor de desarrollo del proyecto en tu navegador, con tu propia cuenta de GitHub.

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de ORNL/GridKit

Todos los issues de ORNL/GridKit

Issues similares

Más issues de C++

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.