/HTMHT/Run2015D-16Dec2015-v1/MINIAOD, CMS collaboration
Cite as: CMS collaboration (2021). HTMHT primary dataset in MINIAOD format from RunD of 2015 (/HTMHT/Run2015D-16Dec2015-v1/MINIAOD). CERN Open Data Portal. DOI:10.7483/OPENDATA.CMS.SRUP.MHPK
Dataset Collision CMS 13TeV pp CERN-LHC
HTMHT 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:
docker.io/cmsopendata/cmssw_7_6_7-slc6_amd64_gcc493:latest
gitlab-registry.cern.ch/cms-cloud/cmssw-docker-opendata/cmssw_7_6_7-slc6_amd64_gcc493:latest
Events stored in this primary dataset were selected because of the presence of a combination of a high scalar sum of the jet transverse momenta (HT); one or more energetic jets; or high missing transverse energy.
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_HTMHT
HLT trigger paths
The possible HLT trigger paths in this dataset are:
HLT_DiCentralPFJet55_PFMET110_JetIdCleaned
HLT_DiCentralPFJet55_PFMET110
HLT_DiPFJet40_DEta3p5_MJJ600_PFMETNoMu140_JetIdCleaned
HLT_DiPFJet40_DEta3p5_MJJ600_PFMETNoMu140
HLT_DiPFJet40_DEta3p5_MJJ600_PFMETNoMu80_JetIdCleaned
HLT_DiPFJet40_DEta3p5_MJJ600_PFMETNoMu80
HLT_PFHT200_DiPFJetAve90_PFAlphaT0p57
HLT_PFHT200_DiPFJetAve90_PFAlphaT0p63
HLT_PFHT200_PFAlphaT0p51
HLT_PFHT250_DiPFJetAve90_PFAlphaT0p55
HLT_PFHT250_DiPFJetAve90_PFAlphaT0p58
HLT_PFHT300_DiPFJetAve90_PFAlphaT0p53
HLT_PFHT300_DiPFJetAve90_PFAlphaT0p54
HLT_PFHT350_DiPFJetAve90_PFAlphaT0p52
HLT_PFHT350_DiPFJetAve90_PFAlphaT0p53
HLT_PFHT350_PFMET100_JetIdCleaned
HLT_PFHT350_PFMET100
HLT_PFHT400_DiPFJetAve90_PFAlphaT0p51
HLT_PFHT400_DiPFJetAve90_PFAlphaT0p52
HLT_Rsq0p25
HLT_Rsq0p30
HLT_RsqMR240_Rsq0p09_MR200_4jet
HLT_RsqMR240_Rsq0p09_MR200
HLT_RsqMR270_Rsq0p09_MR200_4jet
HLT_RsqMR270_Rsq0p09_MR200
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
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
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.