BMU Triggers for Higgs

1. BMU Triggers for Higgs Jason Nett Wisconsin Group Meeting May 5th, 2008 • Muon Categorization for Triggering BEACH 04 J. Piedra 1

2. Methodology • Denominator • WH -> Wbb -> bb events • Generated muon from W • pT > 18 GeV • Numerator • Isolated, high pT muons: calE/pT < 0.2, pT > 20GeV • Divide into stubbed muons or isolated tracks (CMIO minimum ionizing track) • Selection from WH analysis • Categorization vs eta • Categorize all numerator muons • Match to HEPG • form chi of pT, Eta, phi; chi < 40 - used pT dependent pT resolution • ~98% efficient • Stubbed muons: CMUP, CMX, CMU, CMP, BMU or Isolated tracks • Failures: No match, pt too low, fails isolation Wis Group Meeting 2

3. Muon Categorization • No reconstructed muon found N • Small number fail analysis like selection or matching • Note: isolated tracks may pass MET+JETS trigger • Denominator Eta • Candidates for BMUJET and BMUJETMET • Nearly all muons understood Wis Group Meeting 3

4. Muon Categorization • Most fail analysis selection: pt and iso N • Very few isolated high pt muons fail to match to generated W muons • Nearly all muons understood Wis Group Meeting 4

5. Conclusion • Nearly all reconstructed muons in WH events understood • Next steps • Separate Isolated track and BMU categories into triggerable and non-triggerable. • Isolated tracks: MET+JETs triggers • BMU: BMUJET and BMUJETMET triggers • Would rather have BMU trigger than MET+JETs trigger because MET+JETs is not on at all luminosities and has tight cuts at level 3. • Trigger confirmation might be tricky for BMU since the trigger is on stub only, not reconstructed muons. • Note using reconstructed muons to emulate CMUP, CMX, CMU and CMP triggers is reasonable since the trigger efficiency is very high. • Some overlap in stacked histograms needs to be resolved. For instance CMX and BMU may overlap and be counted twice. • Investigate inefficiency at higher eta. May be the CMIO requirements • Revisit trigger rates Wis Group Meeting 5