Introduction
We have some standard programs to make plots and dump cutflows from the ttH ntuples. These exploit TTree::Draw() to let the user draw quantities or count events with appropriate cross sections and corrections applied. The cuts and plots are specified in files using "yaml" syntax (see a very simple introduction here).
Installing the Software
The software comes as part of the ttH multileptonic code, which is unfortunately a rather large code base. Follow the check out procedures given in the CERN wiki page. The scripts are all in the HWWtthCode/other/stack area. Make sure you set up an athena release and RootCore every time you start a new session working with these scripts.
The scripts we're going to use are called do_cutflow.py and dump_plots2.py. They're part of a broader suite of programs based on stack.py, which allows you to do interactive querying and plotting of the MC and data from the command line. Basically do_cutflow.py and dump_plots2.py automate calls to stack.py.
The Input Data
You can use the files in /data/tth/v4_processed/trigpdf. Any output of our ntupler will be compatible with this software (see 8 13 TeV tth Analysis with MultiLepAnalysisNtupler for instructions to build and run that ntupler). The ntupler expects the MC files to be provided with names of the form "DSID.root", and the data files to be "period*.root". All files should be in the same directory.
The Configuration and Cross Section Files
The cross sections for all processes are specified in HWWtthCode/XsectionInput/Xsection8TeV_tth_bkg_v2.yaml and Xsection8TeV_tth_sig_v2.yaml. These are autogenerated from the corresponding .txt files in the same directory, which are much easier to read. By default the "priority 1" samples are the ones that are used, although in practice we override these choices with some regularity. When you run either the cutflow dumper or the plotter, they will first print out all the MC files they have loaded, so you can keep track of what is being done.
You are unlikely to ever need to edit config_8TeV.yaml, but for completeness, this is the file that maps the process names given in the cross section files to categories of processes (e.g. "single top" or "diboson"). Effectively it groups the DSIDs and configures how they will be displayed in the cutflows and plots (and what colors the histograms will be). The color choices are the result of a carefully negotiated agreement, don't touch them unless really necessary. This file also contains weights for various Alpgen Z samples which you can mostly ignore.
Making Cutflows
The cuts are specified in yaml files, in lists like:
...
standard_3l_cutflow.yaml: shows the standard 3l cutflow.
Dumping Plots
Two different things need to be specified for plots:
...