BJetPlusX primary dataset in AOD format from Run of 2012 (/BJetPlusX/Run2012C-22Jan2013-v1/AOD)
/BJetPlusX/Run2012C-22Jan2013-v1/AOD, CMS collaboration
Cite as: CMS collaboration (2017). BJetPlusX primary dataset in AOD format from Run of 2012 (/BJetPlusX/Run2012C-22Jan2013-v1/AOD). CERN Open Data Portal. DOI:10.7483/OPENDATA.CMS.QGLB.GWGH
Dataset Collision CMS 8TeV pp CERN-LHC
Description
BJetPlusX primary dataset in AOD format from RunC of 2012. Run period from run number 198022 to 203742.
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
Dataset characteristics
36498856 events. 3091 files. 10.7 TiB in total.System details
FT53_V21A_AN6CMSSW_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 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_7_patch5
Global tag: FT_R_53_V18::All
Configuration file for RECO step reco_2012C_BJetPlusX
HLT trigger paths
The possible HLT trigger paths in this dataset are:
HLT_DiJet40Eta2p6_BTagIP3DFastPV
HLT_DiJet80Eta2p6_BTagIP3DFastPVLoose
HLT_DiPFJet80_DiPFJet30_BTagCSVd07d05
HLT_DiPFJet80_DiPFJet30_BTagCSVd07d05d03
HLT_DiPFJet80_DiPFJet30_BTagCSVd07d05d03_PFDiJetPt120
HLT_DiPFJet80_DiPFJet30_BTagCSVd07d05d05
HLT_Jet160Eta2p4_Jet120Eta2p4_DiBTagIP3DFastPVLoose
HLT_Jet60Eta1p7_Jet53Eta1p7_DiBTagIP3DFastPV
HLT_Jet80Eta1p7_Jet70Eta1p7_DiBTagIP3DFastPV
HLT_L1DoubleJet36Central
HLT_QuadJet75_55_35_20_BTagIP_VBF
HLT_QuadJet75_55_35_20_VBF
HLT_QuadJet75_55_38_20_BTagIP_VBF
HLT_QuadPFJet78_61_44_31_BTagCSV_VBF
HLT_QuadPFJet78_61_44_31_VBF
HLT_QuadPFJet82_65_48_35_BTagCSV_VBF
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 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
Disclaimer
These open data are released under the Creative Commons Zero v1.0 Universal license.
Neither the experiment(s) ( CMS ) nor CERN endorse any works, scientific or otherwise, produced using these data.
This release has a unique DOI that you are requested to cite in any applications or publications.
