PAHighPt primary dataset in RECO format from the 5.02 TeV proton-Pb run of 2013 (/PAHighPt/HIRun2013-PromptReco-v1/RECO)

Name: /PAHighPt/HIRun2013-PromptReco-v1/RECO
Creator: CMS collaboration
Published: 2023

/PAHighPt/HIRun2013-PromptReco-v1/RECO, CMS collaboration

Cite as: CMS collaboration (2023). PAHighPt primary dataset in RECO format from the 5.02 TeV proton-Pb run of 2013 (/PAHighPt/HIRun2013-PromptReco-v1/RECO). CERN Open Data Portal. DOI:10.7483/OPENDATA.CMS.8EWL.W02X

Dataset Collision Heavy-ion physics CMS 5.02TeV pPb CERN-LHC

Description

PAHighPt primary dataset in RECO format from the 5.02 TeV proton-Pb run of 2013. Reprocessing for run numbers from 210498 to 211631.

For run numbers less than 210676, please use the reprocessed data in the related 28Sep2013-v1 dataset linked below.

During the 2013 proton-Pb data taking, the beam direction was reversed between runs 211256 and 211313.

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

Validated runs, full validation

Validated runs, muons only

Related datasets

The corresponding 28Sep2013-v1 dataset:

/PAHighPt/HIRun2013-28Sep2013-v1/RECO

Dataset characteristics

222789339 events. 15175 files. 94.2 TiB in total.

System details

Recommended global tag for analysis: GR_P_V43D::All
Recommended release for analysis: CMSSW_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:latest
gitlab-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 object or high track multiplicity.

Data taking / HLT
The collision data were assigned to different RAW datasets using the following HLT configuration.

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

How to install the CMS Virtual Machine

Getting Started with CMS 2013 and 2015 Heavy-Ion Open Data

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.