Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

Muons: Tpar editor (nice to have) improvements

未关闭
#8,991 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
48/100
Issue 类型
功能
描述清晰度
基本清楚
活跃度
冷清
领域
frontend

调研方向

阅读相关 issue #8990,并检查 GUI 中现有的 TPar 编辑器界面。跟踪设置温度脚本以及可能的脚本生成器如何使用常规 TPar 文件和 booster TPar 文件。完成标准是编辑后的数据以表格形式呈现,并且无法保存无效文件。

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

描述

Issue Description

As a muon scientist I would like to make it even harder for my users to muck up the TPar file.

How & Where?

This follows on from #8990 and covers the nice to have elements of what was requested by the muon group.

Additional Information
  • The format of the TPar file is constant, though the number of lines varies
  • There are two TPar files used the regular one and the booster one
  • The set temperature script and possibly script generator consume the tpar file
  • There is currently a tpar editor as a device screen in the GUI
  • Not every instrument wants to expose tpar editing to it's users
  • A valid TPar file:
    • containers a header. This is never changed
    • Has a constant number of columns
    • THigh is the TLow of the next line
    • has at least one line that is not header

See our Git Workflow.

Acceptance Criteria

  • We validate TPAR files edited in the editor (see above) before allowing them to be saved
  • We present the data in the editor as a table for editing, rather than a text file

How to Review

Before making a PR...

  • Provide verbose instructions for the reviewer to test that your changes work and fix the issue
  • Describe if/how you have implemented testing for this issue
  • Provide screenshots of the feature to help the reviewer if relevant

If not applicable, write "Not applicable"

...

To the reviewer: Make sure to update submodules!

主要语言
没有语言数据
星标
6
派生
2
平均合并
12 天 19 小时
30 天内合并 PR
3

环境准备

这个项目没有提供开发容器、Dockerfile 或贡献指南,环境需要你自己搭建:先看它的 README,通用步骤见我们的新手贡献指南。

从这里开始

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

ISISComputingGroup/IBEX 的其他 Issue

查看 ISISComputingGroup/IBEX 的全部 Issue

相似的 Issue

更多 Web Dev Issue

把新 issue 发到你的邮箱

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