/HT/Run2011B-12Oct2013-v1/AOD, CMS collaboration
Cite as: CMS collaboration (2020). HT primary dataset in AOD format from RunB of 2011 (/HT/Run2011B-12Oct2013-v1/AOD). CERN Open Data Portal. DOI:10.7483/OPENDATA.CMS.8RRH.4MCC
Dataset Collision CMS 7TeV pp CERN-LHC
HT 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
docker.io/cmsopendata/cmssw_5_3_32-slc6_amd64_gcc472:latest
gitlab-registry.cern.ch/cms-cloud/cmssw-docker-opendata/cmssw_5_3_32-slc6_amd64_gcc472:latest
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_HT
HLT trigger paths
The possible HLT trigger paths in this dataset are:
HLT_DiJet100_PT100
HLT_DiJet130_PT130
HLT_DiJet160_PT160
HLT_DiJet70_PT70
HLT_FatJetMass300_DR1p1_Deta2p0_CentralJet30_BTagIP
HLT_FatJetMass350_DR1p1_Deta2p0_CentralJet30_BTagIP
HLT_FatJetMass750_DR1p1_Deta2p0
HLT_FatJetMass850_DR1p1_Deta2p0
HLT_HT150
HLT_HT150_AlphaT0p60
HLT_HT150_AlphaT0p70
HLT_HT160
HLT_HT200
HLT_HT2000
HLT_HT200_AlphaT0p53
HLT_HT200_AlphaT0p55
HLT_HT200_AlphaT0p60
HLT_HT200_AlphaT0p65
HLT_HT240
HLT_HT250
HLT_HT250_AlphaT0p53
HLT_HT250_AlphaT0p54
HLT_HT250_AlphaT0p55
HLT_HT250_AlphaT0p58
HLT_HT250_AlphaT0p60
HLT_HT250_AlphaT0p62
HLT_HT250_AlphaT0p65
HLT_HT250_DoubleDisplacedJet60
HLT_HT250_DoubleDisplacedJet60_PromptTrack
HLT_HT250_MHT100
HLT_HT250_MHT60
HLT_HT250_MHT70
HLT_HT250_MHT80
HLT_HT250_MHT90
HLT_HT260
HLT_HT260_MHT60
HLT_HT300
HLT_HT300_AlphaT0p52
HLT_HT300_AlphaT0p53
HLT_HT300_AlphaT0p54
HLT_HT300_AlphaT0p55
HLT_HT300_AlphaT0p60
HLT_HT300_CentralJet30_BTagIP
HLT_HT300_CentralJet30_BTagIP_PFMHT55
HLT_HT300_CentralJet30_BTagIP_PFMHT65
HLT_HT300_CentralJet30_BTagIP_PFMHT75
HLT_HT300_MHT75
HLT_HT300_MHT80
HLT_HT300_MHT90
HLT_HT300_PFMHT55
HLT_HT300_PFMHT65
HLT_HT350
HLT_HT350_AlphaT0p51
HLT_HT350_AlphaT0p52
HLT_HT350_AlphaT0p53
HLT_HT350_L1FastJet
HLT_HT350_L1FastJet_MHT100
HLT_HT350_L1FastJet_MHT110
HLT_HT350_MHT100
HLT_HT350_MHT110
HLT_HT350_MHT70
HLT_HT350_MHT80
HLT_HT350_MHT90
HLT_HT360
HLT_HT400
HLT_HT400_AlphaT0p51
HLT_HT400_AlphaT0p52
HLT_HT400_L1FastJet
HLT_HT400_L1FastJet_MHT100
HLT_HT400_L1FastJet_MHT90
HLT_HT400_MHT100
HLT_HT400_MHT80
HLT_HT400_MHT90
HLT_HT440
HLT_HT450
HLT_HT450_AlphaT0p51
HLT_HT450_AlphaT0p52
HLT_HT500
HLT_HT500_JetPt60_DPhi2p94
HLT_HT520
HLT_HT550
HLT_HT550_JetPt60_DPhi2p94
HLT_HT600
HLT_HT600_JetPt60_DPhi2p94
HLT_HT650
HLT_HT700
HLT_HT750
HLT_HT750_L1FastJet
HLT_MR100
HLT_Meff440
HLT_Meff520
HLT_Meff640
HLT_PFHT350_PFMHT100
HLT_PFHT350_PFMHT90
HLT_PFHT400_PFMHT80
HLT_PFHT400_PFMHT90
HLT_PFHT650
HLT_R014_MR150
HLT_R014_MR150_CentralJet40_BTagIP
HLT_R014_MR450_CentralJet40_BTagIP
HLT_R017_MR450_CentralJet40_BTagIP
HLT_R017_MR500_CentralJet40_BTagIP
HLT_R020_MR150
HLT_R020_MR350_CentralJet40_BTagIP
HLT_R020_MR500
HLT_R020_MR550
HLT_R023_MR350_CentralJet40_BTagIP
HLT_R023_MR400_CentralJet40_BTagIP
HLT_R023_MR550
HLT_R025_MR150
HLT_R025_MR250_CentralJet40_BTagIP
HLT_R025_MR400
HLT_R025_MR450
HLT_R029_MR250_CentralJet40_BTagIP
HLT_R029_MR300_CentralJet40_BTagIP
HLT_R029_MR450
HLT_R032
HLT_R032_MR100
HLT_R033_MR200_CentralJet40_BTagIP
HLT_R033_MR300
HLT_R033_MR350
HLT_R035_MR100
HLT_R036_MR200_CentralJet40_BTagIP
HLT_R036_MR350
HLT_R038_MR200
HLT_R038_MR250
HLT_R038_MR300
HLT_R042_MR250
HLT_RMR65
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
You can access these data through the CMS Virtual Machine. See the instructions for setting up the Virtual Machine and getting started in
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.