DoubleElectron primary dataset in AOD format from RunA of 2011 (/DoubleElectron/Run2011A-12Oct2013-v1/AOD)
/DoubleElectron/Run2011A-12Oct2013-v1/AOD, CMS collaboration
Cite as: CMS collaboration (2016). DoubleElectron primary dataset in AOD format from RunA of 2011 (/DoubleElectron/Run2011A-12Oct2013-v1/AOD). CERN Open Data Portal. DOI:10.7483/OPENDATA.CMS.MQXP.QNMB
Dataset Collision CMS 7TeV pp CERN-LHC
Description
DoubleElectron 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
49693737 events. 1697 files. 6.1 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 electrons 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_DoubleElectron
HLT trigger paths
The possible HLT trigger paths in this dataset are:
HLT_DoubleEle10_CaloIdL_TrkIdVL_Ele10
HLT_DoubleEle10_CaloIdL_TrkIdVL_Ele10_CaloIdT_TrkIdVL
HLT_DoubleEle45_CaloIdL
HLT_Ele17_CaloIdL_CaloIsoVL
HLT_Ele17_CaloIdL_CaloIsoVL_Ele15_HFL
HLT_Ele17_CaloIdL_CaloIsoVL_Ele15_HFT
HLT_Ele17_CaloIdL_CaloIsoVL_Ele8_CaloIdL_CaloIsoVL
HLT_Ele17_CaloIdT_CaloIsoVL_TrkIdVL_TrkIsoVL_Ele8_CaloIdT_CaloIsoVL_TrkIdVL_TrkIsoVL
HLT_Ele17_CaloIdT_TrkIdVL_CaloIsoVL_TrkIsoVL_Ele8_CaloIdT_TrkIdVL_CaloIsoVL_TrkIsoVL
HLT_Ele17_CaloIdVT_CaloIsoVT_TrkIdT_TrkIsoVT_Ele8_Mass30
HLT_Ele17_CaloIdVT_CaloIsoVT_TrkIdT_TrkIsoVT_SC8_Mass30
HLT_Ele22_CaloIdL_CaloIsoVL_Ele15_HFT
HLT_Ele32_CaloIdL_CaloIsoVL_SC17
HLT_Ele32_CaloIdT_CaloIsoT_TrkIdT_TrkIsoT_Ele17
HLT_Ele32_CaloIdT_CaloIsoT_TrkIdT_TrkIsoT_SC17
HLT_Ele8
HLT_Ele8_CaloIdL_CaloIsoVL
HLT_Ele8_CaloIdL_CaloIsoVL_Jet40
HLT_Ele8_CaloIdL_TrkIdVL
HLT_Ele8_CaloIdT_CaloIsoVL_TrkIdVL_TrkIsoVL
HLT_Ele8_CaloIdT_TrkIdVL_CaloIsoVL_TrkIsoVL
HLT_Photon20_CaloIdVT_IsoT_Ele8_CaloIdL_CaloIsoVL
HLT_TripleEle10_CaloIdL_TrkIdVL
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.
