CMS list of validated runs Cert_210498-211631_HI_PromptReco_Collisions13_JSON_v2.txt, CMS collaboration
Environment Validation Heavy-ion physics CMS 5.02TeV pPb CERN-LHC
This file describes which luminosity sections in which runs are considered good and should be processed.
This list covers 5.02TeV proton-Pb heavy-ion collision data taken in 2013. HIRun2013 is between run numbers 210498 and 211631.
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
Add the following lines in the configuration file for a cmsRun job:
import FWCore.ParameterSet.Config as cms
import FWCore.PythonUtilities.LumiList as LumiList
goodJSON = 'Cert_210498-211631_HI_PromptReco_Collisions13_JSON_v2.txt'
myLumis = LumiList.LumiList(filename = goodJSON).getCMSSWString().split(',')
Add the file path if needed in the file name.
Add the following statements after the process.source
input file definition:
process.source.lumisToProcess = cms.untracked.VLuminosityBlockRange()
process.source.lumisToProcess.extend(myLumis)
Note that the two last statements must be placed after the process.source
statement defining the input files.
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.