/SinglePhoton/Run2016H-UL2016_MiniAODv2_NanoAODv9-v1/NANOAOD, CMS Collaboration
Cite as: CMS Collaboration (2024). SinglePhoton primary dataset in NANOAOD format from RunH of 2016 (/SinglePhoton/Run2016H-UL2016_MiniAODv2_NanoAODv9-v1/NANOAOD). CERN Open Data Portal. DOI:10.7483/OPENDATA.CMS.0PQP.OQ96
Data recorded in 2016 and published in 2024Dataset Collision CMS 13TeV pp CERN-LHC
SinglePhoton primary dataset in NANOAOD format from RunH of 2016. Run period from run number 281613 to 284044.
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:
NANOAOD datasets are in the ROOT tree format and their analysis does not require the use of CMSSW or CMS open data environments. They can be analysed with common ROOT and Python tools.
gitlab-registry.cern.ch/cms-cloud/root-vncgitlab-registry.cern.ch/cms-cloud/python-vncEvents 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
This NANOAOD dataset was processed from the RAW dataset by the following steps:
Step NANO
Release: CMSSW_10_6_26
Global tag: 106X_dataRun2_v35
Configuration file for NANO step ReReco-Run2016H-SinglePhoton-UL2016_MiniAODv2_NanoAODv9
Output dataset: /SinglePhoton/Run2016H-UL2016_MiniAODv2_NanoAODv9-v1/NANOAOD
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
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
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
You can access these data through XRootD protocol or direct download, and they can be analysed with common ROOT and Python tools. See the instructions for getting started in
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.