GSI Forum - RDF feed
type: channel
description: GSI Helmholtzzentrum für Schwerionenforschung
items: Reconstruction macro crash
items: Re: Reconstruction macro crash

Reconstruction macro crash
type: item
description: Hello, running un_reco_stt_evt.C in macro/run/tdrct I have the following error. I have it in may11 package but also in feb11 package. Could you please halp me? Thanks, Elisa Found Tracks: 0 in event no. 33 ---------------- *** Break *** floating point exception Generating stack trace... 0xb0eea6c7 in ertrch_ + 0xd93 from /home/fioravanti/fairsoft/transport/geant3/lib/tgt_linux/libgeant321.so 0xb0eec4a5 in ertrgo_ + 0xf29 from /home/fioravanti/fairsoft/transport/geant3/lib/tgt_linux/libgeant321.so 0xb0ee98b9 in ertrak_ + 0xc15 from /home/fioravanti/fairsoft/transport/geant3/lib/tgt_linux/libgeant321.so 0xb0fcb450 in TGeant3::Ertrak(float const*, float const*, float const*, float const*, int, char const*) + 0x62 from /home/fioravanti/fairsoft/transport/geant3/lib/tgt_linux/libgeant321.so 0x08f1008a in FairGeanePro::Propagate(int) at /home/fioravanti/fairsoft/pandaroot/geane/FairGeanePro.cxx:327 from /home/fioravanti/fairsoft/buildPanda/lib/libGeane.so 0x08f10c71 in FairGeanePro::Propagate(FairTrackParP*, FairTrackParP*, int) at /home/fioravanti/fairsoft/pandaroot/geane/FairGeanePro.cxx:275 from /home/fioravanti/fairsoft/buildPanda/lib/libGeane.so 0x050db6be in PndSttMvdGemTracking::PropagateToGemPlane(FairTrackParP*, FairTrackParP*, int) at /home/fioravanti/fairsoft/pandaroot/sttmvdtracking/PndSttMvdGemTracking. cxx:949 from /home/fioravanti/fairsoft/buildPanda/lib/libSttMvdTracking.so 0x050de15a in PndSttMvdGemTracking::Retrack() at /home/fioravanti/fairsoft/pandaroot/sttmvdtracking/PndSttMvdGemTracking. cxx:1435 from /home/fioravanti/fairsoft/buildPanda/lib/libSttMvdTracking.so 0x050e2441 in PndSttMvdGemTracking::Exec(char const*) at /home/fioravanti/fairsoft/pandaroot/sttmvdtracking/PndSttMvdGemTracking. cxx:648 from /home/fioravanti/fairsoft/buildPanda/lib/libSttMvdTracking.so 0x0027e9e8 in TTask::ExecuteTasks(char const*) + 0x108 from /home/fioravanti/fairsoft/tools/root/lib/libCore.so.5.29 0x0027e3d9 in TTask::ExecuteTask(char const*) + 0x159 from /home/fioravan…
creator: Elisa Fioravanti
date: 2011-05-19T14:49:03-00:00

Re: Reconstruction macro crash
type: item
description: Ciao Elisa, does it happen on a specific event or does it happen always? Lia.
creator: Lia Lavezzi
date: 2011-05-19T15:00:00-00:00

Re: Reconstruction macro crash
type: item
description: Ciao Lia, it is completely random, yesterday I got it on 670 event, then about 300 event, today 33 event... thanks Elisa
creator: Elisa Fioravanti
date: 2011-05-19T15:02:05-00:00

Re: Reconstruction macro crash
type: item
description: Ok, I will try to reproduce it... just give me the time to install the last external packages... I will let you know, ciao, Lia.
creator: Lia Lavezzi
date: 2011-05-19T15:21:59-00:00

Re: Reconstruction macro crash
type: item
description: Ciao Lia, I have the same problem also in the feb11 package, if I simulate 500 or 1000 events, Elisa
creator: Elisa Fioravanti
date: 2011-05-19T15:37:58-00:00

