Draft: Added alternative Pixel and Strip raw data container.
- Proposal for a new ID raw data EDM:
Store pixel and strip raw data in xAOD like flat arrays. Additionally there is an element range per module which identifies the RAW data associated to each module. While there is a single list of element ranges, the actual raw data can be stored in multiple containers e.g. one container per ROI.
To allow for concurrent registration of new raw data element ranges, each range can be added by an atomic operation to the list of ranges.
Proxy objects can be created to allow accessing the raw data in e.g. range based for loops, or via module and per module RDO indices.
-
new clusterization which eliminates the need of an intermediate cluster collection
-
reduced cluster EDM for pixel and strips, which stores data of the associated hits in small vectors