Rich: Ring track match index fix for timebased data
Quick summary:
- Fix of out-of-bounds access/writing of std::vector, because of usage of TClonesArray container index instead of running/event index
- TClonesArray container index of RichRing now assigned to GlobalTrack, instead of running/event index
- TClonesArray container index of StsTrack now assigned to GlobalTrack, instead of running/event index
Index of the ring in the ring array was used instead of the running index -> resulted in out-of-bounds access/writing of std::vector.
(Can only be noticed for Time-Based simulations)
In case of no immediate crash, this might have even overwritten other memory locations of the programm, resulting in corrupt data.
(Maybe resulting in crashes for MatchRecoToMc?)
Of interest for @f.kornas
Edited by Pierre-Alain Loizeau