PPJet primary dataset in RECO format from RunA of 2013 (/PPJet/Run2013A-PromptReco-v1/RECO)
/PPJet/Run2013A-PromptReco-v1/RECO, CMS collaboration
Cite as: CMS collaboration (2023). PPJet primary dataset in RECO format from RunA of 2013 (/PPJet/Run2013A-PromptReco-v1/RECO). CERN Open Data Portal. DOI:10.7483/OPENDATA.CMS.8XGC.QNOG
Dataset Collision Heavy-ion physics CMS 2.76TeV pp CERN-LHC
Description
PPJet primary dataset in RECO format from RunA of 2013. Run period from run number 211739 to 211831.
This dataset is related to the skim linked below.
These proton-proton data were taken at the same centre-of-mass energy and have a similar trigger menu to Pb-Pb collision data from 2010/2011.
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
Related datasets
The corresponding HighPtPP-15Feb2013-v1 dataset:Dataset characteristics
33716079 events. 1337 files. 5.9 TiB in total.System details
GR_P_V43D::AllCMSSW_5_3_20
Recommended container image for analyses is available in the following locations (see guide):
docker.io/cmsopendata/cmssw_5_3_20-slc6_amd64_gcc472:latestgitlab-registry.cern.ch/cms-cloud/cmssw-docker-opendata/cmssw_5_3_20-slc6_amd64_gcc472:latest
How were these data selected?
Events stored in this primary dataset were selected because of the presence of one or more high-pt jet or high track multiplicity.
Data taking / HLT
The collision data were assigned to different RAW datasets using the following HLT configuration.
HLT trigger paths
The possible HLT trigger paths in this dataset are:
HLT_PAJet20_NoJetID
HLT_PAJet40_NoJetID
HLT_PAJet60_NoJetID
HLT_PAJet80_NoJetID
HLT_PAJet100_NoJetID
HLT_PAJet120_NoJetID
HLT_PAForJet20Eta2
HLT_PAForJet40Eta2
HLT_PAForJet60Eta2
HLT_PAForJet80Eta2
HLT_PAForJet100Eta2
HLT_PAForJet20Eta3
HLT_PAForJet40Eta3
HLT_PAForJet60Eta3
HLT_PAForJet80Eta3
HLT_PAForJet100Eta3
HLT_PATripleJet20_20_20
HLT_PATripleJet40_20_20
HLT_PATripleJet60_20_20
HLT_PATripleJet80_20_20
HLT_PATripleJet100_20_20
HLT_PAJet40ETM30
HLT_PAJet60ETM30
HLT_PAPixelTracks_Multiplicity100
HLT_PAPixelTracks_Multiplicity130
HLT_PAPixelTracks_Multiplicity160
HLT_PAPixelTracks_Multiplicity190
HLT_PAPixelTracks_Multiplicity220
HLT_PAPixelTrackMultiplicity100_FullTrack12
HLT_PAPixelTrackMultiplicity130_FullTrack12
HLT_PAPixelTrackMultiplicity160_FullTrack12
HLT_PAPixelTrackMultiplicity100_L2DoubleMu3
HLT_PAPixelTrackMultiplicity140_Jet80_NoJetID
HLT_PATech35
HLT_PATech35_HFSumET100
HLT_PAHFSumET100
HLT_PAHFSumET140
HLT_PAHFSumET170
HLT_PAHFSumET210
HLT_PAFullTrack12
HLT_PAFullTrack20
HLT_PAFullTrack30
HLT_PAFullTrack50
HLT_PPPixelTracks_Multiplicity55
HLT_PPPixelTracks_Multiplicity70
HLT_PPPixelTracks_Multiplicity85
HLT_PPPixelTrackMultiplicity55_FullTrack12
HLT_PPPixelTrackMultiplicity70_FullTrack12
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
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.
