1 / 7

UK CLEO Meeting – Wednesday 29 th August 2007

Status With First Unified Selection. UK CLEO Meeting – Wednesday 29 th August 2007. The CLEO-c Selection. A unified selection algorithm (for both data and MC) has now been written for the following modes: K3 p vs K3 p (Opp. & Same Sign) K3 p vs KK K3 p vs pp K3 p vs K s p 0

galena
Download Presentation

UK CLEO Meeting – Wednesday 29 th August 2007

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Status With First Unified Selection UK CLEO Meeting – Wednesday 29th August 2007

  2. The CLEO-c Selection • A unified selection algorithm (for both data and MC) has now been written for the following modes: • K3p vs K3p (Opp. & Same Sign) • K3p vs KK • K3p vs pp • K3p vs Ksp0 • K3p vs Kp (Opp. & Same Sign) • In addition, a Ks ‘Search’ Algorithm has also been written for all modes. • Both of these algorithms have now been run over ALL the 281pb-1AND the corresponding 10xlumi MC. • Now writing some unified ROOT code to analyse the results.

  3. A single job generates two Ntuples: • AllTags_K3piSel • AllTags_KsVeto • The contents of each looks like that opposite

  4. e.g. Within the K3piRS ROOT tree, one finds the following leaves:

  5. ROOT Analysis Code This involves, essentially, a separate class for each mode. The class initialises buffers for all the Ntuple leaves for that mode and performs the selection, generating relevant histo’s. The code works in one of three ways: 1) All Selected Candidates 3) 1) 2) 2) Sel. Cuts Sel. Cuts (132 MC Ks) Ks0 Veto Best Cand. Best Cand. Best Cand.

  6. Help! – Ks Veto The Ks veto has only eliminated 5 bkg events! Why is this? I think I’m implementing this feature wrongly. 3) To confirm: If I identify a viable Ks candidate within, say, a K3pi vs K3pi candidate, should I veto on all other K3pi vs K3pi candidates in that event, regardless of whether they have a possible Ks candidate associated with them as well? Currently, I only eliminate the original candidate and not the entire event.

  7. The ‘To Do’ List • Use DE candidate selection criteria • Improve Ks selection (Mass Cut and Flight Sig.) • Improve MC selection algorithm to identify K3p vs K3p events where tracks have been ‘swapped’ between opposite sides • Investigate implementing a Ks veto in our K3p tag since a dominant peaking background in this mode is K*(Ksp)K • Incorporate Kp as an additional tag • Incorporate additional CP tags (KS/KL{h, h’, w, p0p0}) • Perform the ‘Union Jack’ analysis a la Jim on my MC • Ensure the same selection code has been used for both MC and data analysis • Repeat everything for Kpp0 P P

More Related