SingleElectron primary dataset in AOD format from RunA of 2011 (/SingleElectron/Run2011A-12Oct2013-v1/AOD)
/SingleElectron/Run2011A-12Oct2013-v1/AOD, CMS collaboration
Cite as: CMS collaboration (2016). SingleElectron primary dataset in AOD format from RunA of 2011 (/SingleElectron/Run2011A-12Oct2013-v1/AOD). CERN Open Data Portal. DOI:10.7483/OPENDATA.CMS.P87Z.TXTV
Dataset Collision CMS 7TeV pp CERN-LHC
Description
SingleElectron 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
41709195 events. 1542 files. 5.2 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 high-energy electron 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_SingleElectron
HLT trigger paths
The possible HLT trigger paths in this dataset are:
HLT_Ele100_CaloIdVL_CaloIsoVL_TrkIdVL_TrkIsoVL
HLT_Ele100_CaloIdVT_TrkIdT
HLT_Ele17_CaloIdT_TrkIdVL_CaloIsoVL_TrkIsoVL_Ele8_CaloIdT_TrkIdVL_CaloIsoVL_TrkIsoVL
HLT_Ele25_CaloIdL_CaloIsoVL_TrkIdVL_TrkIsoVL
HLT_Ele25_WP80_PFMT40
HLT_Ele27_CaloIdL_CaloIsoVL_TrkIdVL_TrkIsoVL
HLT_Ele27_CaloIdVT_CaloIsoT_TrkIdT_TrkIsoT
HLT_Ele27_WP70_PFMT40_PFMHT20
HLT_Ele27_WP80
HLT_Ele27_WP80_PFMT50
HLT_Ele32_CaloIdL_CaloIsoVL_TrkIdVL_TrkIsoVL
HLT_Ele32_CaloIdVL_CaloIsoVL_TrkIdVL_TrkIsoVL
HLT_Ele32_CaloIdVT_CaloIsoT_TrkIdT_TrkIsoT
HLT_Ele32_WP70
HLT_Ele32_WP70_PFMT50
HLT_Ele42_CaloIdVL_CaloIsoVL_TrkIdVL_TrkIsoVL
HLT_Ele42_CaloIdVT_CaloIsoT_TrkIdT_TrkIsoT
HLT_Ele45_CaloIdVT_TrkIdT
HLT_Ele52_CaloIdVT_TrkIdT
HLT_Ele65_CaloIdVT_TrkIdT
HLT_Ele80_CaloIdVT_TrkIdT
HLT_Ele90_NoSpikeFilter
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.
