/MultiJet/Run2012A-22Jan2013-v1/AOD, CMS collaboration
Cite as: CMS collaboration (2022). MultiJet primary dataset in AOD format from Run of 2012 (/MultiJet/Run2012A-22Jan2013-v1/AOD). CERN Open Data Portal. DOI:10.7483/OPENDATA.CMS.WING.7QKV
Dataset Collision CMS 8TeV pp CERN-LHC
MultiJet primary dataset in AOD format from RunA of 2012. Run period from run number 190456 to 193621.
The list of validated runs, which must be applied to all analyses, 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 several high-energy jet in the event.
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_5_3_7_patch5
Global tag: FT_R_53_V18::All
Configuration file for RECO step reco_2012A_MultiJet
HLT trigger paths
The possible HLT trigger paths in this dataset are:
HLT_DiJet40Eta2p6_BTagIP3D
HLT_DiJet40Eta2p6_BTagIP3DFastPV
HLT_DiJet80Eta2p6_BTagIP3DFastPVLoose
HLT_DiJet80Eta2p6_BTagIP3DLoose
HLT_DiJet80_DiJet60_DiJet20
HLT_DoubleJet20_ForwardBackward
HLT_EightJet30_eta3p0
HLT_EightJet35
HLT_EightJet35_eta3p0
HLT_EightJet40
HLT_ExclDiJet35_HFAND
HLT_ExclDiJet35_HFOR
HLT_ExclDiJet80_HFAND
HLT_Jet160Eta2p4_Jet120Eta2p4_DiBTagIP3DFastPVLoose
HLT_Jet160Eta2p4_Jet120Eta2p4_DiBTagIP3DLoose
HLT_Jet60Eta1p7_Jet53Eta1p7_DiBTagIP3D
HLT_Jet60Eta1p7_Jet53Eta1p7_DiBTagIP3DFastPV
HLT_Jet80Eta1p7_Jet70Eta1p7_DiBTagIP3D
HLT_Jet80Eta1p7_Jet70Eta1p7_DiBTagIP3DFastPV
HLT_L1DoubleJet36Central
HLT_QuadJet50
HLT_QuadJet60_DiJet20
HLT_QuadJet70
HLT_QuadJet75_55_35_20_BTagIP_VBF
HLT_QuadJet75_55_38_20_BTagIP_VBF
HLT_QuadJet80
HLT_QuadJet90
HLT_QuadPFJet75_55_35_20_BTagCSV_VBF
HLT_QuadPFJet75_55_38_20_BTagCSV_VBF
HLT_SixJet35
HLT_SixJet45
HLT_SixJet50
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 Open Data container or the CMS Virtual Machine. See the instructions for setting up one of the two alternative environments and getting started in
Running CMS analysis code using Docker
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.