DoubleMuon primary dataset in MINIAOD format from RunD of 2015 (/DoubleMuon/Run2015D-16Dec2015-v1/MINIAOD)
/DoubleMuon/Run2015D-16Dec2015-v1/MINIAOD, CMS collaboration
Cite as: CMS collaboration (2021). DoubleMuon primary dataset in MINIAOD format from RunD of 2015 (/DoubleMuon/Run2015D-16Dec2015-v1/MINIAOD). CERN Open Data Portal. DOI:10.7483/OPENDATA.CMS.H3TX.ZJZX
Dataset Collision CMS 13TeV pp CERN-LHC
Description
DoubleMuon 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
51342919 events. 1068 files. 804.6 GiB in total.System details
76X_dataRun2_16Dec2015_v0CMSSW_7_6_7
Recommended container image for analyses is available in the following locations (see guide):
docker.io/cmsopendata/cmssw_7_6_7-slc6_amd64_gcc493:latestgitlab-registry.cern.ch/cms-cloud/cmssw-docker-opendata/cmssw_7_6_7-slc6_amd64_gcc493:latest
How were these data selected?
Events stored in this primary dataset were selected because of the presence of at least two energetic muons in the event.
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_DoubleMuon
HLT trigger paths
The possible HLT trigger paths in this dataset are:
HLT_DoubleMu18NoFiltersNoVtx
HLT_DoubleMu23NoFiltersNoVtxDisplaced
HLT_DoubleMu28NoFiltersNoVtxDisplaced
HLT_DoubleMu33NoFiltersNoVtx
HLT_DoubleMu38NoFiltersNoVtx
HLT_DoubleMu8_Mass8_PFHT250
HLT_DoubleMu8_Mass8_PFHT300
HLT_L2DoubleMu23_NoVertex
HLT_L2DoubleMu28_NoVertex_2Cha_Angle2p5_Mass10
HLT_L2DoubleMu38_NoVertex_2Cha_Angle2p5_Mass10
HLT_Mu10_CentralPFJet30_BTagCSV0p54PF
HLT_Mu17_Mu8_DZ
HLT_Mu17_Mu8_SameSign_DZ
HLT_Mu17_Mu8
HLT_Mu17_TkMu8_DZ
HLT_Mu17_TrkIsoVVL_Mu8_TrkIsoVVL_DZ
HLT_Mu17_TrkIsoVVL_Mu8_TrkIsoVVL
HLT_Mu17_TrkIsoVVL_TkMu8_TrkIsoVVL_DZ
HLT_Mu17_TrkIsoVVL_TkMu8_TrkIsoVVL
HLT_Mu17_TrkIsoVVL
HLT_Mu17
HLT_Mu20_Mu10_DZ
HLT_Mu20_Mu10_SameSign_DZ
HLT_Mu20_Mu10
HLT_Mu24_TrkIsoVVL
HLT_Mu24
HLT_Mu27_TkMu8
HLT_Mu30_TkMu11
HLT_Mu34_TrkIsoVVL
HLT_Mu34
HLT_Mu40_TkMu11
HLT_Mu8_TrkIsoVVL
HLT_Mu8
HLT_TripleMu_12_10_5
HLT_TrkMu15_DoubleTrkMu5NoFiltersNoVtx
HLT_TrkMu17_DoubleTrkMu8NoFiltersNoVtx
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
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.
