Is your feature request related to a problem? Please describe.
The acts multitrajectoryhelper provided volume and surface id for each hit. We already have chi2 for each hits in the trajectory data structure (see https://github.com/eic/EDM4eic/blob/ed58344685dd40c0e35154ef0ae7eca3f709aa47/edm4eic.yaml#L330)
. Adding those geometry info helps the tracking performance analysis.
Is your feature request related to a problem? Please describe. The acts multitrajectoryhelper provided volume and surface id for each hit. We already have chi2 for each hits in the trajectory data structure (see https://github.com/eic/EDM4eic/blob/ed58344685dd40c0e35154ef0ae7eca3f709aa47/edm4eic.yaml#L330) . Adding those geometry info helps the tracking performance analysis.
I propose to add the following four integer vectors: ( see https://github.com/acts-project/acts/blob/main/Core/include/Acts/EventData/MultiTrajectoryHelpers.hpp) measurementVolume, measurementLayer, outlierVolume, outlierLayer