MuHad primary dataset in AOD format from RunA of 2011 (/MuHad/Run2011A-12Oct2013-v1/AOD)
/MuHad/Run2011A-12Oct2013-v1/AOD, CMS collaboration
Cite as: CMS collaboration (2016). MuHad primary dataset in AOD format from RunA of 2011 (/MuHad/Run2011A-12Oct2013-v1/AOD). CERN Open Data Portal. DOI:10.7483/OPENDATA.CMS.B57J.DPSR
Dataset Collision CMS 7TeV pp CERN-LHC
Description
MuHad 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
61233399 events. 2603 files. 9.0 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 one or two isolated high-energy muons and a high scalar sum of the jet transverse momenta (HT); or one or two isolated high-energy electrons and a high MR razor kinematic variable, defined in terms of the momentum of the two megajets; or at least one muon and one or more central jets; or high missing transverse momentum from jets and a high scalar sum of the jet transverse momenta (HT); or two different types on high-energy particles, such as a muon and an electron and a high scalar sum of the jet transverse momenta (HT) 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_MuHad
HLT trigger paths
The possible HLT trigger paths in this dataset are:
HLT_DoubleMu3_HT150
HLT_DoubleMu3_HT160
HLT_DoubleMu3_HT200
HLT_DoubleMu3_Mass4_HT150
HLT_DoubleMu5_HT150
HLT_DoubleMu5_Mass4_HT150
HLT_DoubleMu5_Mass8_HT150
HLT_DoubleMu8_Mass8_HT150
HLT_DoubleMu8_Mass8_HT200
HLT_DoubleTkIso10Mu5_Mass8_HT150
HLT_DoubleTkIso10Mu5_Mass8_HT200
HLT_HT200_Mu5_PFMHT35
HLT_HT250_Mu15_PFMHT20
HLT_HT250_Mu15_PFMHT40
HLT_HT250_Mu5_PFMHT35
HLT_HT300_Mu15_PFMHT40
HLT_HT300_Mu15_PFMHT50
HLT_HT300_Mu5_PFMHT40
HLT_HT350_Mu5_PFMHT45
HLT_HT400_Mu5_PFMHT50
HLT_IsoMu17_CentralJet30
HLT_IsoMu17_CentralJet30_BTagIP
HLT_IsoMu17_CentralJet40_BTagIP
HLT_IsoMu17_DiCentralJet30
HLT_IsoMu17_QuadCentralJet30
HLT_IsoMu17_TriCentralJet30
HLT_IsoMu17_eta2p1_CentralJet30
HLT_IsoMu17_eta2p1_CentralJet30_BTagIP
HLT_IsoMu17_eta2p1_CentralPFJet30
HLT_IsoMu17_eta2p1_DiCentralJet30
HLT_IsoMu17_eta2p1_DiCentralPFJet25
HLT_IsoMu17_eta2p1_DiCentralPFJet25_PFMHT15
HLT_IsoMu17_eta2p1_DiCentralPFJet25_PFMHT25
HLT_IsoMu17_eta2p1_DiCentralPFJet30
HLT_IsoMu17_eta2p1_DiPFJet25_Deta3
HLT_IsoMu17_eta2p1_DiPFJet25_Deta3_PFJet25
HLT_IsoMu17_eta2p1_QuadCentralJet30
HLT_IsoMu17_eta2p1_QuadCentralPFJet30
HLT_IsoMu17_eta2p1_TriCentralJet30
HLT_IsoMu17_eta2p1_TriCentralPFJet30
HLT_IsoMu20_DiCentralJet34
HLT_Mu10_R005_MR200
HLT_Mu10_R014_MR200
HLT_Mu10_R025_MR200
HLT_Mu10_R029_MR200
HLT_Mu10_R033_MR200
HLT_Mu12_CentralJet30_BTagIP
HLT_Mu12_DiCentralJet20_BTagIP3D1stTrack
HLT_Mu12_DiCentralJet20_DiBTagIP3D1stTrack
HLT_Mu12_DiCentralJet30_BTagIP3D
HLT_Mu12_eta2p1_DiCentralJet20_BTagIP3D1stTrack
HLT_Mu12_eta2p1_DiCentralJet20_DiBTagIP3D1stTrack
HLT_Mu12_eta2p1_DiCentralJet30_BTagIP3D
HLT_Mu15_HT200
HLT_Mu17_CentralJet30
HLT_Mu17_CentralJet30_BTagIP
HLT_Mu17_CentralJet40_BTagIP
HLT_Mu17_DiCentralJet30
HLT_Mu17_QuadCentralJet30
HLT_Mu17_TriCentralJet30
HLT_Mu17_eta2p1_CentralJet30
HLT_Mu17_eta2p1_CentralJet30_BTagIP
HLT_Mu17_eta2p1_CentralPFJet30
HLT_Mu17_eta2p1_DiCentralJet30
HLT_Mu17_eta2p1_DiCentralPFJet25_PFMHT15
HLT_Mu17_eta2p1_DiCentralPFJet30
HLT_Mu17_eta2p1_DiPFJet25_Deta3
HLT_Mu17_eta2p1_QuadCentralJet30
HLT_Mu17_eta2p1_QuadCentralPFJet30
HLT_Mu17_eta2p1_TriCentralJet30
HLT_Mu17_eta2p1_TriCentralPFJet30
HLT_Mu20_HT200
HLT_Mu30_HT200
HLT_Mu3_DiJet30
HLT_Mu3_Ele8_CaloIdL_TrkIdVL_HT150
HLT_Mu3_Ele8_CaloIdL_TrkIdVL_HT160
HLT_Mu3_Ele8_CaloIdT_TrkIdVL_HT150
HLT_Mu3_Ele8_CaloIdT_TrkIdVL_HT160
HLT_Mu3_QuadJet30
HLT_Mu3_TriJet30
HLT_Mu40_HT200
HLT_Mu40_HT300
HLT_Mu5_DiJet30
HLT_Mu5_Ele8_CaloIdT_TrkIdVL_HT150
HLT_Mu5_Ele8_CaloIdT_TrkIdVL_Mass4_HT150
HLT_Mu5_Ele8_CaloIdT_TrkIdVL_Mass8_HT150
HLT_Mu5_HT200
HLT_Mu5_QuadJet30
HLT_Mu5_TriJet30
HLT_Mu60_HT200
HLT_Mu60_HT300
HLT_Mu8_Ele8_CaloIdT_TrkIdVL_Mass8_HT150
HLT_Mu8_Ele8_CaloIdT_TrkIdVL_Mass8_HT200
HLT_Mu8_HT200
HLT_Mu8_R005_MR200
HLT_Mu8_R020_MR200
HLT_Mu8_R025_MR200
HLT_Mu8_R029_MR200
HLT_TkIso10Mu5_Ele8_CaloIdT_CaloIsoVVL_TrkIdVL_Mass8_HT150
HLT_TkIso10Mu5_Ele8_CaloIdT_CaloIsoVVL_TrkIdVL_Mass8_HT200
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
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.
