GSI Forum
GSI Helmholtzzentrum für Schwerionenforschung

Home » PANDA » PandaRoot » Bugs, Fixes, Releases » Crash in reco macro: "PndSttMvdTracking, nMvdPixelHitsinTrack[4] is 58and it is > nmaxMvdPix
Crash in reco macro: "PndSttMvdTracking, nMvdPixelHitsinTrack[4] is 58and it is > nmaxMvdPix [message #13601] Thu, 14 June 2012 15:35 Go to next message
MartinJGaluska is currently offline  MartinJGaluska
Messages: 203
Registered: March 2010
Location: Germany
first-grade participant
From: *physik.uni-giessen.de
Hello,

I have just encountered this problem (see spoiler) while running a 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 previously run the same simulation with the same version of PandaRoot and have not seen this problem.

I have restarted the macro in order to see if the problem reoccurs.


Toggle Spoiler

[Updated on: Thu, 14 June 2012 17:27]

Report message to a moderator

Re: Crash in reco macro: "PndSttMvdTracking, nMvdPixelHitsinTrack[4] is 58and it is > nmaxMv [message #13602 is a reply to message #13601] Thu, 14 June 2012 17:27 Go to previous messageGo to next message
MartinJGaluska is currently offline  MartinJGaluska
Messages: 203
Registered: March 2010
Location: Germany
first-grade participant
From: *physik.uni-giessen.de
I have seen that

trunk/sttmvdtracking/PndSttMvdTracking.cxx

was modified recently and have updated the trunk/sttmvdtracking folder. After compiling, I ran the reco macro again with the updated files and the same crash occured again in event 490.
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 Go to previous messageGo to next message
Jens Sören Lange is currently offline  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 ...
Re: Crash in reco macro: "PndSttMvdTracking, nMvdPixelHitsinTrack[4] is 58and it is > nmaxMv [message #13605 is a reply to message #13604] Fri, 15 June 2012 10:51 Go to previous messageGo to next message
Lia Lavezzi
Messages: 291
Registered: May 2007
Location: Torino
first-grade participant

From: *pv.infn.it
Dear Martin and Soeren,
the variable you want to change is nmaxMvdPixelHitsInTrack, which is set in line 103 of sttmvdtracking/PndSttMvdTracking.h.
It is in the compiled code, so you will have to recompile.

This code has been written by Gianluigi, who was on a conference in Varenna in these days. I just talked to him on the phone and he told me he is coming back to Pavia. I will see him this afternoon, so please try this fix and if it does not work let us know.

Best regards,
Lia.
Re: Crash in reco macro: "PndSttMvdTracking, nMvdPixelHitsinTrack[4] is 58and it is > nmaxMv [message #13607 is a reply to message #13605] Fri, 15 June 2012 12:27 Go to previous message
MartinJGaluska is currently offline  MartinJGaluska
Messages: 203
Registered: March 2010
Location: Germany
first-grade participant
From: *physik.uni-giessen.de
Dear Lia and Gianluigi,

thank you for your message. I have set nmaxMvdPixelHitsInTrack from 30 to 60, recompiled PandaRoot and have not seen a segmentation violation in event 490 any more. It seems that adjusting this value has solved the problem.
Previous Topic: simulation macro finished with error
Next Topic: segmentation violation in reco macro
Goto Forum:
  


Current Time: Sat Mar 02 14:39:26 CET 2024

Total time taken to generate the page: 0.00942 seconds