Introduction

Overview

Teaching: 30 min
Exercises: 10 min

Questions

• What is luminosity?

• What is the difference between instantaneous and integrated luminosity?

• Why is knowing the luminosity important?

• How is luminosity measured?

Objectives

• Know what luminosity is and why it is important

• Know how luminosity is measured

References

You can find several papers with much more technical detail and several articles with additional (less formal) information in the References.

Instantanous Luminosity

In the context of the LHC, instantaneous luminosity, \(\mathcal{L}_{inst}\), corresponds to the number of “interactions” produced when “bunches” of protons are crossed. Roughly speaking, it corresponds to the “real-time rate of interactions/events/collisions”. During Run 2 of the LHC, groups of ~100 billion protons were crossed as often as 40 million times per second yielding an overall average of 34 interactions per crossing within the CMS detector.

More precisely, instantaneous luminosity quantifies the ability of particle accelerator to produce a certain number of interactions. It represents a proportionality factor between rate of interactions \(\left( \frac{dN}{dt} \right)\) and the cross-section (\(\sigma\)):

[\frac{d\mathrm{N}}{dt} = \mathcal{L}_{inst} \cdot \sigma]

Thus, instantaneous luminosity is usually expressed in the cgs units of \(\mathrm{cm^{-2} s^{-1}}\). Units of “barns” are also used frequently, where \(1 \mathrm{b} = \mathrm{10^{-24} cm^{2}}\), thanks to two Purdue University physicists working on the Manhattan Project in 1942. As an example, let’s very approximately calculate the total Higgs Boson production rate at CMS:

1.1 Total Higgs boson production rate at CMS

• During May 2018, the LHC routinely delivered instantanous luminosities of \(\approx 2 \times 10^{34} \mathrm{cm^{-2} s^{-1}}\) \(\left( 0.02 \mathrm{pb^{-1} s^{-1}} \right)\) at CMS
• The total production cross section of Standard Model Higgs boson at \(\sqrt{s} = 13 \mathrm{TeV}\) can be slightly underestimated as \(\approx 50 \mathrm{pb}\) (see table 11.2 in the 2022 PDG)

What is the rate of Higgs production at CMS? Vote for the corect answer in the short lumi exercise Mattermost channel.

\[\frac{d\mathrm{N_{Higgs}}}{dt} = \mathcal{L}_{inst}^{\mathrm{peak}} \cdot \sigma_{\mathrm{Higgs}}^{\mathrm{total}}\]

Integrated Luminosity

Instantaneous luminosity is aggregated over a certain period of time to obtain integrated luminosity:

[\mathcal{L}{int} = \int \mathcal{L}{inst} dt]

It is commonly used to quantify the “amount of data” delivered by the accelerator or recorded by the experiment. Units of inverse femtobars \(\mathrm{fb^{-1}}\) are frequently used in CMS.

To illustrate, we can very roughly estimate the total number of Higgs bosons produced during 24 hours at CMS:

1.2 Total Higgs bosons produced at CMS during 24 hours

• During Nov 2017, CMS recorded \(\approx 600 \mathrm{pb^{-1}}\) during a 24-hour period of stable beams
• The total production cross section of Standard Model Higgs boson at \(\sqrt{s} = 13 \mathrm{TeV}\) can be slightly underestimated as \(\approx 50 \mathrm{pb}\) (see table 11.2 in the 2022 PDG)

How many Higgs bosons can be produced at CMS during 24 hours? Vote for the corect answer in the short lumi exercise Mattermost channel.

\[\mathrm{N_{Higgs}} = \mathcal{L}_{int}^{\mathrm{24hr}} \cdot \sigma_{\mathrm{Higgs}}^{\mathrm{total}}\]

Importance of Luminosity

Along with the center of mass energy, instantanous luminosity is the most significant performance parameter for any particle accelerator. Real-time monitoring of instantaneous luminosity is critical for the accelerator to carry out beam tuning and collision optimization. It is also essential for the CMS trigger system in order to scale or throttle the data throughput.

Measurement of integrated luminosity is also incredibly crucial since its limited precision represents a contribution to the systematic uncertainty for most physics searches and measurements. The uncertainty in the integrated luminosity is often the dominant systematic uncertainty in EWK cross-section measurements. We can emphasize the impact of the integrated luminosity uncertainty by considering a relatively rare process:

1.3 Total Higgs bosons decaying to muon pairs at CMS during 2018

• During 2018, CMS recorded around \(\approx 60 \mathrm{fb^{-1}}\) of good-quality data with 2.5% uncertainty (see the CMS Lumi POG “quick summary table”)
• The total production cross section of Standard Model Higgs boson at \(\sqrt{s} = 13 \mathrm{TeV}\) can be slightly underestimated as \(\approx 50 \mathrm{pb}\) (see Table 11.2 in the 2022 PDG)
• The branching ratio for \(H \rightarrow \mu \mu\) can be approximated as \(\approx 2 \times 10^{-4}\) (see Table 11.3 in the 2022 PDG)

