DoubleMu primary dataset in AOD format from RunA of 2011 (/DoubleMu/Run2011A-12Oct2013-v1/AOD)
/DoubleMu/Run2011A-12Oct2013-v1/AOD, CMS collaboration
Cite as: CMS collaboration (2016). DoubleMu primary dataset in AOD format from RunA of 2011 (/DoubleMu/Run2011A-12Oct2013-v1/AOD). CERN Open Data Portal. DOI:10.7483/OPENDATA.CMS.RZ34.QR6N
Dataset Collision CMS 7TeV pp CERN-LHC
Description
DoubleMu primary dataset in AOD format from RunA of 2011. Run period from run number 160404 to 173692.
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
Dataset characteristics
39668813 events. 1378 files. 4.8 TiB in total.System details
FT_53_LV5_AN1CMSSW_5_3_32
Recommended container image for analyses is available in the following locations (see guide):
docker.io/cmsopendata/cmssw_5_3_32-slc6_amd64_gcc472:latestgitlab-registry.cern.ch/cms-cloud/cmssw-docker-opendata/cmssw_5_3_32-slc6_amd64_gcc472:latest
How were these data selected?
Events stored in this primary dataset were selected because of the presence of at least two high-energy muon 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 AOD dataset was processed from the RAW dataset by the following step:
Step: RECO
Release: CMSSW_5_3_12_patch1
Global tag: FT_R_53_LV5::All
Configuration file for RECO step reco_2011_DoubleMu
HLT trigger paths
The possible HLT trigger paths in this dataset are:
HLT_DoubleMu3
HLT_DoubleMu45
HLT_DoubleMu4_Acoplanarity03
HLT_DoubleMu5
HLT_DoubleMu5_Acoplanarity03
HLT_DoubleMu5_IsoMu5
HLT_DoubleMu6
HLT_DoubleMu6_Acoplanarity03
HLT_DoubleMu7
HLT_DoubleMu7_Acoplanarity03
HLT_L1DoubleMu0
HLT_L2DoubleMu0
HLT_L2DoubleMu23_NoVertex
HLT_L2DoubleMu30_NoVertex
HLT_L2DoubleMu30_NoVertex_dPhi2p5
HLT_L2DoubleMu35_NoVertex
HLT_L2DoubleMu45_NoVertex
HLT_Mu13_Mu8
HLT_Mu17_Mu8
HLT_Mu17_TkMu8
HLT_Mu8_Jet40
HLT_TripleMu5
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:
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
How can you use these data?
You can access these data through the CMS Virtual Machine. See the instructions for setting up the Virtual Machine and getting started in
Disclaimer
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.