Re: Reconstruction macro crash
type: item
description: Hi Elisa, I simulated and reconstructed 1000 events without the crash... now I am doing the same with others 1000 events (different seed) to see whether it was just luck! In the meanwhile, can you please try the reco with PndSttMvdGemTracking * SttMvdGemTracking = new PndSttMvdGemTracking(1); with the 1 instead of 0, i.e. in verbosity mode, and send me the log file of the crashing event? Maybe I can find out the problem in the log messages... Thanks, Lia.
creator: Lia Lavezzi
date: 2011-05-20T13:46:01-00:00

Re: Reconstruction macro crash
type: item
description: Hello Lia, I simulated again 1000 events, and I have the same crash at the same event number. The following is the error. Thanks Elisa Found Tracks: 0 in event no. 2 ---------------- PROBLEM HAS NO FEASIBLE SOLUTION ==================== EVENT 2 stt + mvd track array 5 gem hits 8 ******* PndSttMvdGemTracking::Reset ******* not assig 8 8 npositions/nhits 6 8 hit 0 @ 13.61 -26.95 116.4 1 1 11 0 0 hit 1 @ -4.861 21.76 116.4 1 1 11 1 0 hit 2 @ 12.97 -27.11 117.6 1 2 12 0 1 hit 3 @ -5.010 22.05 117.6 1 2 12 1 1 hit 4 @ -6.395 30.94 152.4 2 1 21 0 2 hit 5 @ -6.510 31.25 153.6 2 2 22 0 3 hit 6 @ -7.312 40.21 188.4 3 1 31 0 4 hit 7 @ -7.490 40.51 189.6 3 2 32 0 5 pos 0 1 pos 1 1 pos 2 1 pos 3 1 pos 4 1 pos 5 1 PRIMA iHit 7 detId 16(36) PRIMA iHit 8 detId 16(36) PRIMA iHit 9 detId 16(36) PRIMA iHit 10 detId 16(36) PRIMA iHit 11 detId 16(36) PRIMA iHit 12 detId 16(36) PRIMA iHit 13 detId 16(36) PRIMA iHit 14 detId 16(36) PRIMA iHit 15 detId 16(36) PRIMA iHit 16 detId 16(36) PRIMA iHit 17 detId 16(36) PRIMA iHit 18 detId 16(36) PRIMA iHit 19 detId 16(36) PRIMA iHit 20 detId 16(36) PRIMA iHit 21 detId 16(36) PRIMA iHit 22 detId 16(36) PRIMA iHit 23 detId 16(36) PRIMA iHit 24 detId 16(36) PRIMA iHit 25 detId 16(36) PRIMA iHit 26 detId 16(36) PRIMA iHit 27 detId 16(36) PRIMA iHit 28 detId 16(36) PRIMA iHit 29 detId 16(36) PRIMA iHit 30 detId 16(36) PRIMA iHit 31 detId 16(36) PRIMA iHit 32 detId 16(36) start from TVector3 A 3D physics vector (x,y,z)=(39.336944,-5.623349,30.272836) (rho,theta,phi)=(49.954598,52.698661,-8.135506) lastpar error 0.02000 0.02000 1.000 OUT OF SENSOR 107.4 -89.38 45.00 CANNOT PROPAGATE PRIMA iHit 34 detId 16(36) PRIMA iHit 35 detId 16(36) PRIMA iHit 36 detId 16(36) PRIMA iHit 37 detId 16(36) PRIMA iHit 38 detId 16(36) PRIMA iHit 39 detId 16(36) PRIMA iHit 40 detId 16(36) PRIMA iHit 41 detId 16(36) PRIMA iHit 42 detId 16(36) PRIMA iHit 43 detId 16(36) PRIMA iHit 44 detId 16(36) start from TVector3 A 3D physics vector (x,y,z)=(7.658246,39.033931,42.024698) …
creator: Elisa Fioravanti
date: 2011-05-20T14:07:44-00:00

