1 / 12

SUSY DILEPTON TRIGGER MONITORING

SUSY DILEPTON TRIGGER MONITORING. M.Rossi (Udine University). MONITORING VARIABLES. R  events collected by the trigger path having one of the corresponding reconstructed lepton (per trigger path: R11st lepton, R22nd lepton)

tamra
Download Presentation

SUSY DILEPTON TRIGGER MONITORING

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. SUSY DILEPTON TRIGGER MONITORING M.Rossi (Udine University) Multilepton Meeting

  2. MONITORING VARIABLES R events collected by the trigger path having one of the corresponding reconstructed lepton (per trigger path: R11st lepton, R22nd lepton) Q events, that have two reconstructed leptons, not collected by the corresponding trigger path Rate fraction of events collected by trigger path over the luminosity of the run Multilepton Meeting

  3. RUNS SELECTED FOLLOWING DQM CRITERIA • ONLINE bits required to be good: CLC,L1T,L2T,L3T,CAL,COT,CMU,CMP,CMX,SMX • OFFLINE bits required to be good: COT,CAL,CMU,CMP,CMX • From 2002 to most recently available data excluding runs with COT problems 1459 RUNS, 284 pb-1 Multilepton Meeting

  4. RUN QUALITY EVALUATIONfirst attempt at evaluation based on deviation from the local average of monitoring variables Local Average for i-th run: where X = R,Q,Rate If i-th run is marked as suspect Multilepton Meeting

  5. R CEM4_CEM4 ALL RUNS run 144714-144883 CUT on CES in L2 run 163113-163130 Tighter electron L3 triggers w/o SUSPECT RUNS SUSPECT RUNS 160761 163130 178852 Multilepton Meeting

  6. MONITORING VARIABLES FOR CEM4_CEM4 ALL RUNS w/o SUSPECT RUNS Multilepton Meeting

  7. MONITORING VARIABLES FOR CEM4_CEM4_L2_CEM12_PT8 ALL RUNS w/o SUSPECT RUNS Multilepton Meeting

  8. MONITORING VARIABLES FOR CEM4_CEM4_L2_CEM12_PT8 ALL RUNS w/o SUSPECT RUNS Multilepton Meeting

  9. Summary of Monitoring Run processing up-to-date R, Q distributions indicate a locally stable trigger behaviour Rate fluctuations under investigation First attempt at run quality evaluation based on trigger monitoring Multilepton Meeting

  10. Other activities and future plans • Monitoring finalized by mid- August • Then concentrate on efficiency calculations using backup triggers • Exclusive backutp trigger rates by end of August • Trigger efficiencies by end September Multilepton Meeting

  11. BACKUPDOWNSTREAMAPPROACH • For each TRIGGER PATH (T.P.) count: N : # evts selected by the T.P. N1: # evts with offline lepton 1 N2: # evts with offline lepton 2 • In ideal conditions R=1 (R~purity) • For each lepton “type”, expect R values from different T.P. comparable and stable in time R1≡ N1/N and R2 ≡ N2/N Multilepton Meeting

  12. BACKUPUPSTREAM APPROACH • N12 ≡ events with lepton 1 && lepton 2 offline level • N0 ≡ events failing the i-th T.P. Qi ≡ N0/NAB • In ideal conditions Qi = 0 Multilepton Meeting

More Related