JetHT primary dataset in NANOAOD format from RunH of 2016 (/JetHT/Run2016H-UL2016_MiniAODv2_NanoAODv9-v1/NANOAOD)
/JetHT/Run2016H-UL2016_MiniAODv2_NanoAODv9-v1/NANOAOD, CMS Collaboration
Cite as: CMS Collaboration (2024). JetHT primary dataset in NANOAOD format from RunH of 2016 (/JetHT/Run2016H-UL2016_MiniAODv2_NanoAODv9-v1/NANOAOD). CERN Open Data Portal. DOI:10.7483/OPENDATA.CMS.8ALJ.MQSO
Dataset Collision CMS 13TeV pp CERN-LHC
Description
JetHT 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
124050331 events. 72 files. 145.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 a high scalar sum of the jet transverse momenta (HT), or at least one or two energetic 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-JetHT-UL2016_MiniAODv2_NanoAODv9
Output dataset: /JetHT/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-JetHT-UL2016_MiniAODv2
Output dataset: /JetHT/Run2016H-UL2016_MiniAODv2-v2/MINIAOD
Step RECO
Release: CMSSW_10_6_8_patch1
Global tag: 106X_dataRun2_v27
Configuration file for RECO step recoskim_Run2016H_JetHT
Output dataset: /JetHT/Run2016H-21Feb2020_UL2016-v1/AOD
HLT trigger paths
The possible HLT trigger paths in this dataset are:
HLT_AK8DiPFJet250_200_TrimMass30_BTagCSV_p20
HLT_AK8DiPFJet250_200_TrimMass30
HLT_AK8DiPFJet280_200_TrimMass30_BTagCSV_p087
HLT_AK8DiPFJet280_200_TrimMass30_BTagCSV_p20
HLT_AK8DiPFJet280_200_TrimMass30
HLT_AK8DiPFJet300_200_TrimMass30_BTagCSV_p087
HLT_AK8DiPFJet300_200_TrimMass30_BTagCSV_p20
HLT_AK8DiPFJet300_200_TrimMass30
HLT_AK8PFHT600_TrimR0p1PT0p03Mass50_BTagCSV_p20
HLT_AK8PFHT650_TrimR0p1PT0p03Mass50
HLT_AK8PFHT700_TrimR0p1PT0p03Mass50
HLT_AK8PFHT750_TrimMass50
HLT_AK8PFHT800_TrimMass50
HLT_AK8PFJet140
HLT_AK8PFJet200
HLT_AK8PFJet260
HLT_AK8PFJet320
HLT_AK8PFJet360_TrimMass30
HLT_AK8PFJet400_TrimMass30
HLT_AK8PFJet400
HLT_AK8PFJet40
HLT_AK8PFJet450
HLT_AK8PFJet500
HLT_AK8PFJet60
HLT_AK8PFJet80
HLT_CaloJet500_NoJetID
HLT_DiCentralPFJet170_CFMax0p1
HLT_DiCentralPFJet170
HLT_DiCentralPFJet220_CFMax0p3
HLT_DiCentralPFJet330_CFMax0p5
HLT_DiCentralPFJet430
HLT_DiJetVBFMu_PassThrough
HLT_DiJetVBF_PassThrough
HLT_DiPFJetAve100_HFJEC
HLT_DiPFJetAve140
HLT_DiPFJetAve160_HFJEC
HLT_DiPFJetAve200
HLT_DiPFJetAve220_HFJEC
HLT_DiPFJetAve260
HLT_DiPFJetAve300_HFJEC
HLT_DiPFJetAve320
HLT_DiPFJetAve400
HLT_DiPFJetAve40
HLT_DiPFJetAve500
HLT_DiPFJetAve60_HFJEC
HLT_DiPFJetAve60
HLT_DiPFJetAve80_HFJEC
HLT_DiPFJetAve80
HLT_HT2000
HLT_HT2500
HLT_L1_TripleJet_VBF
HLT_PFHT125
HLT_PFHT200
HLT_PFHT250
HLT_PFHT300
HLT_PFHT350
HLT_PFHT400_SixJet30_DoubleBTagCSV_p056
HLT_PFHT400_SixJet30
HLT_PFHT400
HLT_PFHT450_SixJet40_BTagCSV_p056
HLT_PFHT450_SixJet40
HLT_PFHT475
HLT_PFHT550_4JetPt50
HLT_PFHT600
HLT_PFHT650_4JetPt50
HLT_PFHT650_WideJetMJJ900DEtaJJ1p5
HLT_PFHT650_WideJetMJJ950DEtaJJ1p5
HLT_PFHT650
HLT_PFHT750_4JetPt50
HLT_PFHT750_4JetPt70
HLT_PFHT750_4JetPt80
HLT_PFHT800_4JetPt50
HLT_PFHT800
HLT_PFHT850_4JetPt50
HLT_PFHT900
HLT_PFJet140
HLT_PFJet200
HLT_PFJet260
HLT_PFJet320
HLT_PFJet400
HLT_PFJet40
HLT_PFJet450
HLT_PFJet500
HLT_PFJet60
HLT_PFJet80
HLT_QuadPFJet_VBF
HLT_SingleCentralPFJet170_CFMax0p1
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
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.
