Support Component Status + Enrich Branch Model

未关闭
#370 1 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

  • #391 来自 @lukelowry —— 已关闭,未合并

评估

难度
5/5
预计耗时
一周以上
新手友好度
35/100
Issue 类型
功能
描述清晰度
需要澄清
活跃度
冷清
技术栈
cpp

调研方向

首先审查系统模型和输入格式,然后比较 Bus 和现有分支模型的表示方式。确定非活动线路和发电机的组件状态应如何表示、分支类别应如何组织,以及导入的非活动元素应如何保留。完成的标准是:模型和文件格式具有一致的状态表示,并支持所提议的未来 Open/Close 事件。

由索引模型根据 Issue 内容生成。

描述

enhancement
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.

主要语言
C++
星标
27
派生
11
平均合并
2 天 21 小时
30 天内合并 PR
15

环境准备

在 Codespaces 中打开

在浏览器里用你自己的 GitHub 账号启动这个项目的开发容器。

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

ORNL/GridKit 的其他 Issue

查看 ORNL/GridKit 的全部 Issue

相似的 Issue

更多 C++ Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。