SinglePhoton primary dataset in AOD format from RunD of 2015 (/SinglePhoton/Run2015D-16Dec2015-v1/AOD)
/SinglePhoton/Run2015D-16Dec2015-v1/AOD, CMS collaboration
Cite as: CMS collaboration (2021). SinglePhoton primary dataset in AOD format from RunD of 2015 (/SinglePhoton/Run2015D-16Dec2015-v1/AOD). CERN Open Data Portal. DOI:10.7483/OPENDATA.CMS.ARR1.NI0Y
Dataset Collision CMS 13TeV CERN-LHC
Description
SinglePhoton primary dataset in AOD format from RunD of 2015. Run period from run number 256630 to 260627.
The list of validated runs, which must be applied to all analyses, either with the full validation or for an analysis requiring only muons, can be found in:
Related datasets
The corresponding MINIAOD dataset:Dataset characteristics
35338156 events. 1394 files. 5.0 TB in total.System details
76X_dataRun2_16Dec2015_v0CMSSW_7_6_7
How were these data selected?
Events stored in this primary dataset were selected because of the presence of one energetic photon, or one photon and high missing transverse momentum.
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_7_6_3
Global tag: 76X_dataRun2_v15
Configuration file for RECO step reco_2015D_SinglePhoton
HLT trigger paths
The possible HLT trigger paths in this dataset are:
HLT_Photon120_R9Id90_HE10_Iso40_EBOnly_PFMET40
HLT_Photon120_R9Id90_HE10_Iso40_EBOnly_VBF
HLT_Photon120_R9Id90_HE10_IsoM
HLT_Photon120
HLT_Photon135_PFMET100_JetIdCleaned
HLT_Photon135_PFMET100
HLT_Photon165_HE10
HLT_Photon165_R9Id90_HE10_IsoM
HLT_Photon175
HLT_Photon22_R9Id90_HE10_Iso40_EBOnly_PFMET40
HLT_Photon22_R9Id90_HE10_Iso40_EBOnly_VBF
HLT_Photon22_R9Id90_HE10_IsoM
HLT_Photon22
HLT_Photon250_NoHE
HLT_Photon300_NoHE
HLT_Photon30_R9Id90_HE10_IsoM
HLT_Photon30
HLT_Photon36_R9Id90_HE10_Iso40_EBOnly_PFMET40
HLT_Photon36_R9Id90_HE10_Iso40_EBOnly_VBF
HLT_Photon36_R9Id90_HE10_IsoM
HLT_Photon36
HLT_Photon500
HLT_Photon50_R9Id90_HE10_Iso40_EBOnly_PFMET40
HLT_Photon50_R9Id90_HE10_Iso40_EBOnly_VBF
HLT_Photon50_R9Id90_HE10_IsoM
HLT_Photon50
HLT_Photon600
HLT_Photon75_R9Id90_HE10_Iso40_EBOnly_PFMET40
HLT_Photon75_R9Id90_HE10_Iso40_EBOnly_VBF
HLT_Photon75_R9Id90_HE10_IsoM
HLT_Photon75
HLT_Photon90_CaloIdL_PFHT500
HLT_Photon90_CaloIdL_PFHT600
HLT_Photon90_R9Id90_HE10_Iso40_EBOnly_PFMET40
HLT_Photon90_R9Id90_HE10_Iso40_EBOnly_VBF
HLT_Photon90_R9Id90_HE10_IsoM
HLT_Photon90
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:
The Data Quality Monitoring Software for the CMS experiment at the LHC: past, present and future
How can you use these data?
You can access these data through the CMS Open Data container or the CMS Virtual Machine. See the instructions for setting up one of the two alternative environments and getting started in
Running CMS analysis code using Docker
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.
