SinglePhoton primary dataset in AOD format from Run of 2012 (/SinglePhoton/Run2012C-22Jan2013-v1/AOD)

Description

SinglePhoton primary dataset in AOD format from RunC of 2012. Run period from run number 198022 to 203742.

This dataset contains all runs from 2012 RunC. The list of validated runs, which must be applied to all analyses, can be found in

CMS list of validated runs Cert_190456-208686_8TeV_22Jan2013ReReco_Collisions12_JSON.txt

Dataset characteristics

System details

How were these data selected?

Events stored in this primary dataset were selected because of the presence of at least one, mostly energetic, photon with rather loose isolation conditions. The events might also have medium 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_5_3_7_patch5
Global tag: FT_R_53_V18::All
Configuration file for RECO step reco_2012C_SinglePhoton

HLT trigger paths
The possible HLT trigger paths in this dataset are:
HLT_DisplacedPhoton65EBOnly_CaloIdVL_IsoL_PFMET30
HLT_DisplacedPhoton65_CaloIdVL_IsoL_PFMET25
HLT_DoublePhoton5_IsoVL_CEP
HLT_L1DoubleEG3_FwdVeto
HLT_Photon135
HLT_Photon150
HLT_Photon160
HLT_Photon20_CaloIdVL
HLT_Photon20_CaloIdVL_IsoL
HLT_Photon300_NoHE
HLT_Photon30_CaloIdVL
HLT_Photon30_CaloIdVL_IsoL
HLT_Photon50_CaloIdVL
HLT_Photon50_CaloIdVL_IsoL
HLT_Photon75_CaloIdVL
HLT_Photon75_CaloIdVL_IsoL
HLT_Photon90_CaloIdVL
HLT_Photon90_CaloIdVL_IsoL

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

How to install the CMS Virtual Machine

Getting started with CMS open data

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.