-
Notifications
You must be signed in to change notification settings - Fork 51
Home
Information on checking out the package is given in the project main page.
Steering of the canidate building code is controlled by a single .py file, AnalysisStep/test/MasterPy/ZZ4lAnalysis.py, which contains all cuts and selection criteria. This .py produces a transient collection of CompositeCandidates, which contains ZZ candidates passing the full selection, with additional information attached as userFloats.
Information from this collection can be collected with standard CMSSW analysis modules, either to fill histograms directly or to fill trees with more compact information. A simple tree builder is implemented in AnalysisStep/test/Ntuplizers/HZZ4lNtupleMaker.cc. The standard configuration of the tree builder is given in AnalysisStep/test/analyzer.py.
Currently active branches/tags (sample folders in the group's EOS folder)
-
Run2_CutBased_BTag16: HIG-19-001; samples:
RunIILegacy/200205_CutBased/(MC);RunIILegacy/200430_LegacyRun2/ (data). Frozen. -
Run2_CutBased_UL: (current default branch): Run II differential analysis. Samples:
RunIIUL/(tag: UL-DifferentialProd) - Run2UL_22: development for upcoming UL analyses (high-mass, off-shell)
- Run2UL_22_nano: based and synchronized to Run2_UL22; development of a simple nanoAOD-based framework
- Run3_22: based on Run2_UL22_nano; port to CMSSW 12 and initial updates for Run 3 analysis
Branches used for past results:
- [list to be filled]
In order to run synchronization as described in the sync wiki page, the file AnalysisStep/test/analyzer_7XSync.py can be run interactively. This produces one tree (ZZ4lAnalysis.root). The script AnalysisStep/test/synchronizer.py runs on the tree and produces the synchronization file. A second script synchronizerCR.py produces sync files for CRs (DY sync samples should be selected, and filling of CRs must be activated in analyzer_7XSync.py for this purpose).
Note that categorization is computed by the script based on the information stored in the tree. This is based on the code in AnalysisStep/interface/Category.h. Please check synchronizerCR.py to see how it is called.
A list of samples to be processed is maintained in the files AnalysisStep/test/prod/samples_*.csv here.
Starting from this list, some scripts are available to process all samples on the CERN batch system. For details see the Submitting Jobs page.
A simple nanoAOD framework based on nanoAODTools is under development in branch Run2_UL22_nano. See this page for details.