first try to add ZMuMu lines for run-3
We add two lines for Z-> mumu study at Run-3, as Z-> mumu signal line and same-sign line. In these lines, simple event selections are used, as:
-
muon pt > 3 GeV
-
mass window cuts: M(mumu) > 40 GeV for Z->mumu signal line, and M(mumu) > 16 GeV for same-sign line
The trigger rate is test with the standard Run-3 rate setting, using 50k minimum bias events.
Line: Hlt2LowPtSingleJetLineDecision Incl: 0.734165387439 +/- 0.22 kHz, Excl: 0.734165387439 +/- 0.22 kHz
Line: Hlt2MuMuSSLineDecision Incl: 0.0 +/- 0.0 kHz, Excl: 0.0 +/- 0.0 kHz
Line: Hlt2SingleHighPtMuonLineDecision Incl: 0.867650003337 +/- 0.24 kHz, Excl: 0.867650003337 +/- 0.24 kHz
Line: Hlt2ZToMuMuLineDecision Incl: 0.0 +/- 0.0 kHz, Excl: 0.0 +/- 0.0 kHz
To make sure 0 Hz is expected, we also made another test with loosed selection cuts, as
-
muon pt > 0
-
mass window cuts: M(mumu) > 40 MeV, and 16 MeV for signal and SS lines
trigger rates (10k evts) for this setting are shown below:
Line: Hlt2LowPtSingleJetLineDecision Incl: 0.8 +/- 0.28 kHz, Excl: 0.4 +/- 0.19 kHz
Line: Hlt2MuMuSSLineDecision Incl: 741.8 +/- 4.37 kHz, Excl: 157.6 +/- 3.64 kHz
Line: Hlt2SingleHighPtMuonLineDecision Incl: 1.0 +/- 0.31 kHz, Excl: 0.0 +/- 0.0 kHz
Line: Hlt2ZToMuMuLineDecision Incl: 637.9 +/- 4.80 kHz, Excl: 53.7 +/- 2.25 kHz
We were planning to make efficiency plots for Z-> mumu, but when we check Run-3 MC samples, and found there is no request for Z-> mumu from QEE group. So may be we should start to request Z-> mumu sample now.