-- JavierBrochero - 2015-09-23

Inclusive ttbar Cross Section in the Single Lepton Channel (Korean Group)

This twiki contains all the information about this analysis.

  1. Tae Jeong Kim (Profesor)
  2. Javier Brochero (Post-Doc)
  3. Dooyeon Gyun (Phd student)
  4. Ari Lee (Master student)
On this page:
  1. Workflow
  2. Code
  3. Tasks
  4. Additional material

1. Workflow

  1. Flat-ntuple production: It is done using CATTools. the codes are located at:
    1. CATTools/CatAnalyzer/plugins/TtbarSingleLeptonAnalyzer.cc: It contains the basic selection of the objects as electrons, muons, jets, b-tagged jets, etc.
    2. CATTools/CatAnalyzer/prod/ttbarSingleLeptonAnalyzer_cfg.py: Python config file.
    3. CATTools/CatAnalyzer/prod/create-batch: It sends the jobs to condor (tested only in KISTI).
  2. Flat-ntuple analyzer: After make the first object selection and save the output in a flat-Trees, the histograms are produced with a code wrote in C++. The code is located in:
    1. https://github.com/brochero/TopCodeljets/blob/master/TreeReader.C
  3. The output of TreeReader.C is divided in two files:
    1. Root file with all the RAW histograms (fully normalized), and
    2. *.h file with all the yields.
  4. Final histograms production: In this step the final plots with all the style requirements are produced. Code is located at
    1. https://github.com/brochero/TopCodeljets/blob/master/Plot.*
  5. Yield tables, systematic variations and cross section (C&C): (Work in progress) Using the output from TreeReader.C, a root macro produces the tables of yields and systematic variations in LaTeX format. Code in:
    1. https://github.com/brochero/TopCodeljets/blob/master/*******

2. Code

In this section you will find some general comments about the code. More details can be found in README of each package.

1. Flat-ntuples production

  • Check the TtbarSingleLeptonAnalyzer.cc code. Here you can modify/include basic cuts. The output of this step includes all the events that contain only one lepton passing the selection requirements.
  • Compile with:
    % scram b -j 20
  • Test the code using only one sample. Go to prod directory and run ttbarSingleLeptonAnalyzer_cfg.py
    cmsRun ttbarSingleLeptonAnalyzer_cfg.py

In this config file you should specify if you are running over DATA or MC:

# Data or MC Sample
runOnMC = True
# runOnTTbarMC = 0, No ttbar
# runOnTTbarMC = 1, ttbar Signal
# runOnTTbarMC == 2, ttbar Background
runOnTTbarMC = 1

    • runOnMC: True if the sample is MC; False if it is DATA.
    • runOnTTbarMC: 0 to run all MC except ttbar; 1 ttbar signal; 2 ttbar background.
Comment this part when you are running over MC.

# json file

#import FWCore.PythonUtilities.LumiList as LumiList

#process.source.lumisToProcess = LumiList (filename = 'Cert_246908-251883_13TeV_PromptReco_Collisions15_JSON_v2.txt').getVLuminosityBlockRange()

  • Check that the output file (vallot.root) has the correct information.

  • Run over the full available samples. This procedure is performed sample by sample running over all the files using the create-batch file.
    ./create-batch --jobName v7-3-6_DataSingleEG_json-Trigger --fileList List_v7-3-6/DataSingleEG_PromptReco-Run251643-251883.list --maxFiles 1 --cfg ttbarSingleLeptonAnalyzer_cfg.py --queue batch6
    Where DataSingleEG _PromptReco-Run251643-251883.list is a plain file which includes the list of all the files of the process (in this case DATA) with the full path as:


2. Histograms production

  • Download the git repository:
    % git clone https://github.com/brochero/TopCodeljets.git
  • Check the correct path of all input/output directories.
  • To compile:
    % make
  • It creates a TreeReader.run. You can check the how to use it with
    % ./TreeReader.run -h
  • To run, the most recommended way is
    % ./TreeReader.run -i Tree_LepJets_v7-3-6_Spring15-bx50_40pb-1_WJets -o NewPlots _v0
    • -i: Input file. remove the ".root"
    • -o: additional name to the output
  • The file name in this part of the code is the main axis. You mos be careful with the structure name. To avoid any inconvenient, I suggest to use the follow structure:
    • Tree_LepJets_"additional info of the sample"_"Luminosity in pb-1"_"SAMPLE".root
    • Example:
    •  Tree_LepJets_v7-3-6_Spring15-bx50_40pb-1_DataSingleEG.root 
    •  Tree_LepJets_v7-3-6_Spring15-bx50_40pb-1_WW.root= 
    • Where
      • v7-3-6 is the CATTools version.
      • Spring15-bx50 is the MC info.
      • 40pb-1 Luminosity to use in the MC normalization.

3. Task

Here you will find some of the most urgent task which must be performed for the analysis. Please, feel free to put your name in those in which you can contribute and/or add another tasks.

  1. b-tagging code: Implementation of SF_b-tag. (Javier Brochero)
  2. b-tag efficiencies for each MC process. (Javier Brochero and ????)
  3. Comparison between METPF, METnoHF and PuppiMET (Should we add all of them to our ntuples?). (Dooyeon Gyun ????)
  4. Optimization of the event selection cuts. (Ari Lee)
  5. Production of the file list for every CATNtuple production. (Ari Lee)
  6. Tag & Pro package to estimate SF_ID_ISO and SF_Trigger. (Dooyeon Gyun ????)
  7. QCD Daata-Driven method. (Javier Brochero and ????)
  8. Analysis note. (????)
  9. Code to produce yields (C&C). (Javier Brochero)
  10. CMS Fireworks (to display some interesting events. Link HERE). (Ari Lee ????)
  11. PUPPI isolation studies. (Javier Brochero)
  12. Code to normalize MC to the available Luminosity (automatization). (Dooyeon Gyun and Ari Lee????)
  13. Check Br on MADGRAPH ttbar sample. (????)
  14. .....
Edit | Attach | Watch | Print version | History: r6 < r5 < r4 < r3 < r2 | Backlinks | Raw View | Raw edit | More topic actions...
Topic revision: r4 - 2015-09-28 - JavierBrochero
    • Cern Search Icon Cern Search
    • TWiki Search Icon TWiki Search
    • Google Search Icon Google Search

    Sandbox All webs login

  • Edit
  • Attach
This site is powered by the TWiki collaboration platform Powered by PerlCopyright & 2008-2021 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