PAMuon primary dataset in RECO format from the 5.02 TeV proton-Pb run of 2013 (/PAMuon/HIRun2013-28Sep2013-v1/RECO)
/PAMuon/HIRun2013-28Sep2013-v1/RECO, CMS collaboration
Cite as: CMS collaboration (2023). PAMuon primary dataset in RECO format from the 5.02 TeV proton-Pb run of 2013 (/PAMuon/HIRun2013-28Sep2013-v1/RECO). CERN Open Data Portal. DOI:10.7483/OPENDATA.CMS.B1W4.HP9Z
Dataset Collision Heavy-ion physics CMS 5.02TeV pPb CERN-LHC
Description
PAMuon primary dataset in RECO format from the 5.02 TeV proton-Pb run of 2013. Reprocessing for run numbers from 210498 to 210658.
For run numbers greater than or equal to 210676, please use the related PromptReco-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
Related datasets
The corresponding PromptReco-v1 dataset:Dataset characteristics
15445691 events. 1636 files. 5.0 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 muon.
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_PAL1DoubleMu0_HighQ
HLT_PAL1DoubleMuOpen
HLT_PAL2DoubleMu3
HLT_PAMu3
HLT_PAMu7
HLT_PAMu12
HLT_PABTagMu_Jet20_Mu4
HLT_PAMu3PFJet20
HLT_PAMu3PFJet40
HLT_PAMu7PFJet20
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.
