Feature #1169
openFeature #1168: Generalize Detector Decode methods
Task #1184: v1.8 updates to THaDetMap
Rework database format for detector maps
0%
Description
Add support for "v2" detector maps to the detector classes to address the shortcomings of the current design.
I propose the following format:
detector_map = [tag] crate slot start end [logical] [M:model] [R:refchannel] [I:refindex] [P:plane] [S:signal] [, ...]
where
tag: optional "tag" (e.g. "L", "R") for grouping entries. Must be first item of each "line" and start with a letter.
crate: crate number
slot: slot number
start: first hardware channel
end: last hardware channel (inclusive)
logical: optional logical channel number associated with the "start" channel. Must be 5th plain number.
M: optional model number (not recommended, only for cross-check with the crate map)
R: optional reference channel
I: optional reference index
P: optional plane number
S: optional signal number (Hall C)
The items of each "line" are space-separated. Separate detector map "lines" (different crate/slot/channels) are comma-separated. All data are integer numbers, except for the optional leading tag.
Updated by Ole Hansen about 11 hours ago
- Parent task changed from #1168 to #1184