JetHT primary dataset sample in RAW format from RunB of 2012 (from /JetHT/Run2012B-v1/RAW)

Description

A sample from JetHT primary dataset in RAW format from RunB of 2012. Run range [194699,195112].

This dataset contains selected runs from 2012 RunB. The list of validated lumi sections, which must be applied to all analyses on events reconstructed from these data, 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); or at least one or two energetic, mostly central, jets; or high missing transverse energy.

Data taking / HLT
The collision data were assigned to different RAW datasets using the following HLT configuration.

HLT trigger paths
The possible HLT trigger paths in this dataset are:
HLT_DiPFJetAve320
HLT_DiPFJetAve400
HLT_FatDiPFJetMass750_DR1p1_Deta1p5
HLT_HT200
HLT_HT250
HLT_HT300
HLT_HT300_DoubleDisplacedPFJet60
HLT_HT300_DoubleDisplacedPFJet60_ChgFraction10
HLT_HT300_SingleDisplacedPFJet60
HLT_HT300_SingleDisplacedPFJet60_ChgFraction10
HLT_HT350
HLT_HT400
HLT_HT450
HLT_HT500
HLT_HT550
HLT_HT650
HLT_HT650_Track50_dEdx3p6
HLT_HT650_Track60_dEdx3p7
HLT_HT750
HLT_Jet370_NoJetID
HLT_MET80
HLT_MET80_Track50_dEdx3p6
HLT_MET80_Track60_dEdx3p7
HLT_PFHT350
HLT_PFHT650
HLT_PFHT650_DiCentralPFJet80_CenPFJet40
HLT_PFHT700
HLT_PFHT750
HLT_PFJet320
HLT_PFJet400
HLT_PFNoPUHT350
HLT_PFNoPUHT650
HLT_PFNoPUHT650_DiCentralPFNoPUJet80_CenPFNoPUJet40
HLT_PFNoPUHT700
HLT_PFNoPUHT750

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?

These data are in RAW format and not directly usable in analysis. The reconstructed data reprocessed from these RAW data are included in the data of this record. The reconstruction step can be repeated with the configuration file below and the resulting AOD can be compared with the original one using the code available in Validation code to plot basic physics objects from AOD

Example configuration file for reconstruction

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.