GSI Forum - RDF feed
type: channel
description: GSI Helmholtzzentrum für Schwerionenforschung
items: TpcRiemannTrackingTask - ideal PID now working - please rerun reconstruction
items: Re: TpcRiemannTrackingTask - ideal PID now working - please rerun reconstruction

TpcRiemannTrackingTask - ideal PID now working - please rerun reconstruction
type: item
description: Dear Pandarooters, finally we fixed the issues we had with the ideal PID in the RiemannTrackingTask. You can use ideal pid in the reco macros: tpcSPR->SetMCPid(); // use ideal particle identification Please test your reconstruction/analysis macros on a small sample and give feedback. Then the tpc data on the grid should be reprocessed for the final analysis. regards, Johannes
creator: Johannes Rauch
date: 2011-08-01T19:58:04-00:00

Re: TpcRiemannTrackingTask - ideal PID now working - please rerun reconstruction
type: item
description: New TPC jobs were just submitted on the grid with the new august11 release, and the latest fixes in tpc reconstruction. Le't see...
creator: StefanoSpataro
date: 2011-08-02T09:20:04-00:00

Re: TpcRiemannTrackingTask - ideal PID now working - please rerun reconstruction
type: item
description: Hello, I have update pandaroot, and I have run the simulation ofr pi+pi- analysis using the macro in /macro/run/tdrct/npipi I comment out the line tpcSPR->SetMCPid(); // use ideal particle identification in the reco macro. But unfortunately I have this crash: ===== PndPidCorrelator - Event: 822 - Number of tracks for pid 1 - Number of EMC Cluster for pid 27 -W- PndPidCorrelator::GetTrackInfo :: Failed backward propagation *** Break *** floating point exception Generating stack trace... 0x06136b40 in PndPidCandidate::PndPidCandidate(PndPidCandidate const&) at /home/fioravanti/fairsoft/pandaroot/pid/PidData/PndPidCandidate.h:31 from /home/fioravanti/fairsoft/buildPanda/lib/libPid.so 0x0612bfd2 in PndPidCorrelator::AddNeutralCandidate(PndPidCandidate*) at /home/fioravanti/fairsoft/pandaroot/pid/PidCorr/PndPidCorrelator.cxx:119 7 from /home/fioravanti/fairsoft/buildPanda/lib/libPid.so 0x061300a0 in PndPidCorrelator::ConstructNeutralCandidate() at /home/fioravanti/fairsoft/pandaroot/pid/PidCorr/PndPidCorrelator.cxx:663 from /home/fioravanti/fairsoft/buildPanda/lib/libPid.so 0x0613137e in PndPidCorrelator::Exec(char const*) at /home/fioravanti/fairsoft/pandaroot/pid/PidCorr/PndPidCorrelator.cxx:540 from /home/fioravanti/fairsoft/buildPanda/lib/libPid.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/fioravanti/fairsoft/tools/root/lib/libCore.so.5.29 0x02a61d23 in FairRunAna::Run(int, int) at /home/fioravanti/fairsoft/pandaroot/base/FairRunAna.cxx:354 from /home/fioravanti/fairsoft/buildPanda/lib/libBase.so 0x02ac3a38 in <unknown> from /home/fioravanti/fairsoft/buildPanda/lib/libBase.so 0x00c45d7a in Cint::G__ExceptionWrapper(int (*)(G__value*, char const*, G__param*, int), G__value*, char*, G__param*, int) + 0x6a from /home/fioravanti/fairsoft/tools/root/lib/libCint.so.5.29 0x00d00786 in G__execute_call + 0x56 from /home/fioravanti/fairsof…
creator: Elisa Fioravanti
date: 2011-08-02T09:21:29-00:00

Re: TpcRiemannTrackingTask - ideal PID now working - please rerun reconstruction
type: item
description: Hi Elisa, this looks to me like a crash in the FairGeanePro extrapolation inside pid/GetTrackInfo.cxx. Is this another random floating point exception from Geane? Can you verify that, Stefano? Inside the TPC code we use genfit tracks (instead the PndTracks) and use another track representation (RKTrackRep) for our extrapolations. We had no such problems since then. But this is decoupled from the problem you see. Cheers Felix
creator: Felix Boehmer
date: 2011-08-02T09:42:02-00:00

