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

How were these data selected?

Events stored in this primary dataset were selected because of the presence of at least two high-energy electrons in the event.

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_DoubleEle10_CaloIdL_TrkIdVL_Ele10_CaloIdT_TrkIdVL
HLT_Ele15_Ele8_Ele5_CaloIdL_TrkIdVL
HLT_Ele17_CaloIdL_CaloIsoVL
HLT_Ele17_CaloIdT_CaloIsoVL_TrkIdVL_TrkIsoVL
HLT_Ele17_CaloIdT_CaloIsoVL_TrkIdVL_TrkIsoVL_Ele8_CaloIdT_CaloIsoVL_TrkIdVL_TrkIsoVL
HLT_Ele17_CaloIdT_CaloIsoVL_TrkIdVL_TrkIsoVL_Jet30
HLT_Ele17_CaloIdVT_CaloIsoVT_TrkIdT_TrkIsoVT_Ele8_Mass50
HLT_Ele20_CaloIdVT_CaloIsoVT_TrkIdT_TrkIsoVT_SC4_Mass50
HLT_Ele23_CaloIdT_CaloIsoVL_TrkIdVL_TrkIsoVL_HFT30
HLT_Ele27_CaloIdT_CaloIsoVL_TrkIdVL_TrkIsoVL_Ele15_CaloIdT_CaloIsoVL_trackless
HLT_Ele27_CaloIdT_CaloIsoVL_TrkIdVL_TrkIsoVL_HFT15
HLT_Ele32_CaloIdT_CaloIsoT_TrkIdT_TrkIsoT_SC17_Mass50
HLT_Ele5_SC5_Jpsi_Mass2to15
HLT_Ele8_CaloIdL_CaloIsoVL
HLT_Ele8_CaloIdT_CaloIsoVL_TrkIdVL_TrkIsoVL
HLT_Ele8_CaloIdT_CaloIsoVL_TrkIdVL_TrkIsoVL_Jet30
HLT_Ele8_CaloIdT_TrkIdVL
HLT_Ele8_CaloIdT_TrkIdVL_EG7
HLT_Ele8_CaloIdT_TrkIdVL_Jet30
HLT_Photon22_R9Id90_HE10_Iso40_EBOnly
HLT_Photon36_R9Id90_HE10_Iso40_EBOnly
HLT_Photon50_R9Id90_HE10_Iso40_EBOnly
HLT_Photon75_R9Id90_HE10_Iso40_EBOnly
HLT_Photon90_R9Id90_HE10_Iso40_EBOnly
HLT_TripleEle10_CaloIdL_TrkIdVL

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