ElectronHad primary dataset in AOD format from RunB of 2011 (/ElectronHad/Run2011B-12Oct2013-v1/AOD)
/ElectronHad/Run2011B-12Oct2013-v1/AOD, CMS collaboration
Cite as: CMS collaboration (2020). ElectronHad primary dataset in AOD format from RunB of 2011 (/ElectronHad/Run2011B-12Oct2013-v1/AOD). CERN Open Data Portal. DOI:10.7483/OPENDATA.CMS.LXNH.ZQPA
Dataset Collision CMS 7TeV CERN-LHC
Description
ElectronHad primary dataset in AOD format from RunB of 2011. Run period from run number 175833 to 180252.
This dataset contains all runs from 2011 RunB. 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
28212796 events. 1865 files. 6.6 TB in total.System details
FT_53_LV5_AN1CMSSW_5_3_32
How were these data selected?
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_ElectronHad
HLT trigger paths
The possible HLT trigger paths in this dataset are:
HLT_DoubleEle8_CaloIdL_TrkIdVL
HLT_DoubleEle8_CaloIdL_TrkIdVL_HT150
HLT_DoubleEle8_CaloIdL_TrkIdVL_HT160
HLT_DoubleEle8_CaloIdT_TrkIdVL
HLT_DoubleEle8_CaloIdT_TrkIdVL_HT150
HLT_DoubleEle8_CaloIdT_TrkIdVL_HT160
HLT_DoubleEle8_CaloIdT_TrkIdVL_Mass4_HT150
HLT_DoubleEle8_CaloIdT_TrkIdVL_Mass8_HT150
HLT_DoubleEle8_CaloIdT_TrkIdVL_Mass8_HT200
HLT_Ele10_CaloIdL_CaloIsoVL_TrkIdVL_TrkIsoVL_HT200
HLT_Ele10_CaloIdL_CaloIsoVL_TrkIdVL_TrkIsoVL_R005_MR200
HLT_Ele10_CaloIdL_CaloIsoVL_TrkIdVL_TrkIsoVL_R025_MR200
HLT_Ele10_CaloIdL_CaloIsoVL_TrkIdVL_TrkIsoVL_R029_MR200
HLT_Ele10_CaloIdL_TrkIdVL_CaloIsoVL_TrkIsoVL_R005_MR200
HLT_Ele10_CaloIdL_TrkIdVL_CaloIsoVL_TrkIsoVL_R020_MR200
HLT_Ele10_CaloIdL_TrkIdVL_CaloIsoVL_TrkIsoVL_R025_MR200
HLT_Ele10_CaloIdT_CaloIsoVL_TrkIdT_TrkIsoVL_HT200
HLT_Ele10_CaloIdT_TrkIdVL_CaloIsoVL_TrkIsoVL_R020_MR200
HLT_Ele12_CaloIdL_CaloIsoVL_TrkIdVL_TrkIsoVL_R005_MR200
HLT_Ele12_CaloIdL_CaloIsoVL_TrkIdVL_TrkIsoVL_R014_MR200
HLT_Ele12_CaloIdL_CaloIsoVL_TrkIdVL_TrkIsoVL_R025_MR200
HLT_Ele12_CaloIdL_CaloIsoVL_TrkIdVL_TrkIsoVL_R029_MR200
HLT_Ele12_CaloIdL_CaloIsoVL_TrkIdVL_TrkIsoVL_R033_MR200
HLT_Ele15_CaloIdT_CaloIsoVL_TrkIdT_TrkIsoVL
HLT_Ele15_CaloIdT_CaloIsoVL_TrkIdT_TrkIsoVL_HT200
HLT_Ele15_CaloIdT_CaloIsoVL_TrkIdT_TrkIsoVL_HT250
HLT_Ele15_CaloIdT_CaloIsoVL_TrkIdT_TrkIsoVL_HT250_PFMHT25
HLT_Ele15_CaloIdT_CaloIsoVL_TrkIdT_TrkIsoVL_HT250_PFMHT40
HLT_Ele15_CaloIdT_CaloIsoVL_TrkIdT_TrkIsoVL_HT250_PFMHT50
HLT_Ele15_CaloIdVT_CaloIsoT_TrkIdT_TrkIsoT_Jet35_Jet25_Deta2
HLT_Ele15_CaloIdVT_CaloIsoT_TrkIdT_TrkIsoT_Jet35_Jet25_Deta3
HLT_Ele15_CaloIdVT_CaloIsoT_TrkIdT_TrkIsoT_Jet35_Jet25_Deta3_Jet20
HLT_Ele15_CaloIdVT_TrkIdT_Jet35_Jet25_Deta2
HLT_Ele15_CaloIdVT_TrkIdT_Jet35_Jet25_Deta3_Jet20
HLT_Ele17_CaloIdVT_CaloIsoT_TrkIdT_TrkIsoT_CentralJet30_CentralJet25_PFMHT15
HLT_Ele17_CaloIdVT_CaloIsoT_TrkIdT_TrkIsoT_Jet35_Jet25_Deta3p5_Jet25
HLT_Ele17_CaloIdVT_TrkIdT_CentralJet30_CentralJet25
HLT_Ele20_CaloIdVT_CaloIsoT_TrkIdT_TrkIsoT_Jet35_Jet25_Deta3_Jet20
HLT_Ele22_CaloIdVT_CaloIsoT_TrkIdT_TrkIsoT_CentralJet30_CentralJet25
HLT_Ele22_CaloIdVT_CaloIsoT_TrkIdT_TrkIsoT_CentralJet30_CentralJet25_PFMHT20
HLT_Ele22_CaloIdVT_TrkIdT_CentralJet30_CentralJet25
HLT_Ele25_CaloIdVT_CaloIsoT_TrkIdT_TrkIsoT_CentralJet30
HLT_Ele25_CaloIdVT_CaloIsoT_TrkIdT_TrkIsoT_CentralJet30_BTagIP
HLT_Ele25_CaloIdVT_CaloIsoT_TrkIdT_TrkIsoT_CentralJet30_CentralJet25_PFMHT20
HLT_Ele25_CaloIdVT_CaloIsoT_TrkIdT_TrkIsoT_CentralPFJet30
HLT_Ele25_CaloIdVT_CaloIsoT_TrkIdT_TrkIsoT_DiCentralJet30
HLT_Ele25_CaloIdVT_CaloIsoT_TrkIdT_TrkIsoT_DiCentralJet30_PFMHT25
HLT_Ele25_CaloIdVT_CaloIsoT_TrkIdT_TrkIsoT_DiCentralPFJet30
HLT_Ele25_CaloIdVT_CaloIsoT_TrkIdT_TrkIsoT_QuadCentralJet30
HLT_Ele25_CaloIdVT_CaloIsoT_TrkIdT_TrkIsoT_QuadCentralPFJet30
HLT_Ele25_CaloIdVT_CaloIsoT_TrkIdT_TrkIsoT_TriCentralJet30
HLT_Ele25_CaloIdVT_CaloIsoT_TrkIdT_TrkIsoT_TriCentralPFJet30
HLT_Ele25_CaloIdVT_TrkIdT_CentralDiJet30
HLT_Ele25_CaloIdVT_TrkIdT_CentralJet30
HLT_Ele25_CaloIdVT_TrkIdT_CentralJet30_BTagIP
HLT_Ele25_CaloIdVT_TrkIdT_CentralJet40_BTagIP
HLT_Ele25_CaloIdVT_TrkIdT_CentralPFJet30
HLT_Ele25_CaloIdVT_TrkIdT_CentralTriJet30
HLT_Ele25_CaloIdVT_TrkIdT_DiCentralJet30
HLT_Ele25_CaloIdVT_TrkIdT_DiCentralPFJet30
HLT_Ele25_CaloIdVT_TrkIdT_QuadCentralJet30
HLT_Ele25_CaloIdVT_TrkIdT_QuadCentralPFJet30
HLT_Ele25_CaloIdVT_TrkIdT_TriCentralJet30
HLT_Ele25_CaloIdVT_TrkIdT_TriCentralPFJet30
HLT_Ele27_CaloIdVT_CaloIsoT_TrkIdT_TrkIsoT_CentralJet30_CentralJet25
HLT_Ele27_CaloIdVT_CaloIsoT_TrkIdT_TrkIsoT_CentralJet30_CentralJet25_PFMHT20
HLT_Ele27_CaloIdVT_CaloIsoT_TrkIdT_TrkIsoT_Jet35_Jet25_Deta3_Jet20
HLT_Ele27_CaloIdVT_TrkIdT_CentralJet30_CentralJet25
HLT_Ele27_CaloIdVT_TrkIdT_DiCentralPFJet25
HLT_Ele27_CaloIdVT_TrkIdT_DiPFJet25_Deta3
HLT_Ele27_CaloIdVT_TrkIdT_Jet35_Jet25_Deta3_Jet20
HLT_Ele27_WP80_DiCentralPFJet25
HLT_Ele27_WP80_DiCentralPFJet25_PFMHT15
HLT_Ele27_WP80_DiPFJet25_Deta3
HLT_Ele30_CaloIdVT_CaloIsoT_TrkIdT_TrkIsoT_DiCentralJet30_PFMHT25
HLT_Ele30_CaloIdVT_CaloIsoT_TrkIdT_TrkIsoT_Jet35_Jet25_Deta3p5_Jet25
HLT_Ele32_WP80_DiCentralPFJet25_PFMHT25
HLT_Ele32_WP80_DiPFJet25_Deta3p5
HLT_Ele8_CaloIdT_TrkIdT_DiJet30
HLT_Ele8_CaloIdT_TrkIdT_QuadJet30
HLT_Ele8_CaloIdT_TrkIdT_TriJet30
HLT_HT200_DoubleEle5_CaloIdVL_MassJPsi
HLT_HT200_Ele5_CaloIdVL_TrkIdVL_CaloIsoVL_TrkIsoVL_PFMHT35
HLT_HT250_Ele5_CaloIdVL_TrkIdVL_CaloIsoVL_TrkIsoVL_PFMHT35
HLT_HT300_Ele5_CaloIdVL_CaloIsoVL_TrkIdVL_TrkIsoVL_PFMHT40
HLT_HT300_Ele5_CaloIdVL_TrkIdVL_CaloIsoVL_TrkIsoVL_PFMHT40
HLT_HT350_Ele30_CaloIdT_TrkIdT
HLT_HT350_Ele5_CaloIdVL_CaloIsoVL_TrkIdVL_TrkIsoVL_PFMHT45
HLT_HT350_Ele5_CaloIdVL_TrkIdVL_CaloIsoVL_TrkIsoVL_PFMHT45
HLT_HT400_Ele5_CaloIdVL_CaloIsoVL_TrkIdVL_TrkIsoVL_PFMHT50
HLT_HT400_Ele60_CaloIdT_TrkIdT
HLT_HT450_Ele60_CaloIdT_TrkIdT
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
File Indexes
{{$ctrlTbl.files = $ctrl.index_files.files; ""}}
{{$ctrlTbl.totalItems = $ctrl.index_files.total; ""}}
Filename
Size
Filename
Size
Files
{{$ctrlTbl.files = $ctrl.files.files; ""}}
{{$ctrlTbl.totalItems = $ctrl.files.total; ""}}
Filename
Size
Filename
Size
Disclaimer
The open data are released under the Creative Commons CC0 waiver. Neither 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.