Re: Reconstruction macro crash
type: item
description: Hello, I look into: pandaroot/sttmvdtracking/PndSttMvdGemTracking.cxx and I try to print out the value of fpdgCode,tmppar and gempar. I run again the reconstruction macro and before the crash (that I have at the same event as before) I find this following value. I read e-248. Is it not strange? The other value are e-17. Hope it helps, thanks Elisa propagation from TVector3 A 3D physics vector (x,y,z)=(14.075058,-26.674008,-4.163533) (rho,theta,phi)=(30.445771,97.859966,-62.180759) pdg: -13 Position : (14., -27., -4.2) Slopes : dx/dz = -1.5e-17, dy/dz = 1.5e-248 q/p = 11. Position : (0.0, 0.0, 0.0) Slopes : dx/dz = 0.0, dy/dz = 0.0 q/p = 0.0 *** Break *** floating point exception
creator: Elisa Fioravanti
date: 2011-05-20T14:37:51-00:00

Re: Reconstruction macro crash
type: item
description: Hi Elisa, Quote: I read e-248. Is it not strange? The other value are e-17. yes, that' s should not happen... I still do not see the crash in my events, but I was able to force it just putting as starting values the ones from your log (thank you for posting it). Now I should be able to see directly what is the problem and (hopefully) fix it. Stay tuned, Lia.
creator: Lia Lavezzi
date: 2011-05-20T15:27:18-00:00

Re: Reconstruction macro crash
type: item
description: Hi again, I really think the problem is that the z component of the start momentum is 0, but I need to make one further check to be sure. Can you please update your sttmvdtracking directory, rerun the reco in verbose mode and post the new log file? I added to the PndSttMvdGemTracking a few more print outs to understand what happens... Thank you, sorry if I ask you to run all this stuff but the change I put by hand in my code is not enough to test this part. Lia.
creator: Lia Lavezzi
date: 2011-05-20T15:47:20-00:00

Re: Reconstruction macro crash
type: item
description: Hello Lia, sorry for the delay in my answer but I'm travelling (and my flight was post-poned on this afternoon ). So I update my sttmvdtracking directory, and I rerun the reco in verbose mode. Here you can see the log file. The crash is in the event number 2, but I post also the log file about the event number 1, so you can compare the two events. Thanks a lot Elisa Found Tracks: 2 in event no. 1 ---------------- ==================== EVENT 1 stt + mvd track array 2 gem hits 6 ******* PndSttMvdGemTracking::Reset ******* not assig 6 6 npositions/nhits 6 6 hit 0 @ -31.20 -21.33 116.4 1 1 11 0 0 hit 1 @ -31.55 -21.51 117.6 1 2 12 0 1 hit 2 @ -41.68 -26.57 152.4 2 1 21 0 2 hit 3 @ -41.97 -26.87 153.6 2 2 22 0 3 hit 4 @ -52.23 -31.57 188.4 3 1 31 0 4 hit 5 @ -52.51 -31.91 189.6 3 2 32 0 5 pos 0 1 pos 1 1 pos 2 1 pos 3 1 pos 4 1 pos 5 1 PRIMA iHit 0 detId 21(36) PRIMA iHit 1 detId 21(36) PRIMA iHit 0 detId 23(36) PRIMA iHit 1 detId 23(36) PRIMA iHit 0 detId 16(36) PRIMA iHit 1 detId 16(36) PRIMA iHit 2 detId 16(36) PRIMA iHit 3 detId 16(36) PRIMA iHit 4 detId 16(36) PRIMA iHit 5 detId 16(36) PRIMA iHit 6 detId 16(36) PRIMA iHit 7 detId 16(36) PRIMA iHit 8 detId 16(36) PRIMA iHit 9 detId 16(36) PRIMA iHit 10 detId 16(36) PRIMA iHit 11 detId 16(36) PRIMA iHit 12 detId 16(36) PRIMA iHit 13 detId 16(36) PRIMA iHit 14 detId 16(36) PRIMA iHit 15 detId 16(36) PRIMA iHit 16 detId 16(36) PRIMA iHit 17 detId 16(36) PRIMA iHit 18 detId 16(36) PRIMA iHit 19 detId 16(36) PRIMA iHit 20 detId 16(36) PRIMA iHit 21 detId 16(36) PRIMA iHit 22 detId 16(36) PRIMA iHit 23 detId 16(36) start from TVector3 A 3D physics vector (x,y,z)=(27.493812,28.485022,13.169421) (rho,theta,phi)=(41.722175,71.600207,46.014423) lastpar error 0.02000 0.02000 1.000 GET INITIAL PARAMS charge/xc/yc/radius -1 -131.2 154.3 202.5 TVector3 A 3D physics vector (x,y,z)=(0.914593,0.800286,0.403600) (rho,theta,phi)=(1.280559,71.628634,41.186545) TVector3 A 3D physics vector (x,y,z)=(2.140019,1.838233,0.935000) (rho,theta,p…
creator: Elisa Fioravanti
date: 2011-05-21T15:43:32-00:00

