Tearing - Tell a limited plasma from a padded g-file before placing surfaces past the boundary

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

维护者通常 3 天内回复

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
35/100
Issue 类型
缺陷
描述清晰度
基本清楚
活跃度
活跃
领域
backend

调研方向

Start with the g-file reader, which currently drops the limiter contour, and with the overlap scan that places surfaces past ψ_N = 1 when separatrix_q_law fires on a limited plasma. First keep the limiter contour when it is present, then have the scan check whether the boundary touches the limiter and skip any surface past ψ_N = 1 in that case, with a message saying so. Done when a limited EFIT-style test file with a nearby X-point produces no phantom surface and no overlap warning.

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

描述

separatrix_q_law builds a law whenever a poloidal-field minimum on the outermost surface leads to a saddle and the law reproduces the traced shear. A limited plasma with an X-point nearby passes both: one EFIT reconstruction checked gives an X-point at ψ_N = 1.093 and a shear ratio of 0.86. The overlap scan then treats it like a padded diverted file. It places one rational past ψ_N = 1, where no closed surface exists, and warns that no overlap could be established.

Today the domain is unchanged, so this is only a spurious warning. But if the kinetic profiles extend past ψ_N = 1 (p-files often reach about 1.12), that phantom surface would be scored and could move the cut one rational inward.

The size of the gap cannot distinguish the two cases, since a plasma close to diverting can have an X-point just outside ψ_N = 1. The reliable discriminator is the g-file's limiter contour, which GPEC's reader does not keep: a boundary touching the limiter is limited, and no surface past it should be placed.

Done when:

  • The reader keeps the limiter contour, where present.
  • The scan places no surface past ψ_N = 1 when the boundary touches the limiter, and says so.
  • A test with a limited EFIT-style file that has an X-point nearby.

🤖 Generated with Claude Code

主要语言
Julia
星标
11
派生
7
平均合并
3 天 22 小时
30 天内合并 PR
70

环境准备

  • 没有 Dockerfile 或 Docker Compose 文件
  • 有 Pull Request 模板
  • 没有贡献指南

从这里开始

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

OpenFUSIONToolkit/GPEC 的其他 Issue

查看 OpenFUSIONToolkit/GPEC 的全部 Issue

相似的 Issue

更多 Julia Issue

把新 issue 发到你的邮箱

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