/PAMinBiasUPC/HIRun2013-28Sep2013-v1/RECO, CMS collaboration
Cite as: CMS collaboration (2023). PAMinBiasUPC primary dataset in RECO format from the 5.02 TeV proton-Pb run of 2013 (/PAMinBiasUPC/HIRun2013-28Sep2013-v1/RECO). CERN Open Data Portal. DOI:10.7483/OPENDATA.CMS.I2YK.2QAX
Dataset Collision Heavy-ion physics CMS 5.02TeV pPb CERN-LHC
PAMinBiasUPC 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
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
Events stored in this primary dataset were selected because of the presence of signs of ultra-peripheral collisions or because they pass certain minimum-bias type selections.
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_PAL1SingleJet16
HLT_PAL1SingleJet36
HLT_PASingleForJet15
HLT_PASingleForJet25
HLT_PAL1DoubleMu0
HLT_PADimuon0_NoVertexing
HLT_PARomanPots_Tech52
HLT_PAL1Tech53_MB
HLT_PAL1Tech53_MB_SingleTrack
HLT_PAL1Tech54_ZeroBias
HLT_PAT1minbias_Tech55
HLT_PAL1Tech_HBHEHO_totalOR
HLT_PAMinBiasHF
HLT_PAMinBiasHF_OR
HLT_PAMinBiasBHC
HLT_PAMinBiasBHC_OR
HLT_PAMinBiasHfOrBHC
HLT_PABptxPlusNotBptxMinus
HLT_PABptxMinusNotBptxPlus
HLT_PAZeroBias
HLT_PAZeroBiasPixel_SingleTrack
HLT_PAHFOR_SingleTrack
HLT_PAZeroBiasPixel_DoubleTrack
HLT_PADoubleMu4_Acoplanarity03
HLT_PAExclDijet35_HFAND
HLT_PAL1DoubleEG3_FwdVeto
HLT_PAL1DoubleJet20_TotemDiffractive
HLT_PADoubleJet20_ForwardBackward
HLT_PAMu7_Ele7_CaloIdT_CaloIsoVL
HLT_PAUpcSingleEG5Pixel_TrackVeto
HLT_PAUpcSingleEG5Full_TrackVeto7
HLT_PAUpcSingleMuOpenPixel_TrackVeto
HLT_PAUpcSingleMuOpenFull_TrackVeto7
HLT_PAUpcSingleMuOpenTkMu_Onia
HLT_PARandom
HLT_PAL1Tech63_CASTORHaloMuon
HLT_PACastorEmNotHfCoincidencePm
HLT_PACastorEmTotemLowMultiplicity
HLT_PACastorEmNotHfSingleChannel
HLT_PAL1CastorTotalTotemLowMultiplicity
HLT_PAL1SingleMu20_TotemDiffractive
HLT_PAL1SingleJet52_TotemDiffractive
HLT_PAL1SingleEG20_TotemDiffractive
HLT_PAL1DoubleJetC36_TotemDiffractive
HLT_PAL1DoubleMu5_TotemDiffractive
HLT_PAL1DoubleEG5_TotemDiffractive
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
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
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.