MultiJet primary dataset in AOD format from RunA of 2011 (/MultiJet/Run2011A-12Oct2013-v1/AOD)
/MultiJet/Run2011A-12Oct2013-v1/AOD, CMS collaboration
Cite as: CMS collaboration (2016). MultiJet primary dataset in AOD format from RunA of 2011 (/MultiJet/Run2011A-12Oct2013-v1/AOD). CERN Open Data Portal. DOI:10.7483/OPENDATA.CMS.8N95.GCTN
Dataset Collision CMS 7TeV pp CERN-LHC
Description
MultiJet primary dataset in AOD format from RunA of 2011. Run period from run number 160404 to 173692.
The list of validated runs, which must be applied to all analyses, can be found in
CMS list of validated runs Cert_160404-180252_7TeV_ReRecoNov08_Collisions11_JSON.txt
Dataset characteristics
55664572 events. 3737 files. 8.1 TiB in total.System details
FT_53_LV5_AN1CMSSW_5_3_32
Recommended container image for analyses is available in the following locations (see guide):
docker.io/cmsopendata/cmssw_5_3_32-slc6_amd64_gcc472:latestgitlab-registry.cern.ch/cms-cloud/cmssw-docker-opendata/cmssw_5_3_32-slc6_amd64_gcc472:latest
How were these data selected?
Events stored in this primary dataset were selected because of the presence two or more high-energy jets, with or without a b-quark-tag requirement 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_12_patch1
Global tag: FT_R_53_LV5::All
Configuration file for RECO step reco_2011_MultiJet
HLT trigger paths
The possible HLT trigger paths in this dataset are:
HLT_60Jet10
HLT_70Jet10
HLT_70Jet13
HLT_CentralJet46_BTagIP3D_CentralJet38_BTagIP3D
HLT_CentralJet46_CentralJet38_CentralJet20_DiBTagIP3D
HLT_CentralJet46_CentralJet38_DiBTagIP3D
HLT_CentralJet60_CentralJet53_DiBTagIP3D
HLT_DiCentralJet36_BTagIP3DLoose
HLT_DoubleJet30_ForwardBackward
HLT_DoubleJet60_ForwardBackward
HLT_DoubleJet70_ForwardBackward
HLT_DoubleJet80_ForwardBackward
HLT_EightJet120
HLT_EightJet35
HLT_EightJet35_L1FastJet
HLT_EightJet40
HLT_EightJet40_L1FastJet
HLT_ExclDiJet60_HFAND
HLT_ExclDiJet60_HFOR
HLT_L1DoubleJet36Central
HLT_L1ETM30
HLT_L1MultiJet
HLT_QuadJet40
HLT_QuadJet40_IsoPFTau40
HLT_QuadJet45_DiJet40
HLT_QuadJet45_IsoPFTau45
HLT_QuadJet50_BTagIP
HLT_QuadJet50_DiJet40
HLT_QuadJet50_DiJet40_L1FastJet
HLT_QuadJet50_IsoPFTau50
HLT_QuadJet50_Jet40
HLT_QuadJet50_Jet40_Jet30
HLT_QuadJet60
HLT_QuadJet70
HLT_QuadJet80
HLT_QuadJet80_L1FastJet
HLT_QuadJet90
HLT_SixJet45
HLT_SixJet45_L1FastJet
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
Disclaimer
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.