Re: Reconstruction macro crash
type: item
description: Hi Elisa, thank you for the post. It really seems the problem is the starting momentum z component, so I just uploaded to svn a modified PndSttMvdGemTracking.cxx that should fix the problem. If the crash is still there, please let me know! Ciao, Lia.
creator: Lia Lavezzi
date: 2011-05-22T12:20:46-00:00

Re: Reconstruction macro crash
type: item
description: Hello Lia, unfortunately I have the same crash as before. Here you can see the log file. thank you Elisa Found Tracks: 0 in event no. 140 ---------------- PROBLEM HAS NO FEASIBLE SOLUTION ==================== EVENT 140 stt + mvd track array 5 gem hits 8 ******* PndSttMvdGemTracking::Reset ******* not assig 8 8 npositions/nhits 6 8 hit 0 @ 13.61 -26.95 116.4 1 1 11 0 0 hit 1 @ -4.861 21.76 116.4 1 1 11 1 0 hit 2 @ 12.97 -27.11 117.6 1 2 12 0 1 hit 3 @ -5.010 22.05 117.6 1 2 12 1 1 hit 4 @ -6.395 30.94 152.4 2 1 21 0 2 hit 5 @ -6.510 31.25 153.6 2 2 22 0 3 hit 6 @ -7.312 40.21 188.4 3 1 31 0 4 hit 7 @ -7.490 40.51 189.6 3 2 32 0 5 pos 0 1 pos 1 1 pos 2 1 pos 3 1 pos 4 1 pos 5 1 PRIMA iHit 7 detId 16(36) PRIMA iHit 8 detId 16(36) PRIMA iHit 9 detId 16(36) PRIMA iHit 10 detId 16(36) PRIMA iHit 11 detId 16(36) PRIMA iHit 12 detId 16(36) PRIMA iHit 13 detId 16(36) PRIMA iHit 14 detId 16(36) PRIMA iHit 15 detId 16(36) PRIMA iHit 16 detId 16(36) PRIMA iHit 17 detId 16(36) PRIMA iHit 18 detId 16(36) PRIMA iHit 19 detId 16(36) PRIMA iHit 20 detId 16(36) PRIMA iHit 21 detId 16(36) PRIMA iHit 22 detId 16(36) PRIMA iHit 23 detId 16(36) PRIMA iHit 24 detId 16(36) PRIMA iHit 25 detId 16(36) PRIMA iHit 26 detId 16(36) PRIMA iHit 27 detId 16(36) PRIMA iHit 28 detId 16(36) PRIMA iHit 29 detId 16(36) PRIMA iHit 30 detId 16(36) PRIMA iHit 31 detId 16(36) PRIMA iHit 32 detId 16(36) start from TVector3 A 3D physics vector (x,y,z)=(39.336944,-5.623349,30.272836) (rho,theta,phi)=(49.954598,52.698661,-8.135506) lastpar error 0.02000 0.02000 1.000 GET INITIAL PARAMS charge/xc/yc/radius 1 5.431 -102.4 102.8 TVector3 A 3D physics vector (x,y,z)=(0.612841,-0.067291,0.466725) (rho,theta,phi)=(0.773263,52.873333,-6.266050) TVector3 A 3D physics vector (x,y,z)=(16.645778,-0.261378,12.602661) (rho,theta,phi)=(20.880070,52.873723,-0.899604) TVector3 A 3D physics vector (x,y,z)=(0.581943,-0.203581,0.466725) (rho,theta,phi)=(0.773263,52.873333,-19.281329) TVector3 A 3D physics vector (x,y,z)=(39.33694…
creator: Elisa Fioravanti
date: 2011-05-23T09:59:36-00:00

Re: Reconstruction macro crash
type: item
description: Hi Elisa, I added a couple more print outs to check the starting momentum after my prefit, can you please update, rerun and post the messages again? (sorry! ) Thanks, Lia.
creator: Lia Lavezzi
date: 2011-05-23T11:22:23-00:00

Re: Reconstruction macro crash
type: item
description: Hi, I don't know how the stt+mvd+gem code works, but I an wondering if all the tracks are extrapolated to gem planes or only the "forward ones". IO mean, I think that if a track has theta > 30° it will have no chance to hit the gem planes. f such a cut is not present n the code, maybe it could be good to put it, pz will be much bigger than 0, thus no problems. Could it help? Or maybe this is already included in the code?
creator: StefanoSpataro
date: 2011-05-23T11:23:13-00:00

Re: Reconstruction macro crash
type: item
description: Hello Lia this is the new log file: thanks a lot for your help, elisa Found Tracks: 0 in event no. 2 ---------------- PROBLEM HAS NO FEASIBLE SOLUTION ==================== EVENT 2 stt + mvd track array 5 gem hits 8 ******* PndSttMvdGemTracking::Reset ******* not assig 8 8 npositions/nhits 6 8 hit 0 @ 13.61 -26.95 116.4 1 1 11 0 0 hit 1 @ -4.861 21.76 116.4 1 1 11 1 0 hit 2 @ 12.97 -27.11 117.6 1 2 12 0 1 hit 3 @ -5.010 22.05 117.6 1 2 12 1 1 hit 4 @ -6.395 30.94 152.4 2 1 21 0 2 hit 5 @ -6.510 31.25 153.6 2 2 22 0 3 hit 6 @ -7.312 40.21 188.4 3 1 31 0 4 hit 7 @ -7.490 40.51 189.6 3 2 32 0 5 pos 0 1 pos 1 1 pos 2 1 pos 3 1 pos 4 1 pos 5 1 PRIMA iHit 7 detId 16(36) PRIMA iHit 8 detId 16(36) PRIMA iHit 9 detId 16(36) PRIMA iHit 10 detId 16(36) PRIMA iHit 11 detId 16(36) PRIMA iHit 12 detId 16(36) PRIMA iHit 13 detId 16(36) PRIMA iHit 14 detId 16(36) PRIMA iHit 15 detId 16(36) PRIMA iHit 16 detId 16(36) PRIMA iHit 17 detId 16(36) PRIMA iHit 18 detId 16(36) PRIMA iHit 19 detId 16(36) PRIMA iHit 20 detId 16(36) PRIMA iHit 21 detId 16(36) PRIMA iHit 22 detId 16(36) PRIMA iHit 23 detId 16(36) PRIMA iHit 24 detId 16(36) PRIMA iHit 25 detId 16(36) PRIMA iHit 26 detId 16(36) PRIMA iHit 27 detId 16(36) PRIMA iHit 28 detId 16(36) PRIMA iHit 29 detId 16(36) PRIMA iHit 30 detId 16(36) PRIMA iHit 31 detId 16(36) PRIMA iHit 32 detId 16(36) start from TVector3 A 3D physics vector (x,y,z)=(39.336944,-5.623349,30.272836) (rho,theta,phi)=(49.954598,52.698661,-8.135506) lastpar error 0.02000 0.02000 1.000 GET INITIAL PARAMS charge/xc/yc/radius 1 5.431 -102.4 102.8 TVector3 A 3D physics vector (x,y,z)=(0.612841,-0.067291,0.466725) (rho,theta,phi)=(0.773263,52.873333,-6.266050) TVector3 A 3D physics vector (x,y,z)=(16.645778,-0.261378,12.602661) (rho,theta,phi)=(20.880070,52.873723,-0.899604) TVector3 A 3D physics vector (x,y,z)=(0.581943,-0.203581,0.466725) (rho,theta,phi)=(0.773263,52.873333,-19.281329) TVector3 A 3D physics vector (x,y,z)=(39.336944,-5.623349,30.272836) (rho,theta,phi)=…
creator: Elisa Fioravanti
date: 2011-05-23T11:32:12-00:00

Re: Reconstruction macro crash
type: item
description: Hi Stefano, actually there is a test to decide whether the track can reach the GEM plane or not with a simple and quick helix extrapolation to the first plane (no GEANE, just math). In my thoughts that should have been enough to throw away also these pz = 0 tracks, but clearly there is something which goes wrong. ...I was wondering (looking in the log) how is it possible that a track with: first mom = (0.077671,-0.047670,0.000000) first pos = (16.552964,0.397360,0.000000) last mom = (-0.085107,-0.032588,0.000000) has last pos = (14.075058,-26.674008,-4.163533)... Gianluigi, this comes from your PR, do you have any idea? Ciao, Lia.
creator: Lia Lavezzi
date: 2011-05-23T11:36:25-00:00

Re: Reconstruction macro crash
type: item
description: Thanks Elisa, I changed the code again, please try now (and tell me it works ! ) Lia.
creator: Lia Lavezzi
date: 2011-05-23T11:47:08-00:00

Re: Reconstruction macro crash
type: item
description: Hello Lia, unfortunately it is not working yet. Here the log file Thanks a lot elisa Found Tracks: 0 in event no. 2 ---------------- PROBLEM HAS NO FEASIBLE SOLUTION ==================== EVENT 2 stt + mvd track array 5 gem hits 8 ******* PndSttMvdGemTracking::Reset ******* not assig 8 8 npositions/nhits 6 8 hit 0 @ 13.61 -26.95 116.4 1 1 11 0 0 hit 1 @ -4.861 21.76 116.4 1 1 11 1 0 hit 2 @ 12.97 -27.11 117.6 1 2 12 0 1 hit 3 @ -5.010 22.05 117.6 1 2 12 1 1 hit 4 @ -6.395 30.94 152.4 2 1 21 0 2 hit 5 @ -6.510 31.25 153.6 2 2 22 0 3 hit 6 @ -7.312 40.21 188.4 3 1 31 0 4 hit 7 @ -7.490 40.51 189.6 3 2 32 0 5 pos 0 1 pos 1 1 pos 2 1 pos 3 1 pos 4 1 pos 5 1 PRIMA iHit 7 detId 16(36) PRIMA iHit 8 detId 16(36) PRIMA iHit 9 detId 16(36) PRIMA iHit 10 detId 16(36) PRIMA iHit 11 detId 16(36) PRIMA iHit 12 detId 16(36) PRIMA iHit 13 detId 16(36) PRIMA iHit 14 detId 16(36) PRIMA iHit 15 detId 16(36) PRIMA iHit 16 detId 16(36) PRIMA iHit 17 detId 16(36) PRIMA iHit 18 detId 16(36) PRIMA iHit 19 detId 16(36) PRIMA iHit 20 detId 16(36) PRIMA iHit 21 detId 16(36) PRIMA iHit 22 detId 16(36) PRIMA iHit 23 detId 16(36) PRIMA iHit 24 detId 16(36) PRIMA iHit 25 detId 16(36) PRIMA iHit 26 detId 16(36) PRIMA iHit 27 detId 16(36) PRIMA iHit 28 detId 16(36) PRIMA iHit 29 detId 16(36) PRIMA iHit 30 detId 16(36) PRIMA iHit 31 detId 16(36) PRIMA iHit 32 detId 16(36) start from TVector3 A 3D physics vector (x,y,z)=(39.336944,-5.623349,30.272836) (rho,theta,phi)=(49.954598,52.698661,-8.135506) lastpar error 0.02000 0.02000 1.000 GET INITIAL PARAMS charge/xc/yc/radius 1 5.431 -102.4 102.8 TVector3 A 3D physics vector (x,y,z)=(0.612841,-0.067291,0.466725) (rho,theta,phi)=(0.773263,52.873333,-6.266050) TVector3 A 3D physics vector (x,y,z)=(16.645778,-0.261378,12.602661) (rho,theta,phi)=(20.880070,52.873723,-0.899604) TVector3 A 3D physics vector (x,y,z)=(0.581943,-0.203581,0.466725) (rho,theta,phi)=(0.773263,52.873333,-19.281329) TVector3 A 3D physics vector (x,y,z)=(39.336944,-5.623349,30.272836) (…
creator: Elisa Fioravanti
date: 2011-05-23T11:53:15-00:00

Re: Reconstruction macro crash
type: item
description: I added some more print outs, since it does not seem to see a continue I put there and I cannot get why... Can you please update and post the new log (or send it directly to me if you prefer since we are just doing debugging)? Thanks, Lia.
creator: Lia Lavezzi
date: 2011-05-23T12:21:00-00:00

Re: Reconstruction macro crash
type: item
description: Lia Lavezzi wrote on Mon, 23 May 2011 13:36 Hi Stefano, actually there is a test to decide whether the track can reach the GEM plane or not with a simple and quick helix extrapolation to the first plane (no GEANE, just math). In my thoughts that should have been enough to throw away also these pz = 0 tracks, but clearly there is something which goes wrong. ...I was wondering (looking in the log) how is it possible that a track with: first mom = (0.077671,-0.047670,0.000000) first pos = (16.552964,0.397360,0.000000) last mom = (-0.085107,-0.032588,0.000000) has last pos = (14.075058,-26.674008,-4.163533)... Gianluigi, this comes from your PR, do you have any idea? Ciao, Lia. In principle no physics prevents from having a track with Pz=0, and the Pattern Recognition in fact can find a track with Pz =0. Pz =0 when one of the parameter I use to parametrize the Helix is very large. Also, Pz=0 for a track is not in contraddiction, from the Pattern Recognition algorithm point of view, with having the Z position of the last point NOT EXACTLY 0; certainly it must be CLOSE to zero [as in the this example, where last pos = (14.075058,-26.674008,-4.163533) ]. Anyway, I am investigating possible bugs in the code right now Gianluigi
creator: Gianluigi Boca
date: 2011-05-23T13:57:09-00:00

Re: Reconstruction macro crash
type: item
description: Lia Lavezzi wrote on Mon, 23 May 2011 13:36 Hi first mom = (0.077671,-0.047670,0.000000) first pos = (16.552964,0.397360,0.000000) last mom = (-0.085107,-0.032588,0.000000) has last pos = (14.075058,-26.674008,-4.163533)... Gianluigi, this comes from your PR, do you have any idea? Ciao, Lia. I put in Svn a fix to a particular situation arising in the Pattern Recognition when a track doesn't have any Stt Skew Hits nor Mvd hits associated. I am not sure, but that may be the cause of the crash observed by Elisa. So please update PndSttMvdTracking.cxx and .h and try again Gianluigi
creator: Gianluigi Boca
date: 2011-05-24T00:15:18-00:00

Re: Reconstruction macro crash
type: item
description: Moreover, the PndSttMvdGemTracking is now protected from tracks with initial pz = 0 since it is quite clear that they will not be extrapolated to the GEM planes... Lia.
creator: Lia Lavezzi
date: 2011-05-24T08:46:07-00:00

Re: Reconstruction macro crash
type: item
description: Hello, the problem is now fixed and the reconstruction macro for stt doesn't crash anymore. thanks a lot to everyone who helps me Elisa
creator: Elisa Fioravanti
date: 2011-05-25T12:38:16-00:00

Re: Reconstruction macro crash
type: item
description: ... one less...
creator: StefanoSpataro
date: 2011-05-25T12:41:13-00:00