/ppForward/Run2015E-PromptReco-v1/AOD, CMS collaboration
Cite as: CMS collaboration (2023). ppForward primary dataset in AOD format from RunE of 2015 (/ppForward/Run2015E-PromptReco-v1/AOD). CERN Open Data Portal. DOI:10.7483/OPENDATA.CMS.OWZN.Z9DV
Dataset Collision Heavy-ion physics CMS 5.02TeV pp CERN-LHC
ppForward 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
docker.io/cmsopendata/cmssw_7_5_8_patch3-slc6_amd64_gcc491:latest
gitlab-registry.cern.ch/cms-cloud/cmssw-docker-opendata/cmssw_7_5_8_patch3-slc6_amd64_gcc491:latest
Events stored in this primary dataset were selected because of the presence of signs of ultra-peripheral collisions or objects in forward regions.
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_ppForward_261380
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_ppForward_262021
HLT trigger paths
The possible HLT trigger paths in this dataset are:
HLT_HIUPCL1DoubleMuOpenNotHF2
HLT_HIUPCDoubleMuNotHF2Pixel_SingleTrack
HLT_HIUPCL1MuOpen_NotMinimumBiasHF2_AND
HLT_HIUPCMuOpen_NotMinimumBiasHF2_ANDPixel_SingleTrack
HLT_HIUPCL1NotMinimumBiasHF2_AND
HLT_HIUPCNotMinimumBiasHF2_ANDPixel_SingleTrack
HLT_HIUPCL1ZdcOR_BptxAND
HLT_HIUPCZdcOR_BptxANDPixel_SingleTrack
HLT_HIUPCL1ZdcXOR_BptxAND
HLT_HIUPCZdcXOR_BptxANDPixel_SingleTrack
HLT_HIUPCL1NotZdcOR_BptxAND
HLT_HIUPCNotZdcOR_BptxANDPixel_SingleTrack
HLT_HIL1CastorMediumJet
HLT_HICastorMediumJetPixel_SingleTrack
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
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.