Bug #1408
closedCrash in CbmMatchRecoToMC with simulations based on GEANT4
Description
With simulations based on GEANT4 transport quite often you get a crash in CbmMatchRecoToMC task.
The problem is not seen with GEANT3 and becomes more frequent after inactivating specialCuts.
The log and a macro to reproduce the problem are attached.
Example simulation files can be found at /lustre/cbm/users/ogolosov/mc/cbmsim/bug_examples/match_reco_to_mc
Seems to be related to #1393.
RC OCT19, FaisSoft jun19p1, FairRoot jun19p1.
Files
Related issues
Updated by Oleg Golosov over 2 years ago
- File match.log.gz match.log.gz added
- File run_match.C run_match.C added
Updated by Volker Friese over 2 years ago
- Status changed from Assigned to In Progress
Seems to be related to #1393.
Yes, but now it is an StsPoint which does not have a valid index of an MCTrack. I will try to debug that.
Updated by Volker Friese over 2 years ago
- Status changed from In Progress to Resolved
- Assignee changed from Volker Friese to Oleg Golosov
- % Done changed from 0 to 100
Inspection of some MC events show that in some rare cases, MCPoints from systems other than PSD do have a MCTrack index -2. Only seen with GEANT4, not with GEANT3. We will not be able to debug this for the OCT19 release, which is already delayed. We follow this issue further in the related one #1393.
For the time being (in the OCT19 release), I prevented CbmMatchRecoToMC from crashing by skipping over invalid MCTrack indizes. It crashes for STS because for STS track matching, the MCTrack object is accessed, which is not the case for other matching purposed.
Updated by Volker Friese over 2 years ago
- Related to Bug #1393: Digitization crash due to TOF hits without mathed MC-tracks while using Geant4 added
Updated by Volker Friese over 2 years ago
- Due date set to 10/28/2019
- Status changed from Resolved to Closed
Updated by Volker Friese over 2 years ago
- Has duplicate Bug #1426: GEANT4 : run_reco_event.C crashes with useMC = kTRUE added