The pixel match study is split into several stages:

  • Run the trigger path including the PixelMatchFilterAnalysis module before the PixelMatchFilter module. The output file is called "outfile.root"
  • hadd the files together.
  • Run the pixel match study.
  • Run the code to create the analysis note.

Code repositories

The code is avaiable in the cms-iihe git repository (https://github.com/CMSHLTEGammaPixelMatch)

https://github.com/CMSHLTEGammaPixelMatch/HLTEgamma for the PixelMatchFilterAnalysis module (runs under CMSSW_6_2_0)

https://github.com/CMSHLTEGammaPixelMatch/PixelMatchOfflineAnalysis for the code to run the study. This expects signal and background samples for 8 and 13 TeV. It also expects data at 8 TeV and ttbar MC at 13 TeV.

https://github.com/CMSHLTEGammaPixelMatch/PixelMatchLatex for the LaTeX source.

Running the code

The HLTEgamma packages contains the pset for data and MC for the HLT_Ele27_WP80 and HLT_Ele17_Ele8 triggers. This should run out of the box.

The offline analysis code should run out of the box as well, provided the ntuples are located in the "output" directory. Simply run python pixel.py.

The LaTeX code should also run out of the box, and many snippets will be automatically generated by the offline analysis code.

Analysis note

The output of the LaTeX code is the analysis note, AN-2014/092.

-- AidanRandleConde - 29 Jul 2014

Edit | Attach | Watch | Print version | History: r1 | Backlinks | Raw View | WYSIWYG | More topic actions
Topic revision: r1 - 2014-07-29 - AidanRandleConde
    • Cern Search Icon Cern Search
    • TWiki Search Icon TWiki Search
    • Google Search Icon Google Search

    Sandbox All webs login

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