PSS/E generator voltage setpoint VS doesn't reach the bus

未关闭
  • 哪里不对？
#88 1 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 2 天内回复

还没有人认领这个 Issue。

评估

难度
5/5
预计耗时
一周以上
新手友好度
25/100
Issue 类型
功能
描述清晰度
需要澄清
活跃度
活跃
领域
backend

调研方向

Read the PSS/E parsing path and src/pm_io/matpower.jl:241, then trace where bus magnitude is assigned and where generator ext is consumed. Decide whether VS should override local bus voltage, how solved cases and reactive limits affect that choice, and how to skip remote regulation (IREG). Done means the behavior is decided and covered for the chosen cases.

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

描述

The MATPOWER parser copies a generator's Vg onto its PV bus (src/pm_io/matpower.jl:241). The PSS/E path has no equivalent, so a bus's output magnitude is always its RAW VM. VM only has to be accurate in a solved case, while VS is the setpoint itself.

In the .raw test files, 3510 of 7945 generators on type 2 or 3 buses have VS != VM, and 2185 differ by more than 0.01 pu. Some of those are legitimate, such as a machine at a reactive limit in a solved case.

VS is now preserved in generator ext, but nothing downstream reads it.

Decision needed: should VS override the bus magnitude, as it does for MATPOWER?

  • Yes, for local regulation. This overwrites solved voltages at machines on a reactive limit.
  • Only for unsolved cases, which needs some way to tell them apart.
  • No, and leave VS in ext for downstream code.

Remote regulation (IREG) is a known gap, and a remote setpoint belongs on the regulated bus rather than the generator's own, so any override must skip those machines.

🤖 Generated with Claude Code

主要语言
Julia
星标
1
派生
3
平均合并
4 天 18 小时
30 天内合并 PR
10

环境准备

从这里开始

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

Sienna-Platform/PowerFlowFileParser.jl 的其他 Issue

查看 Sienna-Platform/PowerFlowFileParser.jl 的全部 Issue

相似的 Issue

更多 Julia Issue

把新 issue 发到你的邮箱

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