Articles

Luminosity determination in 𝑝𝑝 collisions at √𝑠 = 13 TeV using the ATLAS detector at the LHC

Aad, G.; Abbott, B.; Abeling, K.; Abidi, S. H.; Aboulhorma, A.; Abramowicz, H.; Abreu, H.; Abulaiti, Y.; Hoffman, A. C. A.; Acharya, B. S.; Bourdarios, C. A.; Adamczyk, L.; Adamek, L.; Addepalli, S. V.; Adelman, J.; Adiguzel, A.; Adorni, S.; Adye, T.; Affolder, A. A.; Afik, Y.; Agaras, M. N.; Agarwala, J.; Aggarwal, A.; Agheorghiesei, C.; Aguilar-Saavedra, J. A.; Ahmad, A.; Ahmadov, F.; Ahmed, W. S.; Ahuja, S.; Ai, X.; Aielli, G.; Tamlihat, M. A.; Aitbenchikh, B.; Aizenberg, I.; Akbiyik, M.; Åkesson, T. P. A.; Akimov, A. V.; Akolkar, N. N.; Khoury, K. A.; Alberghi, G. L.; Brooijmans, Gustaaf H.; Busch, Elena Laura; Cole, Brian A.

The luminosity determination for the ATLAS detector at the LHC during Run 2 is presented, with 𝑝𝑝 collisions at a centre-of-mass energy √𝑠 = 13 TeV. The absolute luminosity scale is determined using van der Meer beam separation scans during dedicated running periods in each year, and extrapolated to the physics data-taking regime using complementary measurements from several luminosity-sensitive detectors.

The total uncertainties in the integrated luminosity for each individual year of data-taking range from 0.9% to 1.1%, and are partially correlated between years. After standard data-quality selections, the full Run 2 pp data sample corresponds to an integrated luminosity of 140.1 ± 1.2fb⁻¹, i.e. an uncertainty of 0.83%. A dedicated sample of low-pileup data recorded in 2017–2018 for precision Standard Model physics measurements is analysed separately, and has an integrated luminosity of
338.1 ± 3.1 pb⁻¹.

Files

  • thumnail for 10052_2023_Article_11747.pdf 10052_2023_Article_11747.pdf application/pdf 7.36 MB Download File

Also Published In

Title
The European Physical Journal C
DOI
https://doi.org/10.1140/epjc/s10052-023-11747-w

More About This Work

Academic Units
Physics
Published Here
February 5, 2025

Notes

SWORD deposit contains more than 40 names, only first 40 processed. See mets.xml for full list. Large number of Name fields will generate error in Hyacinth. See JIRA ticket SWORD-86.