GSI Forum
GSI Helmholtzzentrum für Schwerionenforschung

Home » PANDA » PandaRoot » Tracking » Riemann track finder crash.
Re: Riemann track finder crash. [message #11616 is a reply to message #11463] Mon, 04 April 2011 12:27 Go to previous messageGo to previous message
Lia Lavezzi
Messages: 291
Registered: May 2007
Location: Torino
first-grade participant

From: *pv.infn.it
Hi MVD experts,
as agreed during the last EVO meeting, I updated the code to the last revision and re-run the reconstruction on my files to see whether the crash happens or not.

Unfortunately I still see the crash on PndRiemannHit::operator<.

In my previous message on this thread I found a connection between this crash and an uninitialized variable (fS, in PndRiemannHit).

Even if you don' t see the crash, can you please check this variable by putting a cout (std::cout << "s() " << s() << std::endl;) in the function:
bool operator< (const PndRiemannHit& aHit)
of PndRiemannHit.h to see if you see something strange too?

I see something like:
s() -1.174e+14
s() -1.174e+14
s() 1.196e-224
s() 1.196e-224
s() -1.174e+14
s() -1.174e+14
s() 1.196e-224
s() 1.196e-224
s() -1.174e+14
s() -1.174e+14
s() 1.196e-224
s() 1.196e-224
s() -1.174e+14
s() -1.174e+14
s() 1.196e-224

and these are clearly weird numbers.
Thank you in advance,
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 26 04:56:25 CEST 2024

Total time taken to generate the page: 0.01044 seconds