/EG/Run2010A-Apr21ReReco-v1/AOD, CMS collaboration
Cite as: CMS collaboration (2019). EG primary dataset in AOD format from RunA of 2010 (/EG/Run2010A-Apr21ReReco-v1/AOD). CERN Open Data Portal. DOI:10.7483/OPENDATA.CMS.RCVF.FG9L
Dataset Collision CMS 7TeV pp CERN-LHC
EG primary dataset in AOD format from RunA of 2010
The list of validated runs, which must be applied to all analyses, can be found in
CMS list of validated runs Cert_136033-149442_7TeV_Apr21ReReco_Collisions10_JSON_v2.txt
docker.io/cmsopendata/cmssw_4_2_8-slc5_amd64_gcc434:latest
gitlab-registry.cern.ch/cms-cloud/cmssw-docker-opendata/cmssw_4_2_8-slc5_amd64_gcc434:latest
Events stored in this primary dataset were selected because of presence of at least one high-energy electron or photon 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_4_2_1_patch1
Global tag: FT_R_42_V10A::All
The configuration file for RECO step can be generated with the cmsDriver command line script in the corresponding CMSSW release area:
cmsDriver.py reco -s RAW2DIGI,L1Reco,RECO --data --conditions FT_R_42_V10A::All --eventcontent AOD --no_exec --python reco_cmsdriver2010.py
HLT trigger paths
The possible HLT trigger paths in this dataset are:
HLT_DoubleEle10_SW_L1R
HLT_DoubleEle4_SW_eeRes_L1R
HLT_DoubleEle5_SW_L1R
HLT_DoublePhoton15_L1R
HLT_DoublePhoton20_L1R
HLT_DoublePhoton4_Jpsi_L1R
HLT_DoublePhoton4_Upsilon_L1R
HLT_DoublePhoton4_eeRes_L1R
HLT_DoublePhoton5_CEP_L1R
HLT_DoublePhoton5_Jpsi_L1R
HLT_DoublePhoton5_Upsilon_L1R
HLT_Ele10_LW_EleId_L1R
HLT_Ele10_LW_L1R
HLT_Ele10_SW_EleId_L1R
HLT_Ele15_SC10_LW_L1R
HLT_Ele15_SW_CaloEleId_L1R
HLT_Ele15_SW_EleId_L1R
HLT_Ele15_SW_L1R
HLT_Ele20_LW_L1R
HLT_Ele20_SW_L1R
HLT_Ele25_SW_L1R
HLT_Photon10_L1R
HLT_Photon15_L1R
HLT_Photon15_LooseEcalIso_Cleaned_L1R
HLT_Photon15_LooseEcalIso_L1R
HLT_Photon15_TrackIso_Cleaned_L1R
HLT_Photon15_TrackIso_L1R
HLT_Photon20_Cleaned_L1R
HLT_Photon20_L1R
HLT_Photon25_Cleaned_L1R
HLT_Photon30_Cleaned_L1R
HLT_Photon30_L1R
HLT_Photon30_L1R_8E29
HLT_Photon50_Cleaned_L1R
HLT_Photon50_L1R
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
You can access these data through the CMS Virtual Machine. See the instructions for setting up the Virtual Machine and getting started in
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.