October 5, 2004SUSY Meeting -- M.Rossi1 the Udine approach to SUSY Multileptons Udine University...
-
Upload
cody-austin -
Category
Documents
-
view
213 -
download
0
Transcript of October 5, 2004SUSY Meeting -- M.Rossi1 the Udine approach to SUSY Multileptons Udine University...
October 5, 2004 SUSY Meeting -- M.Rossi 1
the Udine approach to
SUSY Multileptons
Udine UniversityM.P.Giordani, G.Pauletta, M.Rossi
October 5, 2004 SUSY Meeting -- M.Rossi 2
Analysis Approach follow same approach of RunI analysis
dilepton trigger 1 tight + 2 loose offline leptons
in this talk: RunII SUSY dilepton trigger Trigger strategy (CDF6074) Towards a good run list: method Cross section studies Conclusions/Plans
October 5, 2004 SUSY Meeting -- M.Rossi 3
Trigger Strategy (1) achieve maximum acceptance/efficiency
SUSY yields leptons through cascade decays leptons typically produced with low pT
multipath dilepton trigger two low pT leptons (baseline) lepton + track (recover stub/cluster inefficiency) Single high pT lepton (best high pT multilepton
efficiency) all paths contribute to acceptance
October 5, 2004 SUSY Meeting -- M.Rossi 4
Trigger Strategy (2) define standard lepton objects
lepton object definitions @ trigger level do not depend on specific trigger path
simplification of trigger calibration compute efficiency for each lepton object combine lepton objects into trigger paths L1 & L2 efficiency can be computed by
comparing single lepton with dilepton paths detector conditions naturally folded in
October 5, 2004 SUSY Meeting -- M.Rossi 5
Data selection
ONLINE bits required to be good: CLC,L1T,L2T,L3T,CAL,COT OFFLINE bits required to be good: COT,CAL From 2002 to 02.13.2004 (no runs with COT problems) Using pre filter data
1324 RUNS, 257 pb-11324 RUNS, 257 pb-1
DQM CRITERIA DQM CRITERIA
October 5, 2004 SUSY Meeting -- M.Rossi 6
Towards a good run list: method
Instead of ~20 trigger paths 6 lepton objects: CEM4, CEM8, PEM8, CMU4, CMUP4, CMX4
Define STANDARD LEPTON OBJECT example: CEM4 = L1_CEM4_PT4 & L2_CEM4_PT4_CES2
Identify suitable monitoring variable Look for suspect runs
GOOD RUN LIST PER LEPTON OBJECT GOOD RUN LIST PER LEPTON OBJECT
October 5, 2004 SUSY Meeting -- M.Rossi 7
TRIGGER PATH = lepton 1 & lepton 2 For each TRIGGER PATH count: D1 : # triggered evts
N1 : " with offline lepton 1
D2 : # triggered evts
N2 : " with offline lepton 2
Towards a good run list: R variable
satisfying STANDARD lepton 1 DEFINITION satisfying STANDARD lepton 1 DEFINITION
satisfying STANDARD lepton 2 DEFINITIONsatisfying STANDARD lepton 2 DEFINITION
R1=N1/D1
R2=N2/D2
sort of purity expect no significant differences between different trigger paths for each lepton type expect stable in time
October 5, 2004 SUSY Meeting -- M.Rossi 8
Towards a good run list: R variable
CEM4
October 5, 2004 SUSY Meeting -- M.Rossi 9
Test for R indipendence of trigger path for each lepton type 1. For each run compute R average of all paths for each lepton type Rlepton
2. R = value for the single trigger path if |R-Rlepton| > 5σ , then the run is suspect
Test for R stability in time 1. Compute local average of Rlepton over 20 runs
before and after <Rlepton>
2. If |Rlepton - <Rlepton>| > 5σ , then the run is suspect
Towards a good run list: suspect run
October 5, 2004 SUSY Meeting -- M.Rossi 10
First estimate of suspect run luminosity for CEM4 lepton object is 0 pb-1
Towards a good run list: suspect run
RCEM4
October 5, 2004 SUSY Meeting -- M.Rossi 11
Trigger cross sections
complementary trigger path studies: L2 exclusive cross sections
L2 instantaneous luminosity dependence
PHYSICS_2_01_v4 (Feb. 2004)L2_CEM8_PT8_CES2_&_TRK8L2_TRK8_L1_CMUP6_PT4L2_CEM12_PT8
PHYSICS_2_05_v10 (June 2004)L2_CEM8_PT8_CES3_&_TRK8L2_CMUP6_PT8L2_CEM8_PT8_CES3_DPS
October 5, 2004 SUSY Meeting -- M.Rossi 12
Exclusive TotalExclusive Total
L2_CEM8_PT8_CES2_&_TRK8 4% 100 nb L2_TRK8_L1_CMUP6_PT4 32% 180 nb L2_CEM12_PT8 20% 250 nb
Using L3 Monitor dataset (MONITOR_L3TAG_PS200)calculated L2 complementary trigger path cross sectionsUsing L3 Monitor dataset (MONITOR_L3TAG_PS200)calculated L2 complementary trigger path cross sections
Trigger cross sections
October 5, 2004 SUSY Meeting -- M.Rossi 13
Events
Lint (nb-1)
σ (nb)σ (nb)
Events
Lint (nb-1)
L2_CEM12_PT8 L2_CEM8_PT8_DPS
Trigger cross sections
October 5, 2004 SUSY Meeting -- M.Rossi 14
Conclusions Monitoring strategy almost defined
Variables (R) behaves as expected
Stable in time Steps correlated to trigger table changes Good run list on the way Very low rejection based on R Comparison with evaluation based on rate underway Trigger cross section studies in progress High degree of overlap our complementary and other triggers Implications depend on future choices of TDWG
October 5, 2004 SUSY Meeting -- M.Rossi 15
Next
Per lepton object: Finalize good run list Calculate efficiency