CMS list of validated runs for 13TeV proton-proton collision data taken in 2016, only valid muons

Description

This file describes which luminosity sections in which runs are considered good and should be processed, for analyses requiring only valid muons.

This list covers 13TeV proton-proton collision data taken in 2016. Run2016G is between run numbers 278820 and 280385. Run2016H is between run numbers 280919 and 284044.

How was the validation done?

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 to use?

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_271036-284044_13TeV_Legacy2016_Collisions16_JSON_MuonPhys.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.