HighPtJet80 primary dataset in AOD format from RunE of 2015 (/HighPtJet80/Run2015E-PromptReco-v1/AOD)
/HighPtJet80/Run2015E-PromptReco-v1/AOD, CMS collaboration
Cite as: CMS collaboration (2023). HighPtJet80 primary dataset in AOD format from RunE of 2015 (/HighPtJet80/Run2015E-PromptReco-v1/AOD). CERN Open Data Portal. DOI:10.7483/OPENDATA.CMS.OJXD.AAZZ
Dataset Collision Heavy-ion physics CMS 5.02TeV pp CERN-LHC
Description
HighPtJet80 primary dataset in AOD format from RunE of 2015. Run period from run number 261445 to 262328.
These proton-proton data were taken at the same centre-of-mass energy and have a similar trigger menu to proton-Pb collision data from 2013.
The list of validated runs, which must be applied to all analyses, either with the full validation or for an analysis requiring only muons, can be found in
Dataset characteristics
28939464 events. 423 files. 1.4 TiB in total.System details
75X_dataRun2_v13CMSSW_7_5_8_patch3
Recommended container image for analyses is available in the following locations (see guide):
docker.io/cmsopendata/cmssw_7_5_8_patch3-slc6_amd64_gcc491:latestgitlab-registry.cern.ch/cms-cloud/cmssw-docker-opendata/cmssw_7_5_8_patch3-slc6_amd64_gcc491:latest
How were these data selected?
Events stored in this primary dataset were selected because of the presence jet with a pt above 80 GeV.
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 (the run number in the configuration file name indicates the first run it was applied to):
Step: RECO
Release: CMSSW_7_5_5_patch3
Global tag: 75X_dataRun2_Prompt_ppAt5TeV_v0
Configuration file for RECO step aod_Run2015E_HighPtJet80_261395
Data processing / RECO
This primary AOD dataset was processed from the RAW dataset by the following step (the run number in the configuration file name indicates the first run it was applied to):
Step: RECO
Release: CMSSW_7_5_6
Global tag: 75X_dataRun2_Prompt_ppAt5TeV_v1
Configuration file for RECO step aod_Run2015E_HighPtJet80_261544
Data processing / RECO
This primary AOD dataset was processed from the RAW dataset by the following step (the run number in the configuration file name indicates the first run it was applied to):
Step: RECO
Release: CMSSW_7_5_5_patch3
Global tag: 75X_dataRun2_Prompt_ppAt5TeV_v0
Configuration file for RECO step aod_Run2015E_HighPtJet80_261553
Data processing / RECO
This primary AOD dataset was processed from the RAW dataset by the following step (the run number in the configuration file name indicates the first run it was applied to):
Step: RECO
Release: CMSSW_7_5_5_patch4
Global tag: 75X_dataRun2_Prompt_ppAt5TeV_v0
Configuration file for RECO step aod_Run2015E_HighPtJet80_262021
HLT trigger paths
The possible HLT trigger paths in this dataset are:
HLT_AK4CaloJet80_Eta5p1
HLT_AK4CaloJet100_Eta5p1
HLT_AK4CaloJet110_Eta5p1
HLT_AK4CaloJet120_Eta5p1
HLT_AK4CaloJet150
HLT_AK4PFJet80_Eta5p1
HLT_AK4PFJet100_Eta5p1
HLT_AK4PFJet110_Eta5p1
HLT_AK4PFJet120_Eta5p1
HLT_AK4CaloJet80_Jet35_Eta1p1
HLT_AK4CaloJet80_Jet35_Eta0p7
HLT_AK4CaloJet100_Jet35_Eta1p1
HLT_AK4CaloJet100_Jet35_Eta0p7
HLT_AK4CaloJet80_45_45_Eta2p1
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:
The Data Quality Monitoring Software for the CMS experiment at the LHC: past, present and future
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.
