Skip to content

Dovombru add back lost end velo state

Dorothea Vom Bruch requested to merge dovombru_add_back_lost_endVelo_state into master

This adds back the functionality of propagating the state to the end of the Velo.

However, please review whether you really need this step. The propagation only changes the x, y and z variables of the state. In the VeloUT algorithm, these are only used for propagations to other z positions, so mathematically it should be the same, no matter whether we propagate from the state at the beam line or at the end of the Velo. There is a slight efficiency difference for VeloUT tracks (1.5% at most in the Velo+UT category) when doing the propagation after the Velo tracking (in consolidate tracks). I believe this comes from the intermediate propagation step.

How is the state used in the forward tracking? Are the x, y and z variables used for something other than propagations? If yes, I suggest that you add the propagation in the prepareOutputTrack function of VeloUT, where you (@gligorov )probably add the state to a track object.

Edited by Dorothea Vom Bruch

Merge request reports