Hacktoberfest 2026:維護者為十月標記出來的 issue,仍然開放、適合新手。 瀏覽 Hacktoberfest issue

`filewriter`: `runlog/icp_event`

未關閉
#92 3 則留言 0 個 reaction 已指派 0 人 在 GitHub 檢視

還沒有人認領這個 Issue。

評估

難度
5/5
預估耗時
一週以上
新手友好度
42/100
Issue 類型
功能
描述清晰度
基本清楚
活躍度
冷清

研究方向

首先追蹤 filewriter 如何消費底層事件資料流,以及它目前如何寫入 runlog 群組。將提議的 newStyle 命令與 Mantid 所說明的剖析行為進行比較,然後確認 START_COLLECTION、STOP_COLLECTION、CHANGE 和 CHANGE_PERIOD 是否反映良好/不良的 frame 與 period 轉換;在認定工作完成之前,釐清是否需要包含 ABORT。

由索引模型根據 Issue 內容生成。

描述

filewriter

The filewriter must be able to write the runlog/icp_event group, as parts of this are currently parsed by Mantid.

From discussions, my current understanding is that Mantid:

  • Does read CHANGE_PERIOD and CHANGE events. We will emulate these by looking at the event data stream and emitting a fake CHANGE_PERIOD message each time we see incoming data with a different period number.
  • Does read START_COLLECTION, STOP_COLLECTION, ABORT messages.
  • Can read BEGIN, RESUME, END_SE_WAIT, PAUSE, END, ABORT, UPDATE, START_SE_WAIT messages, but only if oldStyle is being used.
  • Does not parse the numbers from GF x RF x GUAH x messages.

Potential differences from existing files

  • Proposal is to only write the newStyle commands, so START_COLLECTION, STOP_COLLECTION, CHANGE, CHANGE_PERIOD, ABORT.
  • All data will be emulated (derived from the underlying event data):
    • START_COLLECTION written at the beginning, and then on any transition from a bad frame to a good frame.
    • STOP_COLLECTION written on any transition from a good frame to a bad frame, and then at the end.
    • ABORT - not convinced this is meaningful, if the run is aborted then won't get a .nxs file at all...
    • CHANGE_PERIOD will be written any time we get a frame which has a different period than the most-recently-seen frame
  • CHANGE_PERIOD will account for hardware periods as well as software periods (they look the same to the filewriter in the streaming system). This means that there could be a much higher frequency of CHANGE_PERIOD events than previously.
  • START_COLLECTION and STOP_COLLECTION will account for hardware vetos as well as pause/runcontrol (they look the same to the filewriter in the streaming system). This means that there could be a much higher frequency of START_COLLECTION and STOP_COLLECTION events than previously.
主要語言
沒有語言資料
星號
0
分支
0
PR 合併指標
30 天內沒有已合併 PR

環境準備

這個專案沒有提供開發容器、Dockerfile 或貢獻指南,環境需要你自己搭建:先看它的 README,通用步驟見我們的新手貢獻指南。

從這裡開始

  1. 先讀完整個 Issue,再讀專案的貢獻指南。
  2. 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
  3. Fork 儲存庫,在一個分支上完成修改。
  4. 送出 Pull Request,並在描述裡引用這個 Issue 編號。

ISISComputingGroup/DataStreaming 的其他 Issue

查看 ISISComputingGroup/DataStreaming 的全部 Issue

相似的 Issue

更多 Data Engineering Issue

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。