What is the minimum and maximum expected event yield given the uncertainty in integrated luminosity? Vote for the corect answer in the short lumi exercise Mattermost channel.

\[\mathrm{N}_{H \rightarrow \mu \mu}^{2018} = \left( \mathcal{L}_{int}^{2018} \pm \delta \right) \cdot \sigma_{\mathrm{Higgs}}^{\mathrm{total}} \cdot \mathcal{B}_{H \rightarrow \mu \mu}\]

Luminosity Measurement

CMS has two dedicated systems for measuring luminosity, both located \(z \approx \pm 1.8 \mathrm{m}\) from the interaction point and radius \(\approx 6 \mathrm{cm}\):

Fast Beam Condition Monitor (BCM1F)

C-shaped PCBs arranged into two rings at each side of CMS with double-pad silicon sensors

Real-time histogramming with 6.25 ns per-bin facilitates measurement of machine-induced background

Pixel Luminosity Telescope (PLT)

16 “telescopes” (8 per side of CMS) with three hybrid silicon pixel sensors per telescope

Fast cluster-counting signal (40 MHz) in addition to full pixel info readout

In addition, several sub-detectors are used for luminosity measurement, among them:

PCC (Pixel Cluster Counting)

Counts the mean number of pixel clusters in the most “stable” modules of the silicon pixel detector

Hadronic Forward (HF)

Steel absorber with quartz fibers to detect Cherenkov light histogrammed as function of bunch crossing

Which detector is more photogenic?

This is the most important poll!

https://indico.cern.ch/event/1239959/surveys/4059

Luminosity Calibration

The precise determination of integrated luminosity is particularly challenging at hadron colliders, in part due to the theoretical predictions (e.g. uncertainties in the parton distribution functions and precision of parton-level cross-section calculations) being generally less precise compared to \(e^{+} e^{−}\) colliders. A sub-detector can measure “relative” luminosity on an arbitrary scale based on the reported event rate. The determination of “absolute” luminosity involes re-scaling the measured event rate by a proportionality factor, \(\sigma_{vis}\), derived from the properties of the colliding beams. This scaling factor may be thought of as a way to account for the sub-detector’s particular acceptance and response.

At the LHC, the primary technique to determine the absolute luminosity scale is the van der Meer (vdM) scan method, based on dedicated beam-separation scans. The size and shape of the interaction region is measured by recording the relative interaction rates as a function of the transverse beam separation. After adopting several assumptions (e.g. transverse and longitudinal beam densities are Gaussian, density functions are factorizable into \(x\)- and \(y\)-dependent components, etc.), the visible cross-section can be expressed as

[\sigma_{vis} = \mu_{vis}^{\mathrm{max}} \frac{2 \pi \Sigma_{x} \Sigma_{y}}{n_{1} n_{2}}]

where \(\mu_{vis}^{\mathrm{max}}\) is the peak visible interaction rate, \(n_{1}\) and \(n_{2}\) are the numbers of particles in each of the two bunches, and \(\Sigma_{x}\) and \(\Sigma_{y}\) correspond to the effective beam overlap widths in each scan plane.

Corrections to vdM scan data

Several systematic effects can affect the measurement of \(\sigma_{vis}\). These represent a significant contribution to the final uncertainty in the measurement of integrated luminosity.

Orbit drift corrections

Potential bias from beam positions monitors (DOROS, Arc BPM) at the \(\mu \mathrm{m}\) scale

Beam-beam effects

EM interaction between colliding bunches (deflection & shape)

Length scale calibration

Possible differences in the absolute scale between the nominal beam separation (produced by the steering of the LHC magnets) and the actual separation

Transverse factorizability

Non-factorizability of \(x\) and \(y\) components measured and corrected with the beam-image method

Beam-imaging method: the distributions of reconstructed vertices during beam-imaging scans are used to obtain an image of the transverse bunch profiles integrated over the scanning direction

Other corrections

“Spurious” charges present outside the nominally filled bunches (ghosts👻 in empty bunch slots and out-of-time satellite🛰 charges adjacent to the main bunch)

Dominant uncertainties in the absolute luminosity scale (\(\sigma_{vis}\))

• beam position monitoring
• transverse factorizability
• beam-beam effects

Rate corrections under physics running conditions

Several corrections must be applied to luminometer rates to ensure that the final luminosity values are accurate.

Out-of-time pileup corrections

Most detectors have out-of-time contributions that do not arise from the main colliding bunch (spillover of electronic signals and real additional response from material activation)

Efficiency corrections

Radiation damage can affect the detector response by reducing efficiency, increasing noise, or both