Re: TpcRiemannTrackingTask - ideal PID now working - please rerun reconstruction
type: item
description: Hi Elisa and Felix, Quote: this looks to me like a crash in the FairGeanePro extrapolation inside pid/GetTrackInfo.cxx. Is this another random floating point exception from Geane? Can you verify that, Stefano? I don' t think it is GEANE, from the backtrace it seems that the crash happens in the neutral candidate creation: Quote: 0x06136b40 in PndPidCandidate::PndPidCandidate(PndPidCandidate const&) at /home/fioravanti/fairsoft/pandaroot/pid/PidData/PndPidCandidate.h:31 from /home/fioravanti/fairsoft/buildPanda/lib/libPid.so 0x0612bfd2 in PndPidCorrelator::AddNeutralCandidate(PndPidCandidate*) at /home/fioravanti/fairsoft/pandaroot/pid/PidCorr/PndPidCorrelator.cxx:119 7 from /home/fioravanti/fairsoft/buildPanda/lib/libPid.so 0x061300a0 in PndPidCorrelator::ConstructNeutralCandidate() at /home/fioravanti/fairsoft/pandaroot/pid/PidCorr/PndPidCorrelator.cxx:663 from /home/fioravanti/fairsoft/buildPanda/lib/libPid.so so if you run the pid correlator with SetEmcMode(0) it should skip this part and the crash should not happen anymore (I hope). Cheers, Lia.
creator: Lia Lavezzi
date: 2011-08-02T10:32:33-00:00

