Open borzari opened 1 year ago
there is quite a bit of text here, including the printout. It may be useful to highlight where the actual problem is.
there is quite a bit of text here, including the printout. It may be useful to highlight where the actual problem is.
I tried adding some highlights there, but don't think it would be good to remove text. Some information about the track shortening procedure itself might be useful
An inconsistency on the number of hits/layers with measurement after refitting was observed during the studies of the track shortening procedure to access the tracking pT resolution with shortened tracks. It might be associated to the fitter, but it needs to be investigated. The summary of the bug is written in bold text below and the rest is auxiliary information.
The track shortening procedure consists of filtering events with "good muons", creating a collection of good muon tracks, shortening those tracks by creating new track candidates with only a few hits of the long track (corresponding to the number of layers of measurement set by the user) and refitting the new track candidates with the
KFFittingSmootherWithOutliersRejectionAndRK
fitter.*The procedure is performed to obtain short tracks with 3 to 8 layers of measurement in the end. For a few of the events (2 in 15292; checking a RelVal MC sample), some of the hits of the short track seem to disappear when comparing the layers/substructure of the short and long tracks. The example shown here is for one event where the short tracks with 3 to 7 layers with measurement are created correctly, but the short track with 8 layers with measurement has the hit associated to the 4th layer missing, even though it is added to the track candidate used to create the short track. This can be seen at the lines with in the print out and the size of
ownHits
(explained below).**To reproduce the bug, this repository can be used. Clone the repository, checkout to branch
cmssw_13_1_0_bugsCheck
and follow the information in the README.The information below is ordered as:
isFirstValidHitInLayerAux
, checked in moduleTrackerTrackHitFilterMod.cc
ownHits
is the amount of hits used to create the track candidate that will be refitted