Developing #188
layout of the setup config file and corresponding structure of the unpacked raw data
Status: | Открыта | Start date: | 04/21/2018 | |
---|---|---|---|---|
Priority: | Низкий | Due date: | ||
Assignee: | Egor Ovcharenko | % Done: | 0% | |
Category: | Software | |||
Target version: | - |
Description
We all have to think of the issue.
Egor proposes an XML-like setup file which would encompass all posible so far detector+readout configurations in our lab.
This file should be used for data acquisition, calibration and ..... ?
The first question is how flexible should be mapping between the readout channel (i.e. block Id+channel ID) and outputs of the detectors. We can foresee three situations 1) A number of consequitive electronics channels from the same block correspond to the same number of the detector channels 2) Each detector occupies consequently 2-3 or more electronics channels with different meaning but the same nature of the signal e.g. Stilbene: Amp1, TAC1, Amp2, TAC2, Amp3, TAC3.....3)arbitrary mapping channel by channel.
The second question is how to incorporate into data nad then use info about initializationj of the blocks, like how many bits are there in the output message, Which amplitude range iand sift of the baseline are set etc.
The third question is about the output data strucure. For interactive analysis in the root session it is more convenient to have only those brunches which correspond to actually read-out channels.
At this point, Egor. please edit the task description in order to fit it to your understanding.
History
#1 Updated by Vratislav Chudoba over 6 years ago
- Description updated (diff)
- Category set to Software
#2 Updated by Vratislav Chudoba over 6 years ago
- Assignee changed from Vratislav Chudoba to Egor Ovcharenko
#3 Updated by Sergey Belogurov over 6 years ago
It's a test of the redmine notification service.