MuonEG primary dataset in MINIAOD format from RunD of 2015 (/MuonEG/Run2015D-16Dec2015-v1/MINIAOD)
/MuonEG/Run2015D-16Dec2015-v1/MINIAOD, CMS collaboration
Cite as: CMS collaboration (2021). MuonEG primary dataset in MINIAOD format from RunD of 2015 (/MuonEG/Run2015D-16Dec2015-v1/MINIAOD). CERN Open Data Portal. DOI:10.7483/OPENDATA.CMS.ATNG.FSX3
Dataset Collision CMS 13TeV pp CERN-LHC
Description
MuonEG 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
13442593 events. 297 files. 270.1 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 the presence of one energetic muon and electron or photon.
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_MuonEG
HLT trigger paths
The possible HLT trigger paths in this dataset are:
HLT_DiMu9_Ele9_CaloIdL_TrackIdL
HLT_Mu12_Photon25_CaloIdL_L1ISO
HLT_Mu12_Photon25_CaloIdL_L1OR
HLT_Mu12_Photon25_CaloIdL
HLT_Mu17_Photon22_CaloIdL_L1ISO
HLT_Mu17_Photon30_CaloIdL_L1ISO
HLT_Mu17_Photon35_CaloIdL_L1ISO
HLT_Mu17_TrkIsoVVL_Ele12_CaloIdL_TrackIdL_IsoVL
HLT_Mu23NoFiltersNoVtx_Photon23_CaloIdL
HLT_Mu23_TrkIsoVVL_Ele12_CaloIdL_TrackIdL_IsoVL
HLT_Mu28NoFiltersNoVtxDisplaced_Photon28_CaloIdL
HLT_Mu30_Ele30_CaloIdL_GsfTrkIdVL
HLT_Mu33NoFiltersNoVtxDisplaced_Photon33_CaloIdL
HLT_Mu38NoFiltersNoVtx_Photon38_CaloIdL
HLT_Mu42NoFiltersNoVtx_Photon42_CaloIdL
HLT_Mu8_DiEle12_CaloIdL_TrackIdL
HLT_Mu8_Ele8_CaloIdM_TrackIdM_Mass8_PFHT250
HLT_Mu8_Ele8_CaloIdM_TrackIdM_Mass8_PFHT300
HLT_Mu8_TrkIsoVVL_Ele17_CaloIdL_TrackIdL_IsoVL
HLT_Mu8_TrkIsoVVL_Ele23_CaloIdL_TrackIdL_IsoVL
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
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.
