GSI Forum: Tracking » bug in PidCorrelator

Home » PANDA » PandaRoot » Tracking » bug in PidCorrelator

Show: Today's Messages :: Polls :: Message Navigator

Re: bug in PidCorrelator [message #12388 is a reply to message #12380]

Fri, 29 July 2011 10:51

Lia Lavezzi
Messages: 291
Registered: May 2007
Location: Torino

first-grade participant

From: *pv.infn.it

Hi Dima,

Quote:

Double_t fCov[15], fCovOut[15];

And I can guess that on some platforms it's initialised not with zeros but with rundom double numbers which exceed sometimes limits of float.

fCov is filled just after the declaration with TParam->GetCovQ(fCov) so it should not depend on the local initialization of fCov here, but rather on the covariance matrix elements which are inside the FairTrackParH.
I agree with Stefano to try the FairTrackParH::Print() function to see whether we have these strange numbers or not, then we can investigate where they come from. Maybe they are wrongly defined somewhere and then passed to the FairTrackParH when it is created...
Cheers,
Lia.

Report message to a moderator

[Message index]

		bug in PidCorrelator By: Johannes Rauch on Thu, 28 July 2011 17:52
		Re: bug in PidCorrelator By: Lia Lavezzi on Thu, 28 July 2011 18:18
		Re: bug in PidCorrelator By: Johannes Rauch on Fri, 29 July 2011 15:33
		Re: bug in PidCorrelator By: StefanoSpataro on Thu, 28 July 2011 18:46
		Re: bug in PidCorrelator By: Dima Melnychuk on Thu, 28 July 2011 23:11
		Re: bug in PidCorrelator By: Lia Lavezzi on Fri, 29 July 2011 10:51
		Re: bug in PidCorrelator By: Johannes Rauch on Fri, 29 July 2011 16:00
		Re: bug in PidCorrelator By: StefanoSpataro on Fri, 29 July 2011 16:13

Previous Topic:	Changes in PndTpcRiemannTrackingTask
Next Topic:	Problem with secondary tracks

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

] [

]

Current Time: Wed Jun 03 10:39:46 CEST 2026

Total time taken to generate the page: 0.00959 seconds