BTagMu primary dataset in NANOAOD format from RunH of 2016 (/BTagMu/Run2016H-UL2016_MiniAODv2_NanoAODv9-v1/NANOAOD)
/BTagMu/Run2016H-UL2016_MiniAODv2_NanoAODv9-v1/NANOAOD, CMS Collaboration
Cite as: CMS Collaboration (2024). BTagMu primary dataset in NANOAOD format from RunH of 2016 (/BTagMu/Run2016H-UL2016_MiniAODv2_NanoAODv9-v1/NANOAOD). CERN Open Data Portal. DOI:10.7483/OPENDATA.CMS.PQE8.W27O
Data recorded in 2016 and published in 2024Dataset Collision CMS 13TeV pp CERN-LHC
Description
BTagMu primary dataset in NANOAOD 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 MINIAOD dataset:Dataset characteristics
28769703 events. 16 files. 29.9 GiB in total.System details
NANOAOD datasets are in the ROOT tree format and their analysis does not require the use of CMSSW or CMS open data environments. They can be analysed with common ROOT and Python tools.
Recommended container image for analyses is available in the following locations (see guide):
gitlab-registry.cern.ch/cms-cloud/root-vncgitlab-registry.cern.ch/cms-cloud/python-vnc
Dataset semantics
Variable listHow were these data selected?
Events stored in this primary dataset were selected because of the presence of a muon from the b-quark decay, and one or more jets.
Data taking / HLT
The collision data were assigned to different RAW datasets using the following HLT configuration.
Data processing
This NANOAOD dataset was processed from the RAW dataset by the following steps:
Step NANO
Release: CMSSW_10_6_26
Global tag: 106X_dataRun2_v35
Configuration file for NANO step ReReco-Run2016H-BTagMu-UL2016_MiniAODv2_NanoAODv9
Output dataset: /BTagMu/Run2016H-UL2016_MiniAODv2_NanoAODv9-v1/NANOAOD
Step PAT
Release: CMSSW_10_6_25
Global tag: 106X_dataRun2_v35
Configuration file for PAT step ReReco-Run2016H-BTagMu-UL2016_MiniAODv2
Output dataset: /BTagMu/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_BTagMu
Output dataset: /BTagMu/Run2016H-21Feb2020_UL2016-v1/AOD
HLT trigger paths
The possible HLT trigger paths in this dataset are:
HLT_BTagMu_AK8Jet300_Mu5
HLT_BTagMu_DiJet110_Mu5
HLT_BTagMu_DiJet170_Mu5
HLT_BTagMu_DiJet20_Mu5
HLT_BTagMu_DiJet40_Mu5
HLT_BTagMu_DiJet70_Mu5
HLT_BTagMu_Jet300_Mu5
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 XRootD protocol or direct download, and they can be analysed with common ROOT and Python tools. See the instructions for getting started in
Files and indexes
Disclaimer
These open data are released under the Creative Commons Zero v1.0 Universal license.
Neither the experiment(s) ( CMS ) nor CERN endorse any works, scientific or otherwise, produced using these data.
This release has a unique DOI that you are requested to cite in any applications or publications.