Nonlinear response

Over- or under-counting as a function of instantaneous luminosity

Detector stability and linearity

Determined from comparisons between luminometers

Key Points

• Luminosity is a measure of how many collisions are delivered to and recorded by the detector.

• Instantaneous luminosity is usually expressed as the number of collisions per square centimeter per second.

• Integrated luminosity is the integral of instantaneous luminosity over time and is a measurement of data size. It is usually expressed in units of inverse cross section.

• Knowing the luminosity is important to determining and measuring accelerator and detector performance and operation. It is also an essential component for measuring cross sections and for setting limits on beyond-SM processes.

• Measurement of luminosity is done with several systems in the detector.

Using brilcalc

Overview

Teaching: 10 min
Exercises: 20 min

Questions

• What tools are available to query the delivered and recorded luminosity?

Objectives

• Learn how to use brilcalc to query luminosity information.

Important

This exercise is meant to be run from lxplus.cern.ch.

Please follow the setup instructions before getting started.

brilcalc

brilcalc is the official tool for querying CMS luminosity information. It currently has three subcommands: lumi, beam, and trg. The official brilcalc documentation can be found here: https://cmslumi.web.cern.ch/.

brilcalc lumi

This lesson will focus on the brilcalc lumi subcommand, which can query the delivered and recorded CMS luminosity. Let’s try a few examples:

Glossary

If you are unfamiliar with “fills”, “runs”, “lumisections”, etc., you can find their definitions in the Glossary

Run brilcalc for fill 6666

brilcalc lumi -f 6666

Output

#Data tag : 19v3 , Norm tag: onlineresult
+-------------+-------------------+------+------+---------------------+---------------------+
| run:fill    | time              | nls  | ncms | delivered(/ub)      | recorded(/ub)       |
+-------------+-------------------+------+------+---------------------+---------------------+
| 316108:6666 | 05/10/18 20:54:10 | 20   | 7    | 405.423497145       | 107.184508306       |
| 316109:6666 | 05/10/18 21:01:36 | 54   | 45   | 10039605.429211318  | 3542879.861587470   |
| 316110:6666 | 05/10/18 21:22:27 | 217  | 210  | 84147739.992830962  | 79017103.630366772  |
| 316111:6666 | 05/10/18 22:46:45 | 59   | 48   | 20773266.833208650  | 14573457.533706700  |
| 316112:6666 | 05/10/18 23:09:31 | 19   | 10   | 6499507.705982770   | 228.928666450       |
| 316113:6666 | 05/10/18 23:16:41 | 68   | 64   | 22720996.040678266  | 19663097.809963763  |
| 316114:6666 | 05/10/18 23:42:59 | 1647 | 1647 | 371661976.624663532 | 362106384.976257861 |
+-------------+-------------------+------+------+---------------------+---------------------+
#Summary:
+-------+------+------+------+---------------------+---------------------+
| nfill | nrun | nls  | ncms | totdelivered(/ub)   | totrecorded(/ub)    |
+-------+------+------+------+---------------------+---------------------+
| 1     | 7    | 2084 | 2031 | 515843498.050072670 | 478903259.925057292 |
+-------+------+------+------+---------------------+---------------------+

Run brilcalc for run 325000

brilcalc lumi -r 325000

Output

#Data tag : 19v3 , Norm tag: onlineresult
+-------------+-------------------+-----+------+---------------------+--------------------+
| run:fill    | time              | nls | ncms | delivered(/ub)      | recorded(/ub)      |
+-------------+-------------------+-----+------+---------------------+--------------------+
| 325000:7324 | 10/21/18 08:03:56 | 376 | 371  | 100027429.112490401 | 95257794.416809484 |
+-------------+-------------------+-----+------+---------------------+--------------------+
#Summary:
+-------+------+-----+------+---------------------+--------------------+
| nfill | nrun | nls | ncms | totdelivered(/ub)   | totrecorded(/ub)   |
+-------+------+-----+------+---------------------+--------------------+
| 1     | 1    | 376 | 371  | 100027429.112490401 | 95257794.416809484 |
+-------+------+-----+------+---------------------+--------------------+

brilcalc options

brilcalc provides a generous number of command line options. You can get a summary by running brilcalc lumi --help. But the official documentation is much more comprehensive.

Example brilcalc common command options

Selections

period to query

• -f <fill>
• -r <run>
• --begin <fill>
• --begin <run>
• --begin <MM/DD/YY HH:MM:SS> (UTC)
• --end <fill>
• --end <run>
• --end <MM/DD/YY HH:MM:SS> (UTC)

Filters

conditions to query

• -b <beam status> [“STABLE BEAMS”, “FLAT TOP”, “ADJUST”, “SQUEEZE”]
• --amodetag <machine mode> [“PROTPHYS”, “IONPHYS”, “PAPHYS”]
• --beamenergy <beam energy> (in GeV)

