CMS measures the luminosity with different luminometers (luminosity detectors) and algorithms. The luminosity values presented here correspond to an early version of those obtained with the Hadron Forward calorimeter's Zero Counting algorithm (hfoc). However, as of 2020, an upgraded and more detailed version of the luminosity information is available (and recommended).
The integrated luminosity for validated runs and luminosity sections of the 2012 public data (RunB and RunC) is available in the tables 2012RunBlumi.txt and 2012RunClumi.txt. (The integrated luminosity for validated runs and luminosity sections of all 2012 p-p data taking is available in 2012lumi.txt.)
In your estimate for the integrated luminosity, check for which runs the trigger you have selected is active and sum the values for those runs. The uncertainty in the luminosity measurement of 2012 data should be considered as 2.6% (reference CMS PAS LUM-13-001).
If you are using prescaled triggers, you can find the trigger prescale factors as shown in the trigger example. The change of prescales (run, lumi section, index of prescales) is recorded in
Note that if there are orphan lumi sections listed at the bottom of the lumi files as in json but not in results, they can be safely ignored. These lumi sections have no events as they correspond to the very end of runs for which the stable beam flag was not disabled yet during acquisition.
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