/SingleMu/Run2011B-12Oct2013-v1/AOD, CMS collaboration
Cite as: CMS collaboration (2020). SingleMu primary dataset in AOD format from RunB of 2011 (/SingleMu/Run2011B-12Oct2013-v1/AOD). CERN Open Data Portal. DOI:10.7483/OPENDATA.CMS.XBTD.NKD3
Dataset Collision CMS 7TeV pp CERN-LHC
SingleMu primary dataset in AOD format from RunB of 2011. Run period from run number 175833 to 180252.
The list of validated runs, which must be applied to all analyses, can be found in
CMS list of validated runs Cert_160404-180252_7TeV_ReRecoNov08_Collisions11_JSON.txt
docker.io/cmsopendata/cmssw_5_3_32-slc6_amd64_gcc472:latest
gitlab-registry.cern.ch/cms-cloud/cmssw-docker-opendata/cmssw_5_3_32-slc6_amd64_gcc472:latest
Data taking / HLT
The collision data were assigned to different RAW datasets using the following HLT configuration.
Data processing / RECO
This primary AOD dataset was processed from the RAW dataset by the following step (identical to 2011 RunA):
Step: RECO
Release: CMSSW_5_3_7_patch5
Global tag: FT_R_53_V18::All
Configuration file for RECO step reco_2011_SingleMu
HLT trigger paths
The possible HLT trigger paths in this dataset are:
HLT_IsoMu12
HLT_IsoMu15
HLT_IsoMu15_eta2p1
HLT_IsoMu17
HLT_IsoMu17_eta2p1
HLT_IsoMu20
HLT_IsoMu20_eta2p1
HLT_IsoMu24
HLT_IsoMu24_eta2p1
HLT_IsoMu30
HLT_IsoMu30_eta2p1
HLT_IsoMu34_eta2p1
HLT_IsoMu40_eta2p1
HLT_L1SingleMu10
HLT_L1SingleMu20
HLT_L2Mu10
HLT_L2Mu20
HLT_Mu100
HLT_Mu100_eta2p1
HLT_Mu12
HLT_Mu15
HLT_Mu20
HLT_Mu200_eta2p1
HLT_Mu24
HLT_Mu24_eta2p1
HLT_Mu3
HLT_Mu30
HLT_Mu30_eta2p1
HLT_Mu40
HLT_Mu40_eta2p1
HLT_Mu5
HLT_Mu50_eta2p1
HLT_Mu60
HLT_Mu60_eta2p1
HLT_Mu8
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:
CMS data quality monitoring: Systems and experiences
The CMS Data Quality Monitoring software experience and future improvements
The CMS data quality monitoring software: experience and future prospects
You can access these data through the CMS Virtual Machine. See the instructions for setting up the Virtual Machine and getting started in
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.