ISISComputingGroup / ISISComputingGroup/DataStreaming

kdaectrl: fill out more of nexus_structure in run start

未關閉
#45 1 則留言 0 個 reaction 已指派 0 人 在 GitHub 檢視
主要語言
沒有語言資料
星號
0
分支
0
PR 合併指標
30 天內沒有已合併 PR

描述

in a run start we currently just add placeholders for blocks and for events.

we should write some static fields (based off KDAECTRL's PV values), these are the easy ones:

`title` - based on `TITLE` (assume this won't change and just do it static for now, https://github.com/ISISComputingGroup/DataStreaming/issues/44 needs to be implemented for this)
`start_time` - based on start time of message ( we already put this in the run start)
`name` - the instrument name
`run_number` - the run number
`beamline` - the instrument name
`program_name` - probably shouldn't be ISISICP

the `/instrument` group
which contains
- name - the instrument name
- source (a group) containing:
- name: ISIS
- probe: neutrons
- type: Pulsed Neutron Source

potentially more challenging:
`run_cycle` - the current cycle. how does the ICP get this?
`experiment_identifier` - not sure what this is

as part of this ticket we should actually document these fields in the dev wiki.
todo: there are also some fields which can only be written at the end, write tickets for these.

貢獻指南

這個儲存庫沒有索引到貢獻指南

評估

這個 Issue 還沒有評估資料。

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

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