• Help
    Discussion forum
    Search tips
  • About
    CERN Open Data
    ALICE
    ATLAS
    CMS
    DELPHI
    JADE
    LHCb
    OPERA
    TOTEM
    Glossary

Important notice: opendata-qa.cern.ch is a quality-assurance server. Please use it for testing purposes only. The content may be erased from time to time. Please use opendata.cern.ch for production.

CMS list of validated runs for primary datasets of 2012 data taking

CMS list of validated runs Cert_190456-208686_8TeV_22Jan2013ReReco_Collisions12_JSON.txt, CMS Collaboration

Cite as: CMS Collaboration (2017). CMS list of validated runs for primary datasets of 2012 data taking. CERN Open Data Portal. DOI:10.7483/OPENDATA.CMS.C00V.SE32

Environment Validation CMS CERN-LHC


Description

This file describes which luminosity sections in which runs are considered good and should be processed.

The list covers all p-p data taking in 2012. RunA is between run numbers 190456 -193621, RunB between run numbers 193833 - 196531, RunC between run numbers 198022 - 203742, and RunD between run numbers 203777 - 208686.

Characteristics

1 files. 35.8 KiB in total.

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:

CMS data quality monitoring: Systems and experiences

The CMS Data Quality Monitoring software experience and future improvements

The CMS data quality monitoring software: experience and future prospects

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_190456-208686_8TeV_22Jan2013ReReco_Collisions12_JSON.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.


      

Disclaimer

These open data are released under the Creative Commons Zero v1.0 Universal license.

Logo CC0-1.0

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.

ALICE experiment
ATLAS experiment
CMS experiment
DELPHI experiment
JADE experiment
LHCb experiment
OPERA experiment
PHENIX experiment
TOTEM experiment
© CERN, 2014–2025 ·
Terms of Use ·
Privacy Policy ·
Help ·
GitHub ·
Twitter ·
Email
Powered by Invenio
Open Data Portal v0.3.0
CERN