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

Description

HTMHTParked primary dataset in AOD format from RunB of 2012. Run period from run number 193833 to 196531.

This dataset contains all runs from 2012 RunB. 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 a high scalar sum of the jet transverse momenta (HT) and high missing transverse momentum from jets; or high scalar sum of the jet transverse momenta and high missing transverse momentum; or tight hyperbolic cut on razor variables, like R2 and MR, defined in terms of the momentum of two megajets in the event.

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_2012B_HTMHTParked

HLT trigger paths
The possible HLT trigger paths in this dataset are:
HLT_HT200_AlphaT0p57
HLT_HT250_AlphaT0p55
HLT_HT250_AlphaT0p57
HLT_HT300_AlphaT0p53
HLT_HT300_AlphaT0p54
HLT_HT350_AlphaT0p52
HLT_HT350_AlphaT0p53
HLT_HT400_AlphaT0p51
HLT_HT400_AlphaT0p52
HLT_HT450_AlphaT0p51
HLT_PFHT350_PFMET100
HLT_PFHT400_PFMET100
HLT_PFNoPUHT350_PFMET100
HLT_PFNoPUHT400_PFMET100
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 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.