MinimumBias primary dataset in AOD format from RunB of 2010 (/MinimumBias/Run2010B-Apr21ReReco-v1/AOD)

How were these data selected?

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 MinimumBias dataset:

~60% Minimum-bias-like triggers (some tagger requirements or random triggers):
HLT_L1_BPTX_MinusOnly
HLT_L1_BPTX_PlusOnly
HLT_L1_BPTX
HLT_L1Tech_BSC_HighMultiplicity
HLT_ZeroBias
HLT_Random

~10% large track multiplicity triggers (three subcategories: >75, 85, 100 tracks) for "ridge" studies:
HLT_PixelTracks_Multiplicity100
HLT_PixelTracks_Multiplicity85
HLT_PixelTracks_Multiplicity70

~28% triggers for exotic stopped High mass Stable Charged Particles:
HLT_StoppedHSCP35_v3
HLT_StoppedHSCP20_v3
HLT_StoppedHSCP_v2
HLT_StoppedHSCP

~2%, a technical "muon" (RPC based) trigger:
HLT_L1Tech_RPC_TTU_RBst1_collisions

All possible HLT trigger paths in this dataset are:
HLT_BackwardBSC
HLT_DoublePhoton5_eeRes_L1R
HLT_EgammaSuperClusterOnly_L1R
HLT_ForwardBSC
HLT_HFThreshold10
HLT_HFThreshold3
HLT_HighMult40
HLT_HighMultiplicityBSC
HLT_IsoTrackHB
HLT_IsoTrackHB_8E29
HLT_IsoTrackHE
HLT_IsoTrackHE_8E29
HLT_L1SingleEG1
HLT_L1SingleEG1_NoBPTX
HLT_L1SingleEG20_NoBPTX
HLT_L1SingleEG2_NoBPTX
HLT_L1SingleEG5_NoBPTX
HLT_L1Tech_BSC_HighMultiplicity
HLT_L1Tech_BSC_halo_forPhysicsBackground
HLT_L1Tech_BSC_minBias
HLT_L1Tech_BSC_minBias_OR
HLT_L1Tech_HCAL_HF
HLT_L1Tech_HCAL_HF_coincidence_PM
HLT_L1Tech_RPC_TTU_RBst1_collisions
HLT_L1_BPTX
HLT_L1_BPTX_MinusOnly
HLT_L1_BPTX_PlusOnly
HLT_L1_BSC
HLT_L1_BscMinBiasOR_BeamGas
HLT_L1_BscMinBiasOR_BptxPlusORMinus
HLT_L1_BscMinBiasOR_BptxPlusORMinus_NoBPTX
HLT_L1_HFtech
HLT_MinBias
HLT_MinBiasBSC
HLT_MinBiasBSC_NoBPTX
HLT_MinBiasBSC_OR
HLT_MinBiasEcal
HLT_MinBiasHcal
HLT_MinBiasPixel_DoubleIsoTrack5
HLT_MinBiasPixel_DoubleTrack
HLT_MinBiasPixel_SingleTrack
HLT_MultiVertex6
HLT_MultiVertex8_L1ETT60
HLT_PixelTracks_Multiplicity100
HLT_PixelTracks_Multiplicity40
HLT_PixelTracks_Multiplicity70
HLT_PixelTracks_Multiplicity85
HLT_SplashBSC
HLT_StoppedHSCP
HLT_StoppedHSCP20
HLT_StoppedHSCP35
HLT_StoppedHSCP_8E29
HLT_ZeroBias
HLT_ZeroBiasPixel_SingleTrack

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