Improvements in looking forward fit, state object redefinitions
Defined three state objects:
- KalmanVeloState: contains x, y, z, tx, ty, c00, c20, c22, c11, c31, c33
- VeloState: contains x, y, z, tx, ty, backward
- MiniState: contains x, y, z, tx, ty
in the velo consolidation, VeloStates are created in a Velo::Consolidated::States object, they are used by the UT and SciFi tracking algorithms in the simplified velo Kalman filter, KalmanVeloStates are created and saved in a Velo::Consolidated::KalmanStates ojbect, they are used by the PV finding algorithm and the IP filter MiniStates are used on the fly in many of the UT and SciFi tracking algorithms, and when the backward member is not needed, the VeloState is loaded as MiniState for a UT and SciFi tracking algorithm
only those variables that are really used by subsequent algorithms are stored, the chi2 for example was never used any where, so it is now removed
looking forward sbt:
- split up quality filter kernel into a fit and a quality filter kernel
- the fit clearly takes the most time
- improvement for the fit: load hit variables of a track once from global memory, then use those in all the fitting functions