Tau primary dataset in MINIAOD format from RunH of 2016 (/Tau/Run2016H-UL2016_MiniAODv2-v1/MINIAOD)
/Tau/Run2016H-UL2016_MiniAODv2-v1/MINIAOD, CMS Collaboration
Cite as: CMS Collaboration (2024). Tau primary dataset in MINIAOD format from RunH of 2016 (/Tau/Run2016H-UL2016_MiniAODv2-v1/MINIAOD). CERN Open Data Portal. DOI:10.7483/OPENDATA.CMS.6320.UJGP
Dataset Collision CMS 13TeV pp CERN-LHC Parent Dataset:
Description
Tau primary dataset in MINIAOD format from RunH of 2016. Run period from run number 281613 to 284044.
The list of validated runs, which must be applied to all analyses, either with the full validation or for an analysis requiring only muons, can be found in:
Related datasets
The corresponding NANOAOD dataset:Dataset characteristics
76758754 events. 701 files. 2.3 TiB in total.System details
106X_dataRun2_v37CMSSW_10_6_30
Recommended container image for analyses is available in the following locations (see guide):
docker.io/cmsopendata/cmssw_10_6_30-slc7_amd64_gcc700:latestgitlab-registry.cern.ch/cms-cloud/cmssw-docker-opendata/cmssw_10_6_30-slc7_amd64_gcc700:latest
How were these data selected?
Events stored in this primary dataset were selected because of the presence of at least one tau, or one tau and muon or high missing transverse momentum.
Data taking / HLT
The collision data were assigned to different RAW datasets using the following HLT configuration.
Data processing
This MINIAOD dataset was processed from the RAW dataset by the following steps:
Step PAT
Release: CMSSW_10_6_25
Global tag: 106X_dataRun2_v35
Configuration file for PAT step ReReco-Run2016H-Tau-UL2016_MiniAODv2
Output dataset: /Tau/Run2016H-UL2016_MiniAODv2-v1/MINIAOD
Step RECO
Release: CMSSW_10_6_8_patch1
Global tag: 106X_dataRun2_v27
Configuration file for RECO step recoskim_Run2016H_Tau
Output dataset: /Tau/Run2016H-21Feb2020_UL2016-v1/AOD
HLT trigger paths
The possible HLT trigger paths in this dataset are:
HLT_DoubleMediumCombinedIsoPFTau35_Trk1_eta2p1_Reg
HLT_DoubleMediumCombinedIsoPFTau40_Trk1_eta2p1_Reg
HLT_DoubleMediumCombinedIsoPFTau40_Trk1_eta2p1
HLT_DoubleMediumIsoPFTau32_Trk1_eta2p1_Reg
HLT_DoubleMediumIsoPFTau35_Trk1_eta2p1_Reg
HLT_DoubleMediumIsoPFTau40_Trk1_eta2p1_Reg
HLT_DoubleTightCombinedIsoPFTau35_Trk1_eta2p1_Reg
HLT_DoubleTightCombinedIsoPFTau40_Trk1_eta2p1_Reg
HLT_DoubleTightCombinedIsoPFTau40_Trk1_eta2p1
HLT_IsoMu19_eta2p1_LooseCombinedIsoPFTau20
HLT_IsoMu19_eta2p1_MediumCombinedIsoPFTau32_Trk1_eta2p1_Reg
HLT_IsoMu19_eta2p1_TightCombinedIsoPFTau32_Trk1_eta2p1_Reg
HLT_IsoMu21_eta2p1_MediumCombinedIsoPFTau32_Trk1_eta2p1_Reg
HLT_IsoMu21_eta2p1_TightCombinedIsoPFTau32_Trk1_eta2p1_Reg
HLT_LooseIsoPFTau50_Trk30_eta2p1_MET110
HLT_LooseIsoPFTau50_Trk30_eta2p1_MET120
HLT_LooseIsoPFTau50_Trk30_eta2p1_MET80
HLT_LooseIsoPFTau50_Trk30_eta2p1_MET90
HLT_LooseIsoPFTau50_Trk30_eta2p1
HLT_PFTau120_eta2p1
HLT_PFTau140_eta2p1
HLT_VLooseIsoPFTau120_Trk50_eta2p1
HLT_VLooseIsoPFTau140_Trk50_eta2p1
How were these data validated?
During data taking all the runs recorded by CMS are certified as good for physics analysis if all subdetectors, trigger, lumi and physics objects (tracking, electron, muon, photon, jet and MET) show the expected performance. Certification is based first on the offline shifters evaluation and later on the feedback provided by detector and Physics Object Group experts. Based on the above information, which is stored in a specific database called Run Registry, the Data Quality Monitoring group verifies the consistency of the certification and prepares a json file of certified runs to be used for physics analysis. For each reprocessing of the raw data, the above mentioned steps are repeated. For more information see:
The Data Quality Monitoring Software for the CMS experiment at the LHC: past, present and future
How can you use these data?
You can access these data through the CMS Open Data container or the CMS Virtual Machine. See the instructions for setting up one of the two alternative environments and getting started in
Running CMS analysis code using Docker
Disclaimer
The open data are released under the Creative Commons CC0 waiver. Neither the experiment(s) ( CMS ) nor CERN endorse any works, scientific or otherwise, produced using these data. All releases will have a unique DOI that you are requested to cite in any applications or publications.
