CERN Accelerating science

Luminosity-weighted distribution of the mean number of interactions per bunch crossing, $\mu$, for the full Run~2 $pp$ collision dataset at $\sqrt{s}=13$~\TeV. The $\mu$ corresponds to the mean of the Poisson distribution of the number of interactions per crossing calculated for each proton bunch. It is calculated from the instantaneous per bunch luminosity. All data recorded by ATLAS during stable beams are shown, including machine commissioning periods, special runs for detector calibration, LHC fills with a low number of circulating bunches or bunch spacing greater than 25~ns. The integrated luminosity and the mean $\mu$ value for each year are given also.

Schematic diagram illustrating the nominal Run~2 operations workflow for the data quality assessment of ATLAS data. Online histogram sources include the high-level trigger farm, the data acquisition system, and full reconstruction of a fraction of events accepted by the trigger.

Transverse impact parameter $d_{0}$ versus $\phi$ for charged-particle tracks. Left: For the first processing of the Express stream, the beam-spot location is not yet known accurately and $d_0$ is calculated relative to the beam-spot position as determined online. Right: A correctly determined beam spot results in a flat distribution after the application of updated conditions during the calibration loop, since here $d_0$ is calculated relative to the reconstructed beam spot.

Transverse impact parameter $d_{0}$ versus $\phi$ for charged-particle tracks. Left: For the first processing of the Express stream, the beam-spot location is not yet known accurately and $d_0$ is calculated relative to the beam-spot position as determined online. Right: A correctly determined beam spot results in a flat distribution after the application of updated conditions during the calibration loop, since here $d_0$ is calculated relative to the reconstructed beam spot.

Luminosity-weighted data quality inefficiencies (in \%) during stable beams in standard $pp$ collision physics runs at $\sqrt{s}=13$~\TeV\ between 2015 and 2018.

Top: Cumulative integrated luminosity delivered to and recorded by ATLAS between 2015 and 2018 during stable beam $pp$ collision data-taking at $\sqrt{s}=13$~\TeV. This includes machine commissioning periods, special runs for detector calibration, and LHC fills with a low number of circulating bunches or bunch spacing greater than 25~ns. Also shown is the cumulative integrated luminosity certified for physics analysis usage for the ATLAS experiment between 2015 and 2018 during standard $pp$ collision data-taking at $\sqrt{s}=13$~\TeV. The total integrated luminosity recorded for the standard $\sqrt{s}=13$~\TeV\ $pp$ collision dataset corresponds to 145~fb$^{-1}$. It is this number that is used in the denominator when calculating the data quality efficiency of the standard $\sqrt{s}=13$~\TeV\ $pp$ collision dataset. Bottom: Cumulative data quality efficiency versus total integrated luminosity delivered to the ATLAS experiment between 2015 and 2018.

Top: Cumulative integrated luminosity delivered to and recorded by ATLAS between 2015 and 2018 during stable beam $pp$ collision data-taking at $\sqrt{s}=13$~\TeV. This includes machine commissioning periods, special runs for detector calibration, and LHC fills with a low number of circulating bunches or bunch spacing greater than 25~ns. Also shown is the cumulative integrated luminosity certified for physics analysis usage for the ATLAS experiment between 2015 and 2018 during standard $pp$ collision data-taking at $\sqrt{s}=13$~\TeV. The total integrated luminosity recorded for the standard $\sqrt{s}=13$~\TeV\ $pp$ collision dataset corresponds to 145~fb$^{-1}$. It is this number that is used in the denominator when calculating the data quality efficiency of the standard $\sqrt{s}=13$~\TeV\ $pp$ collision dataset. Bottom: Cumulative data quality efficiency versus total integrated luminosity delivered to the ATLAS experiment between 2015 and 2018.

Illustration of an incident during 2017, which resulted in a significant loss of coverage for muons. Top: Number of hits in the various sectors of the RPC subsystem versus luminosity block, where the absence of entries for $\phi$-sectors 1 and 2 indicates a hardware issue. Bottom: Occupancy of reconstructed muons in the $\eta$--$\phi$ plane, where the deficit in the range $-1<\eta<1$ at $\phi\sim0$ illustrates the impact of this hardware problem on the reconstructed objects.

Illustration of an incident during 2017, which resulted in a significant loss of coverage for muons. Top: Number of hits in the various sectors of the RPC subsystem versus luminosity block, where the absence of entries for $\phi$-sectors 1 and 2 indicates a hardware issue. Bottom: Occupancy of reconstructed muons in the $\eta$--$\phi$ plane, where the deficit in the range $-1<\eta<1$ at $\phi\sim0$ illustrates the impact of this hardware problem on the reconstructed objects.