30 likes | 132 Views
Effect of tracking parameters on Ks reco eff. to see whether we gain significantly by adjusting pT and Impact Parameter cuts in gtr_find. Sample: J/ Ks MC sample with 1.1 min. bias There are many Ks in the MC coming from hard interaction, min. biased events …
E N D
Effect of tracking parameters on Ks reco eff.to see whether we gain significantly by adjusting pT and Impact Parameter cuts in gtr_find • Sample: J/ Ks MC sample with 1.1 min. bias • There are many Ks in the MC coming from hard interaction, min. biased events … • I consider Ks (MC/reco) those within || 2, R 20 cm ….. • My Ks reco : • in principle just looping over GTrack pairs which come from the same vertex, using vkalman_xxx packages • applying my impact parameter (IP) significance cut IP/ >2 • p11.02.00 for results being shown here
GTrack: • Changing pTmin and max IP (DCA) is still not convenient at all • Pushed GTR experts to implement global cuts in the RCP instead of individual obs files • Though they put out the global cuts in RCP, it was not implemented when I tried to use them. • Slava made a new version very recently so that SMT would use the pTmin global cuts • It was said this week that in the newest ~2 test releases have implemented those cuts for CFT --- which I haven’t been able to try yet • At the end, I used Slava’s + changing CFT obs by hand • Absolute efficiencies depend on reco versions and various cuts. But in general, Ks reco efficiency is low. I show the relative efficiencies.
I have NOT changed 2 cuts here There are many IP/DCA cuts in various stages of different values (many are big ~ 10 cm) …