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

IMAT (nGEM detector): Scientists would like to test improved end of run script on nGEM PC

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

还没有人认领这个 Issue。

评估

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

调研方向

从修改后的 Mantid 脚本和 nGEM PC 数据区域开始,使用复制回 PC 的具有代表性的 .edb 文件。测量本地处理为 .nxs 文件的过程,并让 IMAT 科学家检查结果是否能减少后续的在线处理。完成的标准是在下一个周期之前试用过该脚本,并且如果它有用,科学家有运行该脚本的简单说明。

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

描述

Core Size - S

Issue Description

As a scientist using the nGEM detector on IMAT, I am experiencing very slow processing times of the .edb files back to a .nxs files after they have been copied to server storage.

I have a modified Mantid script which I would like the nGEM PC to run on the .edb files locally to generate the .nxs file on the data area on the nGEM PC. This could then be moved by an automatic camera file task (as with other imaging cameras) to the NDX to be archived automatically. Even with new storage, this might still be the easiest way to get the desired .nxs file into a state where it can be uploaded by ADA.

Additional Information

What else do I need to know before starting?

  • IMAT scientists/nGEM detector people can supply details of files/locations.
  • Performance locally may be an issue, but local code on a fast machine to SSD storage should give some guidance as to how this might be improved.
  • Note that this depends (at a minimum) on editing a time binning number in the script. Possibly keeping this in a separate file if users need something simple to edit.

Acceptance Criteria

  • New script is tried out before next cycle on a test set of representative .edb files copied back to the nGEM PC
  • Scientists can check results and decide how well this works (does it save later online processing - and how much)
  • If it looks useful, ensure the scientists have what the need to do this for themselves (simple instructions?).
主要语言
没有语言数据
星标
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

更多 Data Engineering Issue

把新 issue 发到你的邮箱

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