GSI Forum: Bugs, Fixes, Releases » segmentation violation in reco macro

Home » PANDA » PandaRoot » Bugs, Fixes, Releases » segmentation violation in reco macro

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

segmentation violation in reco macro [message #13610]

Fri, 15 June 2012 13:11

MartinJGaluska
Messages: 203
Registered: March 2010
Location: Germany

first-grade participant

From: *physik.uni-giessen.de

Dear all,

after having set nmaxMvdPixelHitsInTrack from 30 to 60 in sttmvdtracking/PndSttMvdTracking.h I encountered another problem when running the reco macro from macro/pid in my simulation of X(3872) -> J/\psi \pi^+ \pi^- with the corrected VVpipi decay model on PandaRoot revision 15615 (Scientific Linux CERN SLC release 5.5 (Boron), 64 bit, fairroot: jan12, root session called with "root -q run_reco_sttcombi.C &> logreco2.log" in a screen session).

I have created a separate topic for this problem as I believe that this problem is not directly related to the nmaxMvdPixelHitsInTrack in the other thread.

Toggle Spoiler

[Updated on: Fri, 15 June 2012 18:38]

Report message to a moderator

[Message index]

		segmentation violation in reco macro By: MartinJGaluska on Fri, 15 June 2012 13:11
		Re: segmentation violation in reco macro -- GEANT related? By: StefanoSpataro on Fri, 15 June 2012 13:38
		Re: segmentation violation in reco macro -- GEANT related? By: MartinJGaluska on Fri, 15 June 2012 13:44
		Re: segmentation violation in reco macro -- GEANT related? By: StefanoSpataro on Fri, 15 June 2012 14:06
		Re: segmentation violation in reco macro -- GEANT related? By: MartinJGaluska on Fri, 15 June 2012 18:37
		Re: segmentation violation in reco macro -- GEANT related? By: StefanoSpataro on Fri, 15 June 2012 18:52
		Re: segmentation violation in reco macro -- GEANT related? By: MartinJGaluska on Fri, 15 June 2012 19:18
		Re: segmentation violation in reco macro -- GEANT related? By: StefanoSpataro on Fri, 15 June 2012 20:27
		Re: segmentation violation in reco macro -- GEANT related? By: MartinJGaluska on Sun, 17 June 2012 15:09

Previous Topic:	Crash in reco macro: "PndSttMvdTracking, nMvdPixelHitsinTrack[4] is 58and it is > nmaxMvdPix
Next Topic:	[FIXED] Possibly a bug in MC Truth Forwarding (?) - no bug after all [SOLVED]

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

] [

]

Current Time: Fri Apr 26 08:46:47 CEST 2024

Total time taken to generate the page: 0.01030 seconds