PhotonHad primary dataset in AOD format from RunB of 2011 (/PhotonHad/Run2011B-12Oct2013-v1/AOD)
/PhotonHad/Run2011B-12Oct2013-v1/AOD, CMS collaboration
Cite as: CMS collaboration (2020). PhotonHad primary dataset in AOD format from RunB of 2011 (/PhotonHad/Run2011B-12Oct2013-v1/AOD). CERN Open Data Portal. DOI:10.7483/OPENDATA.CMS.IOOO.XUYZ
Dataset Collision CMS 7TeV pp CERN-LHC
Description
PhotonHad primary dataset in AOD format from RunB of 2011. Run period from run number 175833 to 180252.
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
10192398 events. 771 files. 2.1 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?
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 (identical to 2011 RunA):
Step: RECO
Release: CMSSW_5_3_7_patch5
Global tag: FT_R_53_V18::All
Configuration file for RECO step reco_2011_PhotonHad
HLT trigger paths
The possible HLT trigger paths in this dataset are:
HLT_Photon30_CaloIdVT_CentralJet20_BTagIP
HLT_Photon40_CaloIdL_R005_MR150
HLT_Photon40_CaloIdL_R014_MR150
HLT_Photon40_CaloIdL_R014_MR500
HLT_Photon40_CaloIdL_R017_MR500
HLT_Photon40_CaloIdL_R020_MR350
HLT_Photon40_CaloIdL_R023_MR350
HLT_Photon40_CaloIdL_R025_MR250
HLT_Photon40_CaloIdL_R029_MR250
HLT_Photon40_CaloIdL_R038_MR200
HLT_Photon40_CaloIdL_R042_MR200
HLT_Photon40_R005_MR150
HLT_Photon40_R014_MR450
HLT_Photon40_R020_MR300
HLT_Photon40_R025_MR200
HLT_Photon40_R038_MR150
HLT_Photon55_CaloIdL_R017_MR500
HLT_Photon55_CaloIdL_R023_MR350
HLT_Photon55_CaloIdL_R029_MR250
HLT_Photon55_CaloIdL_R042_MR200
HLT_Photon60_CaloIdL_HT200
HLT_Photon60_CaloIdL_HT300
HLT_Photon60_CaloIdL_MHT70
HLT_Photon70_CaloIdL_HT200
HLT_Photon70_CaloIdL_HT300
HLT_Photon70_CaloIdL_HT350
HLT_Photon70_CaloIdL_HT400
HLT_Photon70_CaloIdL_HT500
HLT_Photon70_CaloIdL_MHT110
HLT_Photon70_CaloIdL_MHT30
HLT_Photon70_CaloIdL_MHT50
HLT_Photon70_CaloIdL_MHT70
HLT_Photon70_CaloIdL_MHT90
HLT_Photon70_CaloIdXL_HT400
HLT_Photon70_CaloIdXL_HT500
HLT_Photon70_CaloIdXL_MHT100
HLT_Photon70_CaloIdXL_MHT90
HLT_Photon90EBOnly_CaloIdVL_IsoL_TriPFJet25
HLT_Photon90EBOnly_CaloIdVL_IsoL_TriPFJet30
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.