Output/Display

output file, table/csv/html output format, utc/local time, etc.

• -o <output file> (csv format)
• --output-style <output format> [“tab”, “csv”, “html”] (ignored if -o is provided)
• -n <scalefactor> (scale output by 1/scalefactor)
• --cerntime (display times in CERN local time)
• --tssec (display times as UNIX timestamps)

Database connection

connect to a database, such as a web cache

• -c <connection> [“offline”, “online”, “onlinew”, “dev”]

Example brilcalc lumi options

--byls

Show luminosity and average pileup by lumi section

-u <unit>

Show luminosity in the specified unit and scale the output value accordingly

[“/kb”, “/b”, “/mb”, “/ub”, “/nb”, “/pb”, “/fb”, “/ab”]

[“1e21/cm2”, “1e24/cm2”, “1e27/cm2”, “1e30/cm2”, “1e33/cm2”, “1e36/cm2”, “1e39/cm2”, “1e42/cm2”]

--type <luminometer>

Show results from the selected luminometer

[“hfoc”, “hfet”, “bcm1f”, “bcm1fsi”, “bcm1futca”, “pltzero”, “pltslink”, “dt”, “pxl”, “ramses”, “radmon”]

brilcalc --output-style

The stdout (display output) of brilcalc can be specified with the --output-style flag. Note that this in a “common” or “global” option, meaning that it is also available for the brilcalc beam and brilcalc trg subcommands. Let’s reproduce the above output in csv format:

brilcalc lumi -r 325000 --output-style csv

Output

#Data tag : 19v3 , Norm tag: None
#run:fill,time,nls,ncms,delivered(/ub),recorded(/ub)
325000:7324,10/21/18 08:03:56,376,371,100027429.112490401,95257794.416809484
#Summary:
#nfill,nrun,nls,ncms,totdelivered(/ub),totrecorded(/ub)
#1,1,376,371,100027429.112490401,95257794.416809484

2.1 Query luminosity info for fill corresponding to run 325000

Using brilcalc, determine the fill that run 325000 corresponds to. What is the total recorded luminosity for this fill in inverse picobarns? Vote for the corect answer in the short lumi exercise Mattermost channel.

Key Points

• brilcalc is a command-line tool provided by the CMS BRIL group for querying luminosity information.

Normtags and Data Certification

Overview

Teaching: 10 min
Exercises: 20 min

Questions

• What is a normtag?

• What is data certification?

Objectives

• Learn what is a normtag and how to use it

• Learn about data certification and how it relates to physics analyses

Important

This exercise is meant to be run from lxplus.cern.ch.

Please follow the setup instructions before getting started.

Normtags

A normtag is a file that defines the official luminosity calibrations and detectors to use for a given period. The normtag files are maintained by the Lumi POG and periodically updated as the calibrations are improved. It is important to always use the latest normtag in order to get the best results.

Important

Never run brilcalc without a --normtag argument unless you know exactly what you are doing.
Running brilcalc without --normtag will give you the online luminosity, which can change significantly by improvements in calibration. It is neither accurate, nor precise, nor stable.

The Run 2 physics normtag is /cvmfs/cms-bril.cern.ch/cms-lumi-pog/Normtags/normtag_PHYSICS.json. Always use this normtag for pp runs. This is the only normtag which can be used for physics analyses. It covers all of Run 2 for which there is a final approved number for physics (which includes all pp running and some special runs).

3.1 Query fill 6666 using the physics normtag

Using the physics normtag, what is the recorded luminosity in picobarns for fill 6666? Vote for the corect answer in the short lumi exercise Mattermost channel.

Data Certification

Note

This section has some overlap with Exercise 14 from the third Pre-Exercise Set

Data collected by CMS is certified on a luminosity-section basis to determine the subset of data of good quality to be included in physics analyses. Data certification is carried out by taking into account both the operational health of the sub-detectors and scrutiny of the reconstructed physics objects by DPG and POG experts. The outcome of the certification process is regularly updated as more data gets collected, and for each new version of the data processing, by the DQM-DataCertification. One of the main deliverables of this process are JSON files listing runs and lumisection which are good for physics analysis.

3.2 Query processedLumis.json to determine the recorded luminosity for your crab job datset

Refer to your submitted crab job as part of the third set of the Pre-Exercises. Recall that you had to transfer the resulting processedLumis.json file to lxplus.

Using the physics normtag, what is the recorded luminosity in inverse femtobarns for your crab job datset? Please post the correct answer in the short lumi exercise Mattermost channel.

Key Points

• Make sure to use a normtag when querying brilcalc for your analysis

• Data collected by CMS needs to be evaluated and a subset is certified as good quality data to be used for physics analysis