GSI Forum: Bugs, Fixes, Releases » Crash in reco macro: "PndSttMvdTracking, nMvdPixelHitsinTrack[4] is 58and it is

Home » PANDA » PandaRoot » Bugs, Fixes, Releases » Crash in reco macro: "PndSttMvdTracking, nMvdPixelHitsinTrack[4] is 58and it is > nmaxMvdPix

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

Re: Crash in reco macro: "PndSttMvdTracking, nMvdPixelHitsinTrack[4] is 58and it is > nmaxMv [message #13604 is a reply to message #13601]

Fri, 15 June 2012 09:53

Jens Sören Lange
Messages: 193
Registered: June 2005

first-grade participant

From: *physik.uni-giessen.de

Hi all, I guess that's a low pT curler track

-> question to anyone of the MVD experts

can Martin set nMvdPixelHitsinTrack to more than 30?
(if yes, where?)

P.S. Martin needs the plots by Monday, so if anyone has an idea, it would be great ...

Report message to a moderator

[Message index]

		Crash in reco macro: "PndSttMvdTracking, nMvdPixelHitsinTrack[4] is 58and it is > nmaxMvdPix By: MartinJGaluska on Thu, 14 June 2012 15:35
		Re: Crash in reco macro: "PndSttMvdTracking, nMvdPixelHitsinTrack[4] is 58and it is > nmaxMv By: MartinJGaluska on Thu, 14 June 2012 17:27
		Re: Crash in reco macro: "PndSttMvdTracking, nMvdPixelHitsinTrack[4] is 58and it is > nmaxMv By: Jens Sören Lange on Fri, 15 June 2012 09:53
		Re: Crash in reco macro: "PndSttMvdTracking, nMvdPixelHitsinTrack[4] is 58and it is > nmaxMv By: Lia Lavezzi on Fri, 15 June 2012 10:51
		Re: Crash in reco macro: "PndSttMvdTracking, nMvdPixelHitsinTrack[4] is 58and it is > nmaxMv By: MartinJGaluska on Fri, 15 June 2012 12:27

Previous Topic:	simulation macro finished with error
Next Topic:	segmentation violation in reco macro

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

] [

]

Current Time: Thu May 14 05:23:51 CEST 2026

Total time taken to generate the page: 0.00822 seconds