Electron Veto

Electron Veto IPNL

Energy Regression Studies

Energy Regression IPNL

H→γ+γ HLT Studies

From HIG-13-001 the list of HLT paths is this one:

HLT_paths_2012.png

All of them seeded by one of these two L1:

L1efficiency.png

A better HLT paths description can be found in CMS-AN-2012/160 page 9,10.

The general trigger strategy is to keep all possible good photon pairs using the ”OR” triggers:

HLT_Photon26_R9Id85_OR_CaloId10_Iso50_Photon18_R9Id85_OR_CaloId10_Iso50_Mass* v* OR HLT_Photon36_R9Id85_OR_CaloId10_Iso50_Photon22_R9Id85_OR_CaloId10_Iso50_v*

Short explanation about the efficiency estimation (just for info, not our goal)

To measure the trigger efficiencies, one needs to evaluate separately the efficiency of the L1-seeding (L1 efficiency) and the efficiency of the HLT filters provided that the L1 requirement has been satisfied. In this analysis, we use the tag and probe method on Zee data for efficiency measurements. The data sample for efficiency studies is obtained as follows:

  • 1. From DoubleElectron PD, select events that have passed the loosely prescaled path HLT Ele32 CaloIdT CaloIsoT TrkIdT TrkIsoT SC17 Mass50. Since this path requires only one electron passing the tight HLT cuts, the other electron which is required to pass only the very loose SC17 filter, is suitable for our measurement.

  • 2. We require at least one offline electron to be matched to the HLT electron leg, and at least two offline photons to be matched to the HLT electron and the HLT super-cluster leg, respectively. The two offline photons are required to have an invariant mass compatible with the Z peak (between 70 GeV and 110 GeV), and to pass an offline p T cut of 30 GeV and 22.5 GeV, respectively.

  • 3. We require further that the event has passed preselection and has diphoton MVA > 0.05.

  • 4. The photon matched to the HLT electron leg is also required to be matched to an L1 e/γ isolated object with ET > 22 GeV (requirement compatible with the HLT Ele32 CaloIdT CaloIsoT TrkIdT TrkIsoT SC17 Mass50 path). Then, we can label this photon as TAG and the other one as PROBE, and perform various efficiency measurements.

To account for the fact that electrons and photons have different R9 distributions, each electron pair used for the trigger efficiency measurement has been weighted so that the R9 distribution of the associated superclusters matches the one of Higgs photons according to the signal MC. The net effect is an increasing of the measured efficiency due to the migration of events towards higher R9 values. For events that have passed preselection and diphoton MVA > 0.05, we found the HLT efficiency of the OR of the two triggers mentioned above to be 99.49±0.09%. For events hat have passed the standard CiC supertight selection, we found the HLT efficiency to be 99.73±0.09%.

The turn-ons in Etgamma1 X Etgamma2 and m_gammagamma phase spaces limit the acceptance for our low-mass case (we basically want to be sure we are on the 'plateaux') with the existing HLT paths used in the official analysis.

Plots style.

In order to include the binomial error in the text box for each cell, a simple macro stored in git has been created. Running on top of previous output. Below just an example.

turn_on_plot.png

EXO HLT trigger studies

In this twiki page you can find the list of triggers used and planned for EXO analysis.

HLT efficiency normalized to Generated particles.

The goal of this study is to produce the turn-on curve for the Trigger used on the H→γ+γ discovery. In order to understand the reach of this trigger for log mass higgs.

The datasets used for the study are:

/GluGluToHToGG_M-90_7TeV-powheg-pythia6/Summer11-START311_V2-v1/GEN-SIM and /GluGluToHToGG_M-130_7TeV-powheg-pythia6/Summer11-START311_V2-v1/GEN-SIM

According to the note and the HLT menu used in the production of this datasets the bits and the names of the trigger paths are:

bit_194_HLT_Photon26_R9Id85_OR_CaloId10_Iso50_Photon18_R9Id85_OR_CaloId10_Iso50_Mass60_v5 OR bit_195_HLT_Photon26_R9Id85_OR_CaloId10_Iso50_Photon18_R9Id85_OR_CaloId10_Iso50_Mass70_v1 OR bit_205_HLT_Photon36_R9Id85_OR_CaloId10_Iso50_Photon22_R9Id85_OR_CaloId10_Iso50_v5

90 Gev MC Sample

Turn-on curve by using a 90 GeV sample /GluGluToHToGG_M-90_7TeV-powheg-pythia6/Summer11-START311_V2-v1/GEN-SIM (100.000 events) if you want to check, GEN distribution and other interesting trigger paths turn-on curves check ALL DETAILED plots for this mass point.

90bitOR_efficiency.png

The statistics for the high pT region is still low

130 Gev MC Sample

Turn on curve 130 GeV sample /GluGluToHToGG_M-130_7TeV-powheg-pythia6/Summer11-START311_V2-v1/GEN-SIM (100.000 events) if you want to check, GEN distribution and other interesting trigger-paths-turn-on curves check ALL DETAILED plots for this mass point.

130bitOR_efficiency.png

All samples available in /GluGluToHToGG_M-*_7TeV-powheg-pythia6/Summer11-START311_V2-v1/GEN-SIM (all mass points) have been analyzed. Several improvements on the plots and stacking passing different filtes have been produced. All detailed plots can be checked here

-- CamiloCarrillo - 27 Nov 2013

Topic attachments
I Attachment History Action Size Date Who Comment
PNGpng 130bitOR_efficiency.png r1 manage 59.1 K 2013-12-11 - 14:41 CamiloCarrillo  
PNGpng 90bitOR_efficiency.png r1 manage 60.1 K 2013-12-11 - 14:40 CamiloCarrillo  
PNGpng HLT_paths_2012.png r1 manage 92.5 K 2013-11-27 - 11:25 CamiloCarrillo  
PNGpng L1efficiency.png r1 manage 24.4 K 2013-12-03 - 15:13 CamiloCarrillo  
PNGpng turn_on_plot.png r1 manage 66.3 K 2013-12-03 - 15:17 CamiloCarrillo  
Edit | Attach | Watch | Print version | History: r10 < r9 < r8 < r7 < r6 | Backlinks | Raw View | WYSIWYG | More topic actions
Topic revision: r10 - 2014-05-07 - CamiloCarrillo
 
    • Cern Search Icon Cern Search
    • TWiki Search Icon TWiki Search
    • Google Search Icon Google Search

    Main All webs login

This site is powered by the TWiki collaboration platform Powered by PerlCopyright &© 2008-2019 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback