Project

General

Profile

Bug #2263

BackTracker crashes on events with more than one neutrino interaction

Added by Nicholas Raddatz about 8 years ago. Updated over 7 years ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Category:
-
Start date:
12/05/2011
Due date:
% Done:

100%

Estimated time:
Duration:

Description

BackTracker produces a seg fault error when it encounters an event with more than one interaction.
The following is the output message on the event it fails on. This is event 114 of the file:
/nova/data/mc/S11.11.16/genie/ndos/sim_genie_ndos_none_nhc_simpleflux_swapping_none_10000_0.root
after reconstruction with KalmanTrack in the S11.11.16 release. Also noted failure in events 59
and 173 of this file which also have two neutrino interactions

%MSG
Begin processing the 1st record. run: 1 subRun: 0 event: 114 at 05-Dec-2011 16:29:04 CST
%MSG-w ClusterCheater: ClusterCheater:cluster 05-Dec-2011 16:29:04 CST run: 1 subRun: 0 event: 114
no particle in ParticleNavigator has track id 293 this could be a problem. Certainly won't make a Cluster for it.
%MSG
%MSG-w ClusterCheater: ClusterCheater:cluster 05-Dec-2011 16:29:04 CST run: 1 subRun: 0 event: 114
no particle in ParticleNavigator has track id 294 this could be a problem. Certainly won't make a Cluster for it.
%MSG
%MSG-w ClusterCheater: ClusterCheater:cluster 05-Dec-2011 16:29:04 CST run: 1 subRun: 0 event: 114
no particle in ParticleNavigator has track id 297 this could be a problem. Certainly won't make a Cluster for it.
%MSG
%MSG-w ClusterCheater: ClusterCheater:cluster 05-Dec-2011 16:29:04 CST run: 1 subRun: 0 event: 114
no particle in ParticleNavigator has track id 298 this could be a problem. Certainly won't make a Cluster for it.
%MSG
%MSG-w ClusterCheater: ClusterCheater:cluster 05-Dec-2011 16:29:04 CST run: 1 subRun: 0 event: 114
no particle in ParticleNavigator has track id 341 this could be a problem. Certainly won't make a Cluster for it.
%MSG
%MSG-w ClusterCheater: ClusterCheater:cluster 05-Dec-2011 16:29:04 CST run: 1 subRun: 0 event: 114
no particle in ParticleNavigator has track id 344 this could be a problem. Certainly won't make a Cluster for it.
%MSG
%MSG-w ClusterCheater: ClusterCheater:cluster 05-Dec-2011 16:29:04 CST run: 1 subRun: 0 event: 114
no particle in ParticleNavigator has track id 412 this could be a problem. Certainly won't make a Cluster for it.
%MSG
%MSG-w ClusterCheater: ClusterCheater:cluster 05-Dec-2011 16:29:04 CST run: 1 subRun: 0 event: 114
no particle in ParticleNavigator has track id 416 this could be a problem. Certainly won't make a Cluster for it.
%MSG
%MSG-w ClusterCheater: ClusterCheater:cluster 05-Dec-2011 16:29:04 CST run: 1 subRun: 0 event: 114
no particle in ParticleNavigator has track id 639 this could be a problem. Certainly won't make a Cluster for it.
%MSG
%MSG-w ClusterCheater: ClusterCheater:cluster 05-Dec-2011 16:29:04 CST run: 1 subRun: 0 event: 114
no particle in ParticleNavigator has track id 641 this could be a problem. Certainly won't make a Cluster for it.
%MSG
%MSG-w ClusterCheater: ClusterCheater:cluster 05-Dec-2011 16:29:04 CST run: 1 subRun: 0 event: 114
no particle in ParticleNavigator has track id 642 this could be a problem. Certainly won't make a Cluster for it.
%MSG
Segmentation fault

History

#1 Updated by Nicholas Raddatz about 8 years ago

The job I run is to get this error is:
nova -c kalmantrackjob -s /nova/data/mc/S11.11.16/genie/ndos/sim_genie_ndos_none_nhc_simpleflux_swapping_none_10000_0.root -o kalman_reco.root
which runs over the whole file without problem. This is then followed by:
nova -c cheaterrecojob.fcl -s kalman_reco.root

#2 Updated by Nicholas Raddatz almost 8 years ago

  • % Done changed from 0 to 100

Problem was that sim::Particles from the second sim::ParticleList were going out of scope in BackTracker.cxx. Solved by making new sim::Particles from those in the sim::ParticleLists and adding them to the ParticleNavigator one at a time making the ParticleNavigator take ownership over the particles.

#3 Updated by Nicholas Raddatz almost 8 years ago

  • Status changed from New to Resolved

Change status to resolved

#4 Updated by Gavin Davies over 7 years ago

  • Status changed from Resolved to Closed


Also available in: Atom PDF