HT primary dataset in AOD format from Run of 2012 (/HT/Run2012A-22Jan2013-v1/AOD)
/HT/Run2012A-22Jan2013-v1/AOD, CMS collaboration
Cite as: CMS collaboration (2022). HT primary dataset in AOD format from Run of 2012 (/HT/Run2012A-22Jan2013-v1/AOD). CERN Open Data Portal. DOI:10.7483/OPENDATA.CMS.T133.SAN2
Dataset Collision CMS 8TeV pp CERN-LHC
Description
HT primary dataset in AOD format from RunA of 2012. Run period from run number 190456 to 193621.
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
6644517 events. 523 files. 1.8 TiB in total.System details
FT53_V21A_AN6CMSSW_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?
Events stored in this primary dataset were selected because of the presence of a high scalar sum of the jet transverse momenta (HT).
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_2012A_HT
HLT trigger paths
The possible HLT trigger paths in this dataset are:
HLT_CleanPFHT300_Ele15_CaloIdT_CaloIsoVL_TrkIdT_TrkIsoVL_PFMET45
HLT_CleanPFHT300_Ele15_CaloIdT_CaloIsoVL_TrkIdT_TrkIsoVL_PFMET50
HLT_CleanPFHT300_Ele40_CaloIdVT_TrkIdT
HLT_CleanPFHT300_Ele60_CaloIdVT_TrkIdT
HLT_CleanPFHT350_Ele5_CaloIdT_CaloIsoVL_TrkIdT_TrkIsoVL_PFMET45
HLT_CleanPFHT350_Ele5_CaloIdT_CaloIsoVL_TrkIdT_TrkIsoVL_PFMET50
HLT_FatDiPFJetMass750_DR1p1_Deta1p5
HLT_HT200
HLT_HT200_AlphaT0p57
HLT_HT250
HLT_HT250_AlphaT0p55
HLT_HT250_AlphaT0p57
HLT_HT250_DoubleDisplacedPFJet60
HLT_HT250_DoubleDisplacedPFJet60_ChgFraction10
HLT_HT250_SingleDisplacedPFJet60
HLT_HT250_SingleDisplacedPFJet60_ChgFraction10
HLT_HT300
HLT_HT300_AlphaT0p53
HLT_HT300_AlphaT0p54
HLT_HT300_DoubleDisplacedPFJet60
HLT_HT300_DoubleDisplacedPFJet60_ChgFraction10
HLT_HT300_SingleDisplacedPFJet60
HLT_HT300_SingleDisplacedPFJet60_ChgFraction10
HLT_HT350
HLT_HT350_AlphaT0p52
HLT_HT350_AlphaT0p53
HLT_HT400
HLT_HT400_AlphaT0p51
HLT_HT400_AlphaT0p52
HLT_HT450
HLT_HT450_AlphaT0p51
HLT_HT500
HLT_HT550
HLT_HT650
HLT_HT750
HLT_PFHT350
HLT_PFHT350_PFMET100
HLT_PFHT400_PFMET100
HLT_PFHT650
HLT_PFHT650_DiCentralPFJet80_CenPFJet40
HLT_PFHT700
HLT_PFHT750
HLT_RsqMR40_Rsq0p04
HLT_RsqMR45_Rsq0p09
HLT_RsqMR55_Rsq0p09_MR150
HLT_RsqMR60_Rsq0p09_MR150
HLT_RsqMR65_Rsq0p09_MR150
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 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
Disclaimer
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.
