/SingleElectron/Run2012B-v1/RAW, CMS collaboration
Cite as: CMS collaboration (2019). SingleElectron primary dataset sample in RAW format from RunB of 2012 (from /SingleElectron/Run2012B-v1/RAW). CERN Open Data Portal. DOI:10.7483/OPENDATA.CMS.64I6.R3K5
Dataset Collision CMS 8TeV pp CERN-LHC
A sample from SingleElectron primary dataset in RAW format from RunB of 2012. Run range [194117, 194199].
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
docker.io/cmsopendata/cmssw_5_3_32-slc6_amd64_gcc472:latest
gitlab-registry.cern.ch/cms-cloud/cmssw-docker-opendata/cmssw_5_3_32-slc6_amd64_gcc472:latest
Events stored in this primary dataset were selected because of the presence of at least one high-energy electron in the event, or at least one high-energy electron and one or more central jets.
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_Ele100_CaloIdVT_TrkIdT
HLT_Ele22_CaloIdL_CaloIsoVL
HLT_Ele24_WP80_CentralPFJet35_CentralPFJet25
HLT_Ele24_WP80_CentralPFJet35_CentralPFJet25_PFMET20
HLT_Ele24_WP80_PFJet30_PFJet25_Deta3
HLT_Ele24_WP80_PFJet30_PFJet25_Deta3_CentralPFJet30
HLT_Ele25_CaloIdVL_CaloIsoT_TrkIdVL_TrkIsoT_TriCentralPFNoPUJet30
HLT_Ele25_CaloIdVL_CaloIsoT_TrkIdVL_TrkIsoT_TriCentralPFNoPUJet30_30_20
HLT_Ele25_CaloIdVT_CaloIsoT_TrkIdT_TrkIsoT_CentralPFNoPUJet30
HLT_Ele25_CaloIdVT_CaloIsoT_TrkIdT_TrkIsoT_CentralPFNoPUJet30_BTagIPIter
HLT_Ele25_CaloIdVT_CaloIsoT_TrkIdT_TrkIsoT_TriCentralPFNoPUJet30_30_20
HLT_Ele25_CaloIdVT_CaloIsoVL_TrkIdVL_TrkIsoT_DiCentralPFNoPUJet30
HLT_Ele25_CaloIdVT_CaloIsoVL_TrkIdVL_TrkIsoT_TriCentralPFNoPUJet30
HLT_Ele25_CaloIdVT_CaloIsoVL_TrkIdVL_TrkIsoT_TriCentralPFNoPUJet45_35_25
HLT_Ele25_CaloIdVT_CaloIsoVL_TrkIdVL_TrkIsoT_TriCentralPFNoPUJet50_40_30
HLT_Ele25_CaloIdVT_TrkIdT_TriCentralPFNoPUJet30_30_20
HLT_Ele27_CaloIdL_CaloIsoVL_TrkIdVL_TrkIsoVL
HLT_Ele27_WP80
HLT_Ele27_WP80_CentralPFJet80
HLT_Ele27_WP80_PFMET_MT50
HLT_Ele27_WP80_WCandPt80
HLT_Ele30_CaloIdVT_TrkIdT
HLT_Ele32_CaloIdL_CaloIsoVL_TrkIdVL_TrkIsoVL
HLT_Ele32_WP80_CentralPFJet35_CentralPFJet25
HLT_Ele32_WP80_CentralPFJet35_CentralPFJet25_PFMET20
HLT_Ele32_WP80_PFJet30_PFJet25_Deta3
HLT_Ele32_WP80_PFJet30_PFJet25_Deta3_CentralPFJet30
HLT_Ele65_CaloIdVT_TrkIdT
HLT_Ele80_CaloIdVT_GsfTrkIdT
HLT_Ele80_CaloIdVT_TrkIdT
HLT_Ele90_CaloIdVT_GsfTrkIdT
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
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
The open data are released under the Creative Commons CC0 waiver. Neither the experiment(s) ( 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.