MuOnia primary dataset in AOD format from RunA of 2011 (/MuOnia/Run2011A-12Oct2013-v1/AOD)
/MuOnia/Run2011A-12Oct2013-v1/AOD, CMS collaboration
Cite as: CMS collaboration (2016). MuOnia primary dataset in AOD format from RunA of 2011 (/MuOnia/Run2011A-12Oct2013-v1/AOD). CERN Open Data Portal. DOI:10.7483/OPENDATA.CMS.FZ5U.TTXP
Dataset Collision CMS 7TeV pp CERN-LHC
Description
MuOnia 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
62229649 events. 2298 files. 7.6 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 muons in the event requiring only very low energy and some requirements in the invariant mass for selecting low-mass resonances.
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_MuOnia
HLT trigger paths
The possible HLT trigger paths in this dataset are:
HLT_Dimuon0_Barrel_Upsilon
HLT_Dimuon0_Jpsi
HLT_Dimuon0_Jpsi_Muon
HLT_Dimuon0_Jpsi_NoVertexing
HLT_Dimuon0_Omega_Phi
HLT_Dimuon0_Upsilon
HLT_Dimuon0_Upsilon_Muon
HLT_Dimuon10_Jpsi_Barrel
HLT_Dimuon11_PsiPrime
HLT_Dimuon13_Jpsi_Barrel
HLT_Dimuon4_Bs_Barrel
HLT_Dimuon5_Upsilon_Barrel
HLT_Dimuon6_Bs
HLT_Dimuon6_LowMass
HLT_Dimuon6p5_Barrel_Jpsi
HLT_Dimuon6p5_Barrel_PsiPrime
HLT_Dimuon6p5_Jpsi
HLT_Dimuon6p5_Jpsi_Displaced
HLT_Dimuon6p5_LowMass
HLT_Dimuon6p5_LowMass_Displaced
HLT_Dimuon7_Jpsi_Displaced
HLT_Dimuon7_Jpsi_X_Barrel
HLT_Dimuon7_LowMass_Displaced
HLT_Dimuon7_PsiPrime
HLT_Dimuon7_Upsilon_Barrel
HLT_Dimuon9_PsiPrime
HLT_Dimuon9_Upsilon_Barrel
HLT_DoubleMu2_Bs
HLT_DoubleMu3_Bs
HLT_DoubleMu3_Jpsi
HLT_DoubleMu3_LowMass
HLT_DoubleMu3_Quarkonium
HLT_DoubleMu3_Upsilon
HLT_DoubleMu3p5_Jpsi_Displaced
HLT_DoubleMu4_Dimuon4_Bs_Barrel
HLT_DoubleMu4_Dimuon6_Bs
HLT_DoubleMu4_Jpsi_Displaced
HLT_DoubleMu4_LowMass_Displaced
HLT_DoubleMu4p5_LowMass_Displaced
HLT_DoubleMu5_Jpsi_Displaced
HLT_DoubleMu5_LowMass_Displaced
HLT_Mu3_Track3_Jpsi
HLT_Mu5_L2Mu2
HLT_Mu5_L2Mu2_Jpsi
HLT_Mu5_Track2_Jpsi
HLT_Mu7_Track5_Jpsi
HLT_Mu7_Track7_Jpsi
HLT_TripleMu0_TauTo3Mu
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.
