Stop 0L 13 TeV Production

Basic info

The 0L stop analysis uses crab to do all pre processing to produce personalized NanoAOD ntuples to include the resolved SUSY tagger. The code used is here for preprocessing: NanoSUSY

Instructions to go from making our Ntuples to post processing is here: Lets Make Ntuples

Lumi information can be found here: Lumi

General global Tag information can be found here: GlobalTag Please be aware when or if using automatic global tag that the tag you want needs to be available in the CMSSW version you are running on.

List of samples are in multiple places one place is here: Signal and Background/Data this will link crab submission to pre processing to post processing so locations of files will be listed there and naming convention of the samples also listed here.

Pre Processing General information

Pre Processing CFG and file location

  • CFG files live here: PreProcess_StopNtuple
  • Current Tag is here: TBD
  • 2016 Production
    • The samples are here: Summer16_94X_v3
  • 2017 Production
    • The MC samples: Fall17_94X_v2_NanAOD_MC
    • The data samples: Fall17_94X_Mar_2018_NanAOD_Data
  • 2018 Production
    • The samples are here: Autumn18_102X_v1


  • Are bing used by koushik and Joe
  • Moving to NanoAOD when that happens will be deleted
  • Top_ntuple_V8, Top_ntuple_V9 directories
  • trainingTuples directories

"CMSSW8028_2016" production (Should be deleted when Cross checks are done)

  • Are being used by Hui for cross checks
  • Lumi info: 35.9/fb
  • Location: /eos/uscms/store/user/lpcsusyhad/Stop_production/CMSSW8028_2016/
  • Remarks: DeepAK8, Deep resolved, Goldilocks variables all included, doubles to floats, 2 different electron types ID's

Ntuples used for 2016 data publications

  • Are not hosted at Baylor
  • Location : /eos/uscms/store/user/lpcsusyhad/Stop_production
  • Summer16_80X_Mar_2017_Ntp_v13X
  • Summer16_80X_Mar_2017_Ntp_v13X_rerun
  • Summer16_80X_Mar_2017_Ntp_v13X_UCSB_signals

"TriggerStudies2017" production (this maybe outdated maybe Hui can update it if it is still needed or delete it)

  • Lumi info: 41.82 /fb For MET 2017
  • Location: /eos/uscms/store/user/lpcsusyhad/Stop_production/TriggerStudies2017

Post Processing General information

  • General information
  • Current Config here: PostProcess_StopTuple_V2.6.0
  • V1 production
    • This code used what is currently master branch as of Apr24th. I do not think it was ever tagged.
    • It did not have scale factors or systematics and was missing TauMVA.
  • V2p2 production
    • This was a intermediate production and had some scale factor stuff Found some problems and is now deleted.
  • V2p6 production
    • Second full processing 2016-2018
    • Had scale factors included
    • initial look
    • There was a Tag but there was an issue with initial submission so a change was made in the code[ [][postpro_v2.7]]

  • V2p7 production
    • Code tagged here: postpro_v2.7
    • fixing cross section
    • fixing NAN issue in 2016 for the DeepCSV
    • fixing dphi logic

Search bin Design


  • Z Invisible
    • Control regions:
  • Lost Lepton
    • Control region:
  • QCD *Smearing information

Object information

CMS SUS analysis/object recommendations

Top tags




Electron Modules


Electron ID

Everyone is updating to these collections


Electron Iso and Effective Area

EA_ETA   (1.0,    1.479,    2.0,    2.2,    2.3,    2.4     )
EA_VALUE (0.1440, 0.1562, 0.1032, 0.0859, 0.1116, 0.1321, 0.1654)

Other useful information


-- ScarletNorberg - 2019-04-24

Edit | Attach | Watch | Print version | History: r3 < r2 < r1 | Backlinks | Raw View | WYSIWYG | More topic actions
Topic revision: r3 - 2019-04-24 - unknown
    • 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-2020 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