SingleMuon primary dataset in MINIAOD format from RunH of 2016 (/SingleMuon/Run2016H-UL2016_MiniAODv2-v2/MINIAOD)

How were these data selected?

Events stored in this primary dataset were selected because of the presence of at least one energetic muon, or at least one muon and one or more jets, tau or high missing transverse momentum.

Data taking / HLT
The collision data were assigned to different RAW datasets using the following HLT configuration.

Data processing
This MINIAOD dataset was processed from the RAW dataset by the following steps:

Step PAT
Release: CMSSW_10_6_25
Global tag: 106X_dataRun2_v35
Configuration file for PAT step ReReco-Run2016H-SingleMuon-UL2016_MiniAODv2
Output dataset: /SingleMuon/Run2016H-UL2016_MiniAODv2-v2/MINIAOD

HLT trigger paths
The possible HLT trigger paths in this dataset are:
HLT_DoubleIsoMu17_eta2p1_noDzCut
HLT_DoubleIsoMu17_eta2p1
HLT_IsoMu16_eta2p1_MET30_LooseIsoPFTau50_Trk30_eta2p1
HLT_IsoMu16_eta2p1_MET30
HLT_IsoMu17_eta2p1_LooseIsoPFTau20_SingleL1
HLT_IsoMu17_eta2p1_LooseIsoPFTau20
HLT_IsoMu18
HLT_IsoMu19_eta2p1_LooseIsoPFTau20_SingleL1
HLT_IsoMu19_eta2p1_LooseIsoPFTau20
HLT_IsoMu19_eta2p1_MediumIsoPFTau32_Trk1_eta2p1_Reg
HLT_IsoMu20
HLT_IsoMu21_eta2p1_LooseIsoPFTau20_SingleL1
HLT_IsoMu21_eta2p1_LooseIsoPFTau50_Trk30_eta2p1_SingleL1
HLT_IsoMu21_eta2p1_MediumIsoPFTau32_Trk1_eta2p1_Reg
HLT_IsoMu22_eta2p1
HLT_IsoMu22
HLT_IsoMu24_eta2p1
HLT_IsoMu24
HLT_IsoMu27
HLT_IsoTkMu18
HLT_IsoTkMu20
HLT_IsoTkMu22_eta2p1
HLT_IsoTkMu22
HLT_IsoTkMu24_eta2p1
HLT_IsoTkMu24
HLT_IsoTkMu27
HLT_L1SingleMu16
HLT_L1SingleMu18
HLT_L2Mu10
HLT_Mu10_TrkIsoVVL_DiPFJet40_DEta3p5_MJJ750_HTT350_PFMETNoMu60
HLT_Mu15_IsoVVVL_BTagCSV_p067_PFHT400
HLT_Mu15_IsoVVVL_PFHT350_PFMET50
HLT_Mu15_IsoVVVL_PFHT350
HLT_Mu15_IsoVVVL_PFHT400_PFMET50
HLT_Mu15_IsoVVVL_PFHT400
HLT_Mu15_IsoVVVL_PFHT600
HLT_Mu16_eta2p1_MET30
HLT_Mu20
HLT_Mu24_eta2p1
HLT_Mu27
HLT_Mu28NoFiltersNoVtx_CentralCaloJet40
HLT_Mu28NoFiltersNoVtx_DisplacedJet40_Loose
HLT_Mu300
HLT_Mu30_eta2p1_PFJet150_PFJet50
HLT_Mu33NoFiltersNoVtxDisplaced_DisplacedJet50_Loose
HLT_Mu33NoFiltersNoVtxDisplaced_DisplacedJet50_Tight
HLT_Mu350
HLT_Mu38NoFiltersNoVtxDisplaced_DisplacedJet60_Loose
HLT_Mu38NoFiltersNoVtxDisplaced_DisplacedJet60_Tight
HLT_Mu38NoFiltersNoVtx_DisplacedJet60_Loose
HLT_Mu40_eta2p1_PFJet200_PFJet50
HLT_Mu45_eta2p1
HLT_Mu50_IsoVVVL_PFHT400
HLT_Mu50
HLT_Mu55
HLT_Mu8_TrkIsoVVL_DiPFJet40_DEta3p5_MJJ750_HTT300_PFMETNoMu60
HLT_TkMu17
HLT_TkMu20
HLT_TkMu24_eta2p1
HLT_TkMu27
HLT_TkMu50

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

How to install the CMS Virtual Machine

Getting started with CMS open data