BTagCSV primary dataset in NANOAOD format from RunG of 2016 (/BTagCSV/Run2016G-UL2016_MiniAODv2_NanoAODv9-v1/NANOAOD)
/BTagCSV/Run2016G-UL2016_MiniAODv2_NanoAODv9-v1/NANOAOD, CMS Collaboration
Cite as: CMS Collaboration (2024). BTagCSV primary dataset in NANOAOD format from RunG of 2016 (/BTagCSV/Run2016G-UL2016_MiniAODv2_NanoAODv9-v1/NANOAOD). CERN Open Data Portal. DOI:10.7483/OPENDATA.CMS.QCRI.DFDV
Data recorded in 2016 and published in 2024Dataset Collision CMS 13TeV pp CERN-LHC
Description
BTagCSV primary dataset in NANOAOD format from RunG of 2016. Run period from run number 278820 to 280385.
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
100826567 events. 63 files. 122.3 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 at least two jets, tagged as b-quark jets with combined secondary vertex.
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-Run2016G-BTagCSV-UL2016_MiniAODv2_NanoAODv9
Output dataset: /BTagCSV/Run2016G-UL2016_MiniAODv2_NanoAODv9-v1/NANOAOD
Step PAT
Release: CMSSW_10_6_25
Global tag: 106X_dataRun2_v35
Configuration file for PAT step ReReco-Run2016G-BTagCSV-UL2016_MiniAODv2
Output dataset: /BTagCSV/Run2016G-UL2016_MiniAODv2-v1/MINIAOD
Step RECO
Release: CMSSW_10_6_8_patch1
Global tag: 106X_dataRun2_v27
Configuration file for RECO step recoskim_Run2016G_BTagCSV
Output dataset: /BTagCSV/Run2016G-21Feb2020_UL2016-v1/AOD
HLT trigger paths
The possible HLT trigger paths in this dataset are:
HLT_DoubleJet90_Double30_DoubleBTagCSV_p087
HLT_DoubleJet90_Double30_TripleBTagCSV_p087
HLT_DoubleJetsC100_DoubleBTagCSV_p014_DoublePFJetsC100MaxDeta1p6
HLT_DoubleJetsC100_DoubleBTagCSV_p026_DoublePFJetsC160
HLT_DoubleJetsC100_SingleBTagCSV_p014_SinglePFJetC350
HLT_DoubleJetsC100_SingleBTagCSV_p014
HLT_DoubleJetsC100_SingleBTagCSV_p026_SinglePFJetC350
HLT_DoubleJetsC100_SingleBTagCSV_p026
HLT_DoubleJetsC112_DoubleBTagCSV_p014_DoublePFJetsC112MaxDeta1p6
HLT_DoubleJetsC112_DoubleBTagCSV_p026_DoublePFJetsC172
HLT_QuadJet45_DoubleBTagCSV_p087
HLT_QuadJet45_TripleBTagCSV_p087
HLT_QuadPFJet_BTagCSV_p016_VBF_Mqq460
HLT_QuadPFJet_BTagCSV_p016_VBF_Mqq500
HLT_QuadPFJet_BTagCSV_p016_p11_VBF_Mqq200
HLT_QuadPFJet_BTagCSV_p016_p11_VBF_Mqq240
HLT_Rsq0p02_MR300_TriPFJet80_60_40_BTagCSV_p063_p20_Mbb60_200
HLT_Rsq0p02_MR300_TriPFJet80_60_40_DoubleBTagCSV_p063_Mbb60_200
HLT_Rsq0p02_MR400_TriPFJet80_60_40_DoubleBTagCSV_p063_Mbb60_200
HLT_Rsq0p02_MR450_TriPFJet80_60_40_DoubleBTagCSV_p063_Mbb60_200
HLT_Rsq0p02_MR500_TriPFJet80_60_40_DoubleBTagCSV_p063_Mbb60_200
HLT_Rsq0p02_MR550_TriPFJet80_60_40_DoubleBTagCSV_p063_Mbb60_200
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.
