0000150: Reconstruction hangs on certain events

View Issue Details [ Jump to Notes ]

[ Issue History ] [ Print ]

Project

Category

View Status

Date Submitted

Last Update

0000150

Hall D Offline

General

public

2011-10-18 11:03

2011-11-07 14:43

Reporter

davidl

Assigned To

staylor

Priority

normal

Severity

major

Reproducibility

always

Status

resolved

Resolution

fixed

Platform

OS Version

Summary

0000150: Reconstruction hangs on certain events

Description

Here is the e-mail originally sent by Igor Senderovich:

Hi David, hi Simon,

I've isolated an event that essentially hangs the reconstruction, i.e. halts with 100% CPU
http://zeus.phys.uconn.edu/~senderovich/tmp/hdg_smeared_badevt.hddm [^] <http://zeus.phys.uconn.edu/%7Esenderovich/tmp/hdg_smeared_badevt.hddm> [^]

You can reproduce this with the phys_tree plugin. Trying to view the event with hdview2 couldn't work either for the same problem, presumably: it froze on me too.

I suspect the rate of such chokes is about 1 in a hundred events. This was event 136. Running reconstruction with 7 threads produced crippled all the threads before reaching event 1000. (I can try to isolate the others for you)

I should note, this is with revision 8351

Thanks, and let me know how I could help.
-Igor

Tags

No tags attached.

Attached Files

Relationships

Notes
(0000186) staylor (developer) 2011-10-24 16:54	I have confirmed the behavior on ifarm1102: the code hangs on this event and eventually causes a segmentation fault. I have isolated the problem to what appears to be nonsense in the start counter (T=9.13056e+22) for one of the tracks. When the DChargedTrackHypothesis code tries to match this to the RF bucket it effectively enters an infinite loop...

(0000198) staylor (developer) 2011-11-07 14:42	I have put a trap in the code to deal with nonsense in the start counter (or any other detector) by looking at times relative to the smallest drift time in the drift chambers.

Issue History
Date Modified	Username	Field	Change
2011-10-18 11:03	davidl	New Issue
2011-10-24 16:54	staylor	Note Added: 0000186
2011-10-24 16:58	staylor	Status	new => confirmed
2011-10-24 16:58	staylor	Status	confirmed => assigned
2011-10-24 16:58	staylor	Assigned To	=> staylor
2011-11-07 14:42	staylor	Note Added: 0000198
2011-11-07 14:43	staylor	Status	assigned => resolved
2011-11-07 14:43	staylor	Resolution	open => fixed