/Commissioning/Run2010B-Apr21ReReco-v1/AOD, CMS collaboration
Cite as: CMS collaboration (2014). Commissioning primary dataset in AOD format from RunB of 2010 (/Commissioning/Run2010B-Apr21ReReco-v1/AOD). CERN Open Data Portal. DOI:10.7483/OPENDATA.CMS.VTD5.V7Y3
Dataset Collision CMS 7TeV CERN-LHC
Commissioning primary dataset in AOD format from RunB of 2010
This dataset contains all runs from 2010 RunB. The list of validated runs, which must be applied to all analyses, can be found in
CMS list of validated runs Cert_136033-149442_7TeV_Apr21ReReco_Collisions10_JSON_v2.txt
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_4_2_1_patch1
Global tag: FT_R_42_V10A::All
The configuration file for RECO step can be generated with the cmsDriver command line script in the corresponding CMSSW release area:
cmsDriver.py reco -s RAW2DIGI,L1Reco,RECO --data --conditions FT_R_42_V10A::All --eventcontent AOD --no_exec --python reco_cmsdriver2010.py
HLT trigger paths
There are four categories of triggers in the Commissioning dataset:
~30% "almost" Minimum-bias-like trigger (some tagger requirements):
HLT_L1_BptxXOR_BscMinBiasOR
~10% multi-vertex triggers with or without energy threshold (biased):
HLT_MultiVertex6_v2
HLT_MultiVertex6
HLT_MultiVertex8_L1ETT60_v2
HLT_MultiVertex8_L1ETT60
~30% isolated track triggers with some L1 jet (e.g. for taus):
HLT_IsoTrackHB_v2
HLT_IsoTrackHB
HLT_IsoTrackHE_v3
HLT_IsoTrackHE_v2
HLT_IsoTrackHE
~20% technical "muon" (DT or CSC based) triggers:
HLT_Activity_CSC
HLT_Activity_DT
HLT_Activity_DT_Tuned
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
CC0 license
