Keep Measurements 'by value' inside TrackFitResult, Keep Trajectories 'by value' inside Measurement (!1380) · Merge requests · LHCb / Rec

Gerhard Raven requested to merge concrete-trajectories-from-detectors into master Jan 16, 2019

Keep Measurement by value inside TrackFitResult instead of as 'owned' pointers. In addition, keep trajectories inside Measurement by value, except for the OT case, which uses several distinct types of Trajectory.

note: this should be applied in conjunction with LHCb!1708 (merged), Lbcom!313 (merged) and Alignment!87 (merged)

Edited Jan 28, 2019 by Marco Cattaneo

Keep Measurements 'by value' inside TrackFitResult, Keep Trajectories 'by value' inside Measurement

Merge request reports