Added a check for tracks with nDoF>256 into TupleToolTrackInfo

Added a check for tracks with nDoF>256. If such a track appears, ProbChi2 is set to -1.

The reason for this is when using TupleToolTrackInfo for WG TrackCalib production, the following error was occasionally spotted:

TupleMuonTTPlus FATAL Standard std::exception is caught TupleMuonTTPlus ERROR array::at: _n (which is 277) >= Nm (which is 257) We found that the error is triggered by probChi2(). From the information at doxygen http://lhcb-doxygen.web.cern.ch/lhcb-doxygen/davinci/latest/d7/dc6/class_l_h_cb_1_1_track.html#a60eef162cbcc97106e34f860eebb70b6 this is an issue emerging from nDof > 256.

The tracks used for TrackEff studies are MuonTT tracks. The number of muon hits can be rather large, causing nDoF > 256.

• [2018-12-06 00:17] Validation started with lhcb-2018-patches#419
• [2018-12-07 00:12] Validation started with lhcb-2018-patches#420
• [2018-12-08 00:14] Validation started with lhcb-2018-patches#421
• [2018-12-09 00:09] Validation started with lhcb-2018-patches#422
• [2018-12-10 00:10] Validation started with lhcb-2018-patches#423
• [2018-12-11 00:11] Validation started with lhcb-2018-patches#424
• [2018-12-12 00:12] Validation started with lhcb-2018-patches#425

added 1 commit

• 83cf8f84 - Update TupleToolTrackInfo.cpp

Compare with previous version

mentioned in commit 5e41fb89

merged

mentioned in commit ba84725a

mentioned in merge request !451 (merged)

mentioned in commit 886426c7

mentioned in merge request !452 (merged)

@rekopecn, I cherry-picked this to run2-patches and master. Is that enough for you? This way I avoid back-propagating to older branches.

@erodrigu Yes, that will do it, many thanks!