style rules tweaks

Author: jmhogan

docs/analysis/lumi.md

@@ -5,8 +5,8 @@
 
 In collider physics, discovery potential can be summarized with two pieces of information:
 
- * center-of-mass collision energy, $\sqrt{s}$, that drives the range of produced particle masses, and
- * luminosity, $\mathcal{L}$, that drives the size of the accumulated dataset.
+ - center-of-mass collision energy, $\sqrt{s}$, that drives the range of produced particle masses, and
+ - luminosity, $\mathcal{L}$, that drives the size of the accumulated dataset.
 
 ## Calculating luminosity
 
@@ -24,20 +24,20 @@ $\mathcal{L}_{\mathrm{int.}} = N/\sigma.$
 
 Cross section is measured in "barns", a unit of area relevant for nuclear-scale processes. The most literal meaning of the word cross section would describe cutting a (spherical?) atomic nucleus in half through the middle, exposing a circular flat surface. As targets for projectiles in nuclear reactions, most atomic nuclei "look" fairly circular, and the circles would have areas on the order of 10-100 square femtometers. A "barn" is exactly 100 square femtometers, or $1 \times 10^{-28}$ square meters. Luminosity is therefore measured in the even stranger unit of inverse barns!
 
-Typical cross sections for particle physics interactions are much smaller than nuclear physics interactions, ranging from millibarns down to femtobarns. The integrated luminosities required to discover these interactions grows as the cross section shrinks. 
+Typical cross sections for particle physics interactions are much smaller than nuclear physics interactions, ranging from millibarns down to femtobarns. The integrated luminosities required to discover these interactions grows as the cross section shrinks.
 
 #### CMS Luminometers
 
 CMS has several subdetectors that serve as "luminometers":
 
- * Pixels: pixel tracking detector, which covers $|\eta| < 2.5$
- * HF: forward hadron calorimeter, which covers $3 < |\eta| < 5.2$
- * PLT: pixel luminosity telescope, an array of 16 "telescopes" with pixel sensors in planes facing the interaction point. 
- * BCM1F: the fast beam conditions monitor, a system of diamond sensors on the PLT apparatus.
+ - Pixels: pixel tracking detector, which covers $|\eta| < 2.5$
+ - HF: forward hadron calorimeter, which covers $3 < |\eta| < 5.2$
+ - PLT: pixel luminosity telescope, an array of 16 "telescopes" with pixel sensors in planes facing the interaction point.
+ - BCM1F: the fast beam conditions monitor, a system of diamond sensors on the PLT apparatus.
 
-![](../images/luminometers.PNG)
+![Image of CMS luminometer positions.](../images/luminometers.PNG)
 
-The pixel detector contributes two measurements that are used for luminosity calculations: the number of charge clusters observed, and the number of vertices found with more than 10 tracks. The number of clusters can be used to compute the cross section for producing "visible particles". It is vanishingly unlikely that particles overlap each other in the pixel detector, so the average number of clusters in the pixel detector tracks directly with the number of simultaneous collisions in CMS. The visible cross section is the slope, or ratio, of this relationship. 
+The pixel detector contributes two measurements that are used for luminosity calculations: the number of charge clusters observed, and the number of vertices found with more than 10 tracks. The number of clusters can be used to compute the cross section for producing "visible particles". It is vanishingly unlikely that particles overlap each other in the pixel detector, so the average number of clusters in the pixel detector tracks directly with the number of simultaneous collisions in CMS. The visible cross section is the slope, or ratio, of this relationship.
 
 In the HF, a suite of FPGA readout electronics processes data at the full 40 MHz LHC collision rate. The record the number of channels in which above-threshold charge was deposited during the bunch crossing. The PLT looks for tracks from the collision point that hit all three sensors in one of the telescopes -- the fraction of events with no PLT coincidences can be used in the luminosity calculation. The BCM1F has readout that is optimized for time precision. This subdetector has a time resolution of just over 6 ns, so it can separate collision hits from beam-related background hits. The data from all of these luminometers can be used to converge on a precise, stable determination of the luminosity in CMS.
 
@@ -71,20 +71,22 @@ The two methods produce very similar formulas based on different observables. Af
 
 Proton-proton collisions:
 
- * 2011 data: 5.1 fb$^{-1}$
- * 2012 data: 19.6 fb$^{-1}$
- * 2015 data: 2.3 fb$^{-1}$
- * 2016 data: 35.9 fb$^{-1}$ (As of 2024, 16.4 fb$^{-1}$ have been released as Open Data.)
+ - 2011 data: 5.1 fb$^{-1}$
+ - 2012 data: 19.6 fb$^{-1}$
+ - 2015 data: 2.3 fb$^{-1}$
+ - 2016 data: 35.9 fb$^{-1}$ (As of 2024, 16.4 fb$^{-1}$ have been released as Open Data.)
 
 Heavy-ion collisions:
 
- * 2011 PbPb data: 149 $\mu\mathrm{b}^{-1}$
- * 2013 pp reference data: 5.3 pb$^{-1}$
- * 2013 pPb data: 30.4 nb$^{-1}$
- * 2015 pp reference data: 28 pb$^{-1}$
- * 2015 PbPb data: 560 $\mu\mathrm{b}^{-1}$
+ - 2011 PbPb data: 149 $\mu\mathrm{b}^{-1}$
+ - 2013 pp reference data: 5.3 pb$^{-1}$
+ - 2013 pPb data: 30.4 nb$^{-1}$
+ - 2015 pp reference data: 28 pb$^{-1}$
+ - 2015 PbPb data: 560 $\mu\mathrm{b}^{-1}$
 
 Read more:
- * [Luminosity Public Results](https://twiki.cern.ch/twiki/bin/view/CMSPublic/LumiPublicResults)
- * [Data Quality Public Results](https://twiki.cern.ch/twiki/bin/view/CMSPublic/DataQuality)
- * [Luminosity publications](https://twiki.cern.ch/twiki/bin/view/CMSPublic/PhysicsResultsLUM)
+
+ - [Luminosity Public Results](https://twiki.cern.ch/twiki/bin/view/CMSPublic/LumiPublicResults)
+ - [Data Quality Public Results](https://twiki.cern.ch/twiki/bin/view/CMSPublic/DataQuality)
+ - [Luminosity publications](https://twiki.cern.ch/twiki/bin/view/CMSPublic/PhysicsResultsLUM)
+