JetHT primary dataset in MINIAOD format from RunD of 2015 (/JetHT/Run2015D-16Dec2015-v1/MINIAOD)
/JetHT/Run2015D-16Dec2015-v1/MINIAOD, CMS collaboration
Cite as: CMS collaboration (2021). JetHT primary dataset in MINIAOD format from RunD of 2015 (/JetHT/Run2015D-16Dec2015-v1/MINIAOD). CERN Open Data Portal. DOI:10.7483/OPENDATA.CMS.IDN0.S11Z
Dataset Collision CMS 13TeV CERN-LHC
Description
JetHT primary dataset in MINIAOD format from RunD of 2015. Run period from run number 256630 to 260627.
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 AOD dataset:Dataset characteristics
76523854 events. 1607 files. 1.5 TB in total.System details
76X_dataRun2_16Dec2015_v0CMSSW_7_6_7
How 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 / RECO
This primary MINIAOD dataset was processed from the RAW dataset by the following step:
Step: RECO
Release: CMSSW_7_6_3
Global tag: 76X_dataRun2_v15
Configuration file for RECO step reco_2015D_JetHT
HLT trigger paths
The possible HLT trigger paths in this dataset are:
HLT_AK8DiPFJet250_200_TrimMass30_BTagCSV0p45
HLT_AK8DiPFJet280_200_TrimMass30_BTagCSV0p45
HLT_AK8PFHT600_TrimR0p1PT0p03Mass50_BTagCSV0p45
HLT_AK8PFHT650_TrimR0p1PT0p03Mass50
HLT_AK8PFHT700_TrimR0p1PT0p03Mass50
HLT_AK8PFJet360_TrimMass30
HLT_CaloJet500_NoJetID
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_HT200
HLT_HT2500
HLT_HT275
HLT_HT325
HLT_HT425
HLT_HT575
HLT_L1_TripleJet_VBF
HLT_PFHT200
HLT_PFHT250
HLT_PFHT300
HLT_PFHT350
HLT_PFHT400_SixJet30_BTagCSV0p55_2PFBTagCSV0p72
HLT_PFHT400_SixJet30
HLT_PFHT400
HLT_PFHT450_SixJet40_PFBTagCSV0p72
HLT_PFHT450_SixJet40
HLT_PFHT475
HLT_PFHT550_4JetPt50
HLT_PFHT550_4Jet
HLT_PFHT600
HLT_PFHT650_4JetPt50
HLT_PFHT650_4Jet
HLT_PFHT650_WideJetMJJ900DEtaJJ1p5
HLT_PFHT650_WideJetMJJ950DEtaJJ1p5
HLT_PFHT650
HLT_PFHT750_4JetPt50
HLT_PFHT800
HLT_PFJet140
HLT_PFJet200
HLT_PFJet260
HLT_PFJet320
HLT_PFJet400
HLT_PFJet40
HLT_PFJet450
HLT_PFJet500
HLT_PFJet60
HLT_PFJet80
HLT_QuadPFJet_VBF
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
File Indexes
{{$ctrlTbl.files = $ctrl.index_files.files; ""}}
{{$ctrlTbl.totalItems = $ctrl.index_files.total; ""}}
Filename
Size
Filename
Size
Files
{{$ctrlTbl.files = $ctrl.files.files; ""}}
{{$ctrlTbl.totalItems = $ctrl.files.total; ""}}
Filename
Size
Filename
Size
Disclaimer
The open data are released under the Creative Commons CC0 waiver. Neither 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.