Re: TpcRiemannTrackingTask - ideal PID now working - please rerun reconstruction
type: item
description: Hi Lia I implemented the fix you proposed, this makes the pid-macro crash at a later event with the following stack trace. This points towards geane, as it crashed during propagation using geane. Best regards Sverre *** Break *** floating point exception =========================================================== There was a crash (#7 0xb71bee3d in SigHandler(ESignals) ()). This is the entire stack trace of all threads: =========================================================== #0 0xb76ed424 in __kernel_vsyscall () #1 0xb6580003 in __waitpid_nocancel () at ../sysdeps/unix/syscall-template.S:82 #2 0xb6521e63 in do_system (line=<value optimized out>) at ../sysdeps/posix/system.c:149 #3 0xb663d3bd in system ( line=0x30d42650 " /nfs/hicran/project/panda/SIM/FAIRRoot/fairsoft_release_may11/tools/root _5.28d_qt_custom_TH2Poly/etc/gdb-backtrace.sh 12515 1>&2") at pt-system.c:29 #4 0xb71b933d in TUnixSystem::Exec(char const*) () from /nfs/hicran/project/panda/SIM/FAIRRoot/fairsoft_release_may11/tools/root _5.28d_qt_custom_TH2Poly/lib/libCore.so #5 0xb71bf91a in TUnixSystem::StackTrace() () from /nfs/hicran/project/panda/SIM/FAIRRoot/fairsoft_release_may11/tools/root _5.28d_qt_custom_TH2Poly/lib/libCore.so #6 0xb71bed2f in TUnixSystem::DispatchSignals(ESignals) () from /nfs/hicran/project/panda/SIM/FAIRRoot/fairsoft_release_may11/tools/root _5.28d_qt_custom_TH2Poly/lib/libCore.so #7 0xb71bee3d in SigHandler(ESignals) () from /nfs/hicran/project/panda/SIM/FAIRRoot/fairsoft_release_may11/tools/root _5.28d_qt_custom_TH2Poly/lib/libCore.so #8 0xb71b5ee2 in sighandler(int) () from /nfs/hicran/project/panda/SIM/FAIRRoot/fairsoft_release_may11/tools/root _5.28d_qt_custom_TH2Poly/lib/libCore.so #9 <signal handler called> #10 0xb0b8ce9d in FairGeanePro::Propagate (this=0x30d44cc8, TParam=0x30d44a38, TEnd=0x30d44f70, PDG=-211) at /nfs/hicran/project/panda/SIM/sdorheim/Programming/pandaROOT/cleanTrunk/ geane/FairGeanePro.cxx:143 #11 0xaffdeb1f in PndPidCorrelator::GetTrackInfo (this=0…
creator: Sverre Dørheim
date: 2011-08-02T11:03:27-00:00

Re: TpcRiemannTrackingTask - ideal PID now working - please rerun reconstruction
type: item
description: The neutral candidate problem is related to memory issues appearing seldomly only in few distributions/compiler versions, and it does not affect grid production. I can only suggest to comment out the call to the functioning the pid correlator.
creator: StefanoSpataro
date: 2011-08-02T11:33:41-00:00

Re: TpcRiemannTrackingTask - ideal PID now working - please rerun reconstruction
type: item
description: Hi Sverre, this is the same crash Johannes experienced some days ago (see here: http://forum.gsi.de/index.php?t=tree&th=3300&start=0&rid=993 &S=714ce46ffd2aeca38d39ebfd37e21456). It would be helpful to understand what happens it you could post the helix parameters using the FairTrackParH::Print() function, i.e. if you could put the line: helix->Print(); in PndPidTrackInfo.cxx, before the Propagate function that crashes and run the pid again. Cheers, Lia.
creator: Lia Lavezzi
date: 2011-08-02T12:18:26-00:00

Re: TpcRiemannTrackingTask - ideal PID now working - please rerun reconstruction
type: item
description: Hi, I have rerun tpc reconstruction for eta_c with ideal pid in TpcRiemannTrackingTask and results are very close to what I showed yesterday with pion hypothesis ( http://panda-wiki.gsi.de/pub/Tracking/TdrPreliminary/eta_c01.08.2011.pdf). In both cases 5000 events were analysed with the same simulated data. So eta_c reconstruction efficiency is 28.0% (ideal pid) vs 27.9% (pion), sigma(eta_c)=12.5 MeV (ideal pid) vs 12.3 MeV (pion), sigma(phi)=3.4 MeV (ideal pid) vs sigma(phi)=3.5 MeV (pion). Dima
creator: Dima Melnychuk
date: 2011-08-02T12:50:24-00:00

Re: TpcRiemannTrackingTask - ideal PID now working - please rerun reconstruction
type: item
description: Hi Lia I implemented the printout in the PndPidTrackInfo.cxx: helix->Print(); Bool_t rc = fPro0->Propagate(helix, fRes, fPidHyp*charge); Here is the print out from the last track before the crash. The elements in the Covariance matrix seems very small. 0x2a09cd08 Position : (-1.9e+03, 6.5e+02, 1.5e+02) Angles : Lambda = 0.018, Phi = -0.34 q/p = 1.2 fCovMatrix[0] = 0x2a09cd08 -1.2e+58 fCovMatrix[1] = 0x2a09cd08 6.3e+55 fCovMatrix[2] = 0x2a09cd08 1.7e+57 fCovMatrix[3] = 0x2a09cd08 -1.7e+60 fCovMatrix[4] = 0x2a09cd08 -6.1e+57 fCovMatrix[5] = 0x2a09cd08 -1.9e+53 fCovMatrix[6] = 0x2a09cd08 -3.3e+54 fCovMatrix[7] = 0x2a09cd08 5.9e+57 fCovMatrix[8] = 0x2a09cd08 2.7e+55 fCovMatrix[9] = 0x2a09cd08 -1.6e+56 fCovMatrix[10] = 0x2a09cd08 1.4e+59 fCovMatrix[11] = 0x2a09cd08 -2.1e+57 fCovMatrix[12] = 0x2a09cd08 -1.3e+62 fCovMatrix[13] = 0x2a09cd08 -2.1e+59 fCovMatrix[14] = 0x2a09cd08 -6.5e+57 *** Break *** floating point exception =========================================================== There was a crash (#7 0xb724ce3d in SigHandler(ESignals) ()). This is the entire stack trace of all threads: =========================================================== #0 0xb777b424 in __kernel_vsyscall () #1 0xb660e003 in __waitpid_nocancel () at ../sysdeps/unix/syscall-template.S:82 #2 0xb65afe63 in do_system (line=<value optimized out>) at ../sysdeps/posix/system.c:149 #3 0xb66cb3bd in system ( line=0x28dc7f28 " /nfs/hicran/project/panda/SIM/FAIRRoot/fairsoft_release_may11/tools/root _5.28d_qt_custom_TH2Poly/etc/gdb-backtrace.sh 31010 1>&2") at pt-system.c:29 #4 0xb724733d in TUnixSystem::Exec(char const*) () from /nfs/hicran/project/panda/SIM/FAIRRoot/fairsoft_release_may11/tools/root _5.28d_qt_custom_TH2Poly/lib/libCore.so #5 0xb724d91a in TUnixSystem::StackTrace() () from /nfs/hicran/project/panda/SIM/FAIRRoot/fairsoft_release_may11/tools/root _5.28d_qt_custom_TH2Poly/lib/libCore.so #6 0xb724cd2f in TUnixSystem::DispatchSignals(ESignals) () from /nfs/hicran/project/panda/SIM/FAIRRoot/fair…
creator: Sverre Dørheim
date: 2011-08-02T13:25:44-00:00

Re: TpcRiemannTrackingTask - ideal PID now working - please rerun reconstruction
type: item
description: If I read the position values at the beginning, they seem meters far from the interaction point. I suppose those parameters are completely screwed for some reason, well before the backward extrapolation.
creator: StefanoSpataro
date: 2011-08-02T13:29:38-00:00

Re: TpcRiemannTrackingTask - ideal PID now working - please rerun reconstruction
type: item
description: I agree with Stefano. Also the covariance matrix elements are too big (10 to +54/55/60!). GEANE fails because the input is wrong. Lia.
creator: Lia Lavezzi
date: 2011-08-02T14:37:24-00:00

Re: TpcRiemannTrackingTask - ideal PID now working - please rerun reconstruction
type: item
description: Hello Lia. I agree as well, and I am looking into the source for these weird start values. Even though, the code should not segment, the back propagation should fail ... Best Regards Sverre
creator: Sverre Dørheim
date: 2011-08-02T14:56:35-00:00

Re: TpcRiemannTrackingTask - ideal PID now working - please rerun reconstruction
type: item
description: In principle I agree, but it would require to touch again the GEANE fortran code and patch the external packages, it is better to fix this crash in the C++ code before entering GEANE (at least for now). Lia.
creator: Lia Lavezzi
date: 2011-08-02T15:43:01-00:00

Re: TpcRiemannTrackingTask - ideal PID now working - please rerun reconstruction
type: item
description: Hello Stefano, Lia To study the problem a bit closer I took a look at the output of the fits in the TPC+MVD+GEM before the conversion to PndTracks. In this plot one can see the start-position of all tracks in the XY-plane, and one can clearly see some starting points which are way off. This is of course ALL tracks, also the tracks where the fits went wrong. Looking at only the tracks with track.getCardinalRep().getStatusFlag()==0, where the fit converged I get something like this, where all start values are within a reasonable range. The rough binning is to make the outlyers a bit more visible. This led me to investigate if this flag is checked at any time later in the analysis chain and as far as I can see this information is lost when converting the GFTrack to a PndTrack, where the PndTrack gets a new flag which is: -1 if NDF=0 or Genfit threw an exeption when calculated the momentum at the first and last detector plane 1 otherwhise I did the same plot for all GFTracks where NDF!=0 resulting in: Where clearly can see that the worst outliers are gone. Since only this flag is awailable atthe PndPidTrackInfo level I implemented this check before the extrapolation: Bool_t rc=false; if(track->GetFlag()==1){ rc = fPro0->Propagate(helix, fRes, fPidHyp*charge); } This was then tested on 1000 events, whith no crash in the PID-macr. This is probably the quickest fix as one only needs to rerun the PID-Macro. Best regards Sverre Ps: Looking at the statistics in the 3 plots: All GFTracks:5113 statusflag 0:4132 ndf!=0 :4912 A lot more tracks get lost when cutting away events with statusflag!=0(ie something whent wrong) than just cutting away events with ndf!=0. The effect of this should also be tested.
creator: Sverre Dørheim
date: 2011-08-02T18:49:03-00:00