Home » PANDA » PandaRoot » Tracking » Update on eta_c reconstruction with STT and TPC
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Re: Update on eta_c reconstruction with STT and TPC [message #12147 is a reply to message #12146] |
Mon, 27 June 2011 15:16   |
StefanoSpataro
Messages: 2736
Registered: June 2005
Location: Torino
|
first-grade participant |
From: *to.infn.it
|
|
This is the output of the tpcriemanntask if i set the DEBUG to 1:
pdg: 211 charge: 3.000
MC pid pdg: -11 charge: 3.000
charge corrected MC pid pdg: -11
center of track TVector3 A 3D physics vector (x,y,z)=(12.483792,3.663404,0.000000) (rho,theta,phi)=(13.010211,90.000000,16.354474)
Radius of track [cm]: 3.778
Dip of track [deg]: 46.17
seed values:
start position: TVector3 A 3D physics vector (x,y,z)=(14.202656,7.027931,25.054993) (rho,theta,phi)=(29.645572,32.311851,26.327688)
momentum [GeV]: 0.03149
p_perp [GeV]: 0.02272
direction: TVector3 A 3D physics vector (x,y,z)=(0.642457,-0.328217,-0.692476) (rho,theta,phi)=(1.000000,133.826418,-27.061496)
winding: 1
invertedTrack: 0
pdg id: -11
Tracklet 3 nhits = 48
pdg: 211 charge: 3.000
MC pid pdg: 22 charge: 0.000
charge corrected MC pid pdg: -22
center of track TVector3 A 3D physics vector (x,y,z)=(1.549914,37.385460,-0.000000) (rho,theta,phi)=(37.417574,90.000000,87.626011)
Radius of track [cm]: 37.18
Dip of track [deg]: 24.07
seed values:
start position: TVector3 A 3D physics vector (x,y,z)=(-15.273078,4.230596,35.533201) (rho,theta,phi)=(38.907239,24.037374,164.517430)
momentum [GeV]: 0.5482
p_perp [GeV]: 0.2236
direction: TVector3 A 3D physics vector (x,y,z)=(-0.363711,0.184549,0.913047) (rho,theta,phi)=(1.000000,24.070050,153.096469)
winding: 1
invertedTrack: 1
pdg id: -22
RKTrackRep::setPDG particle -22 not known to TDatabasePDG -> abort
maybe it could help somehow.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| Re: Update on eta_c reconstruction with STT and TPC [message #12389 is a reply to message #12384] |
Fri, 29 July 2011 14:33 |
Gianluigi Boca
Messages: 177
Registered: March 2004
|
first-grade participant |
From: *gsi.de
|
|
Hi Dima,
I was still working on the Cleanup code for Stt in the last days.
Maybe you run with some non-final version and that's the cause of this sudden 15.6% efficiency.
So last night I put the final version (...yes, right  ) of the Stt PR+Cleanup code in svn. I hope the efficiency for Stt returns to the previous values.
Also I updated all the analysis Macros (run_reco_stt_evt.C and
run_reco_stt_mix.C) for all the physics channels (eta_c,
llbar, npipi, psi3770) by adding the following line necessary
to activate the Cleanup code :
SttMvdTracking->Cleanup();
Please notice that in the non-mixing Macros (run_reco_stt_evt.C)
this line is COMMENTED OUT for the time being, because I would like to see if possible, if there are problems with the various analysis and no Cleanup.
If everything is fine, then activating the Cleanup should be beneficial even for the non-mixed events (it rejectes spurious tracks) even though I would expect a bit of a lowering in the reconstruction efficiency.
Lia has also updated the run_reco_stt_evt.C and run_reco_stt_mix.C adding the task of the extrapolation to the Gem region.
She is also checking the last details today. By tonight let's say at 20:00 all the Macro should be ready and can be used on the Grid. She will send aroung a message on the Forum when dona.
Tschuess an alle
Gianluigi
| Dima Melnychuk wrote on Fri, 29 July 2011 00:36 |
Hi Stefano,
I also would like to clarify the question of data production on GRID.
But comming to TPC vs STT efficieny.
TPC efficiency = 28.9% (using vertex fit)
STT efficiency with GRID data =26.4% with all tracks and 23.7% with requirement of at least one STT hit in track.
STT efficiency with latest trunk version (2000 events) = 15.6%
(with requirement of at least one STT hit).
But I have no idea if the work on STT code is finished?
So I suppose that STT signal data should also be reproduced but the question is if to reproduce them together with TPC or later?
For TPC data reproduction in addition to tpc directory, genfit and RKTrackRep in GenfitTools/trackrep should be updated to rev 370 and updated tpc reco macros should be used.
And coming to the question of reconstruction of fully mixed events. I do not know how realistic is to expect to produce them by 5-7 August (the date when the GRID will be off), but without knowing when the code will be ready, there is still the question if the available DPM data should be used or they also needs to be reproduced. At least for TPC there were recent modifications related to clustering, which is the part of digitization, and I suppose TPC expert should define how important they are for DPM data which will be used for mixing.
Dima
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Goto Forum:
Current Time: Thu Nov 28 01:49:12 CET 2024
Total time taken to generate the page: 0.01120 seconds
|
GSI Forum
Search
Help
Members
Login
Home
