when looping over Wire-based tracks and time-based tracks and checking their candidatid number
it happens quite often that the number of candidate tracks is smaller than the candidateid number
of the wirebased or timebased track! I would have expected that this should never be possible.
formally:
when looping over Wire-based tracks and time-based tracks and checking their candidatid number it happens quite often that the number of candidate tracks is smaller than the candidateid number of the wirebased or timebased track! I would have expected that this should never be possible. formally:
DTrackCandidate.size() < DTrackWireBased.candidateid DTrackCandidate.size() < DTrackTimeBased.candidateid
can someone reproduce this?