JetMon primary dataset in AOD format from Run of 2012 (/JetMon/Run2012B-22Jan2013-v1/AOD)
/JetMon/Run2012B-22Jan2013-v1/AOD, CMS collaboration
Cite as: CMS collaboration (2017). JetMon primary dataset in AOD format from Run of 2012 (/JetMon/Run2012B-22Jan2013-v1/AOD). CERN Open Data Portal. DOI:10.7483/OPENDATA.CMS.L01D.5QY8
Dataset Collision CMS 8TeV CERN-LHC
Description
JetMon primary dataset in AOD format from RunB of 2012. Run period from run number 193833 to 196531.
This dataset contains all runs from 2012 RunB. 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
10143710 events. 818 files. 3.1 TB in total.System details
FT53_V21A_AN6CMSSW_5_3_32
How were these data selected?
Events stored in this primary dataset were selected because of the presence of at least one 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_2012B_JetMon
HLT trigger paths
The possible HLT trigger paths in this dataset are:
HLT_DiPFJetAve140
HLT_DiPFJetAve200
HLT_DiPFJetAve260
HLT_DiPFJetAve40
HLT_DiPFJetAve80
HLT_PASingleForJet15
HLT_PASingleForJet25
HLT_PFJet140
HLT_PFJet200
HLT_PFJet260
HLT_PFJet40
HLT_PFJet80
HLT_SingleForJet15
HLT_SingleForJet25
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
File Indexes
{{$ctrlTbl.files = $ctrl.index_files.files; ""}}
{{$ctrlTbl.totalItems = $ctrl.index_files.total; ""}}
Filename
Size
Filename
Size
Files
{{$ctrlTbl.files = $ctrl.files.files; ""}}
{{$ctrlTbl.totalItems = $ctrl.files.total; ""}}
Filename
Size
Filename
Size
Disclaimer
The open data are released under the Creative Commons CC0 waiver. Neither 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.
