GSI Forum - RDF feed
type: channel
description: GSI Helmholtzzentrum für Schwerionenforschung
items: Ideal Tracking Tasks
items: Re: Ideal Tracking Tasks

Ideal Tracking Tasks
type: item
description: Dear trackers. There are now two ideal tracking tasks. The concept is to match hits from STT or FTS to MC tracks and adding MVD+GEM hits afterwards. The packages & classes are: sttmvdtracking/PndSttMvdGemTrackingIdeal fts/PndFtsTrackerIdeal Set your track output branch with: SetTrackOutput("...") Smearing can be introduced by: SetMomentumSmearing(spx,spy,spz) SetRelativeMomentumSmearing(dp/p) SetVertexSmearing(svx,svy,svz) SetTrackingEfficiency(epsilon) One can deactivate the additional detectors by: SetMvdActivity(kFALSE) SetGemActivity(kFALSE) Cheers. Ralf
creator: Ralf Kliemt
date: 2013-03-20T12:21:20-00:00

Re: Ideal Tracking Tasks
type: item
description: Hi Ralf, I have added a ideal reconstruction macro under pandaroot/macro/run/recoideal_complete.C I put there: PndSttMvdGemTrackingIdeal* trackStt = new PndSttMvdGemTrackingIdeal(); trackStt->SetRelativeMomentumSmearing(0.05); trackStt->SetVertexSmearing(0.05, 0.05, 0.05); trackStt->SetTrackingEfficiency(1.); trackStt->SetTrackOutput("SttMvdGemIdealTrack"); fRun->AddTask(trackStt); What I find strange is that if I run muons (13) at 1 GeV, with a momentum smearing of 5%, once I plot: cbmsim.Draw("-1./SttMvdGemIdealTrack.fTrackParamLast.fQp>>aa(200,-1.5,0.5)","SttMvdGemIdealTrack.fRefIndex==0") I obtain a width of 37 MeV instead of 50. Vertices seem fine. Could you please check also in your case? The second thing I found is that half of the track are failing with the kalman, which sounds a bit strange. But this I could check more deeply later.
creator: StefanoSpataro
date: 2013-03-21T17:50:35-00:00

Re: Ideal Tracking Tasks
type: item
description: Hi Stefano. I found that to be a bug indeed. Fixed in SVN. Ralf
creator: Ralf Kliemt
date: 2013-03-25T10:13:47-00:00

Re: Ideal Tracking Tasks
type: item
description: Hi Ralf, thanks for the fix, I have tried and now the resution seems correct. Still I have problems in the kalman, half of the tracks fail the fit. Is it possible that the candidate is not sorted in the proper way? If you run the recoideal_complete.C, after the fit in substance I do not see any momentum improvement.
creator: StefanoSpataro
date: 2013-03-26T08:29:55-00:00

Re: Ideal Tracking Tasks
type: item
description: Hm. Doesn't sorting occur in the interface of GenFit? Ralf
creator: Ralf Kliemt
date: 2013-03-26T09:24:51-00:00

Re: Ideal Tracking Tasks
type: item
description: Hi. I modified the sorting parameter to be rho=(x*x+y*y) Should be better now. Ralf
creator: Ralf Kliemt
date: 2013-03-26T10:12:45-00:00

Re: Ideal Tracking Tasks
type: item
description: Hi Ralf, now it breaks: ===PndRecoKalmanFit::Init() finished =================================================== -I- PndMCTrackAssociator::Init [INFO ] Branch: STTHitMix not found in Tree [INFO ] Branch: STTHitMix not found in Tree -W- PndMCTrackAssociator::Init: Using STTHit array [INFO ] Branch: MVDHitsStripMix not found in Tree [INFO ] Branch: MVDHitsStripMix not found in Tree -W- PndMCTrackAssociator::Init: Using MVDHitsStrip array [INFO ] Branch: MVDHitsPixelMix not found in Tree [INFO ] Branch: MVDHitsPixelMix not found in Tree -W- PndMCTrackAssociator::Init: Using MVDHitsPixel [INFO ] The number of entries in chain is 1000 *** Break *** segmentation violation =========================================================== There was a crash. This is the entire stack trace of all threads: =========================================================== #0 0x00007fb69d05b43e in __libc_waitpid (pid=<optimized out>, stat_loc=0x7fffb1524580, options=0) at ../sysdeps/unix/sysv/linux/waitpid.c:32 #1 0x00007fb69cfe129e in do_system (line=0x10d73550 "/home/spataro/sep12/fairbuild/etc/gdb-backtrace.sh 28302 1>&2") at ../sysdeps/posix/system.c:149 #2 0x00007fb69df18787 in TUnixSystem::StackTrace() () from /home/spataro/sep12/fairbuild/lib/root/libCore.so.5.34 #3 0x00007fb69df1b063 in TUnixSystem::DispatchSignals(ESignals) () from /home/spataro/sep12/fairbuild/lib/root/libCore.so.5.34 #4 <signal handler called> #5 0x00007fb691d20c82 in FairHit::GetX (this=0x0) at /home/spataro/sep12/pandaroot/base/FairHit.h:37 #6 0x00007fb68d01fb91 in PndSttMvdGemTrackingIdeal::Exec (this=0x24ecda0, option=0x7fb691d33360 "") at /home/spataro/sep12/pandaroot/sttmvdtracking/PndSttMvdGemTrackingIdeal.cxx:190 #7 0x00007fb69deaed23 in TTask::ExecuteTasks(char const*) () from /home/spataro/sep12/fairbuild/lib/root/libCore.so.5.34 #8 0x00007fb69deaf356 in TTask::ExecuteTask(char const*) () from /home/spataro/sep12/fairbuild/lib/root/libCore.so.5.34 #9 0x00007fb691c5ad34 in FairRunAna::Run (this=0x1989cf0…
creator: StefanoSpataro
date: 2013-03-26T16:38:34-00:00

Re: Ideal Tracking Tasks
type: item
description: Strange. I fixed it. However I see often messages that something in GEANE aborts or GenFit cannot converge. Might be just due to one of the tracks going into a "bad" region... Ralf
creator: Ralf Kliemt
date: 2013-03-27T08:49:29-00:00

Re: Ideal Tracking Tasks
type: item
description: Much better now, thanks, now most (98%) of the primary tracks tracks are fitted, and I obtain some reasonable momentum resolution. Many thanks.
creator: StefanoSpataro
date: 2013-03-27T09:33:30-00:00