GSI Forum
GSI Helmholtzzentrum für Schwerionenforschung

Home » PANDA » PandaRoot » Tracking » Riemann track finder crash.
Re: Riemann track finder crash. [message #11463 is a reply to message #11436] Wed, 26 January 2011 18:44 Go to previous messageGo to previous message
Lia Lavezzi
Messages: 291
Registered: May 2007
Location: Torino
first-grade participant

From: *pv.infn.it
Hi,
concerning the crash on PndRiemannHit::operator<, I think it is due to the fact that fS in PndRiemannHit is not initialized.

I was having the same crash and by printing the s() and aHit.s() values inside the bool operator< (const PndRiemannHit& aHit)function, i.e. the arclengths which are compared, I got a lot of lines like these:
S 5.06921e-307 AHIT.S() 2.80686e-317
S 5.06921e-307 AHIT.S() 2.80686e-317
S 3.35472e-304 AHIT.S() 2.80686e-317
S 3.35472e-304 AHIT.S() 5.06921e-307
S 5.06921e-307 AHIT.S() 2.80686e-317

i.e. the values are not initialized.

They come from sortHits() which is inside PndRiemannTrack::refit, called for the first time in PndMvdRiemannTrackFinder::GetStartTracks().
At this stage the fS variable of the PndRiemannHit is not filled yet and this may lead to the crash.
If the sorting is not necessary in this first call, then the fS initialization should fix the problem.
What do the experts think of this?
Cheers,
Lia.

 
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Read Message
Previous Topic: energy dose to readout electronics
Next Topic: Timeout for the STT and STT+MVD pattern recognition
Goto Forum:
  


Current Time: Fri Apr 19 02:08:07 CEST 2024

Total time taken to generate the page: 0.01367 seconds