Satellite Bunches:

• Measurement of the Rate of Collisions from Satellite Bunches for the April-May 2010 LHC Luminosity Calibration − ATLAS-CONF-2010-102

Multiple Year Collision Plots

These plots are based on the online luminosity estimate.

plot

Delivered Luminosity versus time for 2011-2018 (p-p data only) Cumulative luminosity versus day delivered to ATLAS during stable beams and for high energy p-p collisions.	pdf file
Total Integrated Luminosity at Run 2 (13 TeV pp data only) Cumulative luminosity versus time delivered to ATLAS (green) and recorded by ATLAS (yellow) during stable beams for pp collisions at 13 TeV centre-of-mass energy in LHC Run 2. A version showing just the delivered luminosity (green) is also available as pdf and png for making overlay animations.	pdf file
Total Integrated Luminosity and Data Quality in 2015-2018 Cumulative luminosity versus time delivered to ATLAS (green), recorded by ATLAS (yellow), and certified to be good quality data (blue) during stable beams for pp collisions at 13 TeV centre-of-mass energy in 2015-2018. The complete pp data sample in 2018 is shown. The delivered luminosity accounts for the luminosity delivered from the start of stable beams until the LHC requests ATLAS to put the detector in a safe standby mode to allow a beam dump or beam studies. The recorded luminosity reflects the DAQ inefficiency, as well as the inefficiency of the so‐ called "warm start": when the stable beam flag is raised, the tracking detectors undergo a ramp of the high-voltage and, for the pixel system, turning on the preamplifiers. The data quality assessment shown corresponds to the All Good efficiency shown in the 2015-2018 Full Dataset DQ tables here. The All Good Data Quality criteria require all reconstructed physics objects to be of good data quality. A version showing just the delivered luminosity (green) is available as pdf and png. A version showing the delivered luminosity (green) and recorded luminosity (yellow) is available as pdf and png.	pdf file

Luminosity summary plots for 2018 pp data taking

These plots show the estimated integrated luminosity with an initial calibration for the 2018 data.

Total Integrated Luminosity in 2018 Cumulative luminosity versus time delivered to (green) and recorded by ATLAS (yellow) during stable beams for pp collisions at 13 TeV centre-of-mass energy in 2018. The delivered luminosity accounts for luminosity delivered from the start of stable beams until the LHC requests ATLAS to put the detector in a safe standby mode to allow for a beam dump or beam studies. The recorded luminosity reflects the DAQ inefficiency, as well as the inefficiency of the so-called ‘warm start’: when the stable beam flag is raised, the tracking detectors undergo a ramp of the high-voltage and, for the pixel system, turning on the preamplifiers. <The luminosity shown represents an initial 13 TeV luminosity calibration for the 2018 data based on van-der-Meer beam-separation scans in 2017.	pdf file
Total Integrated Luminosity and Data Quality in 2018 Cumulative luminosity versus time delivered to ATLAS (green), recorded by ATLAS (yellow), and certified to be good quality data (blue) during stable beams for pp collisions at 13 TeV centre-of-mass energy in 2018. The complete pp data sample in 2018 is shown. The delivered luminosity accounts for the luminosity delivered from the start of stable beams until the LHC requests ATLAS to put the detector in a safe standby mode to allow a beam dump or beam studies. The recorded luminosity reflects the DAQ inefficiency, as well as the inefficiency of the so‐ called "warm start": when the stable beam flag is raised, the tracking detectors undergo a ramp of the high-voltage and, for the pixel system, turning on the preamplifiers. The data quality assessment shown corresponds to the All Good efficiency shown in the 2018 Full Dataset DQ tables here. The All Good Data Quality criteria require all reconstructed physics objects to be of good data quality. A version showing just the delivered luminosity (green) is available as pdf and png. A version showing the delivered luminosity (green) and recorded luminosity (yellow) is available as pdf and png.	pdf file
Integrated Luminosity by Day in 2018 Integrated luminosity per day time delivered to (green) and recorded by ATLAS (yellow) during stable beams for pp collisions at 13 TeV centre-of-mass energy in 2018. The data shown is identical to the data shown above, except not cumulative over the year.	pdf file
Peak Luminosity per Fill in 2018 The peak instantaneous luminosity delivered to ATLAS during stable beams for pp collisions at 13 TeV centre-of-mass energy is shown for each LHC fill as a function of time in 2018. The luminosity is determined using counting rates measured by the luminosity detectors, and is based on an initial estimate from van-der-Meer beam-separation scans during 2017.	pdf file
Peak Interactions per Crossing in 2018 The maximum number of inelastic collisions per beam crossing (µ) during stable beams for pp collisions at 13 TeV centre-of-mass energy is shown for each fill in 2018. The preliminary luminosity measurement is used to determine the number of interactions per beam crossing as µ = Lbunch x σinel / fr where Lbunch is the per-bunch instantaneous luminosity, σinel is the inelastic cross-section at 13 TeV, which is taken to be 80 mb, and fr is the LHC revolution frequency of 11.245 kHz. The number of interactions shown is averaged over all colliding bunch pairs, and only the peak value per fill during stable beams is shown.	pdf file
Total Stable Beam Time by Day in 2018 Total Stable Beams Time - shown is the amount of time in stable beams delivered by the LHC each calendar day integrated over 2018. Also shown is the stable beams time multiplied by the L1 livefraction to show the amount of stable beams time recorded by ATLAS.	pdf file
Stable Beam Time in 2018 Stable Beams Time per day - shown is the amount of time in stable beams delivered by the LHC for each calendar day. Also shown is the stable beams time multiplied by the L1 livefraction to show the amount of stable beams time recorded by ATLAS.	pdf file

Luminosity summary plots for 2018 PbPb data taking

Total Integrated Luminosity in 2018 Cumulative luminosity versus time delivered to (blue) and recorded by ATLAS (cyan) during stable beams for PbPb collisions at 5 TeV centre-of-mass energy in 2018. The delivered luminosity accounts for luminosity delivered from the start of stable beams until the LHC requests ATLAS to put the detector in a safe standby mode to allow for a beam dump or beam studies. The recorded luminosity reflects the DAQ inefficiency, as well as the inefficiency of the so-called ‘warm start’: when the stable beam flag is raised, the tracking detectors undergo a ramp of the high-voltage and, for the pixel system, turning on the preamplifiers. Shown is the luminosity as determined from counting rates measured by the luminosity detectors using a preliminary calibration.	pdf file
Integrated Luminosity by Day in 2018 Integrated luminosity per day time delivered to (blue) and recorded by ATLAS (cyan) during stable beams for PbPb collisions at 5 TeV centre-of-mass energy in 2018. The data shown is identical to the data shown above, except not cumulative over the running period.	pdf file
Peak Luminosity per Fill in 2018 The peak instantaneous luminosity delivered to ATLAS during stable beams for PbPb collisions at 5 TeV centre-of-mass energy is shown for each LHC fill as a function of time in 2018. The luminosity is determined using counting rates measured by the luminosity detectors, and is based on an initial calibration estimated from the previous 2015 PbPb data.	pdf file

Luminosity summary plots for 2017 pp data taking

These plots show the estimated integrated luminosity with a preliminary calibration for the 2017 data.

Total Integrated Luminosity in 2017 Cumulative luminosity versus time delivered to (green) and recorded by ATLAS (yellow) during stable beams for pp collisions at 13 TeV centre-of-mass energy in 2017. The delivered luminosity accounts for luminosity delivered from the start of stable beams until the LHC requests ATLAS to put the detector in a safe standby mode to allow for a beam dump or beam studies. The recorded luminosity reflects the DAQ inefficiency, as well as the inefficiency of the so-called ‘warm start’: when the stable beam flag is raised, the tracking detectors undergo a ramp of the high-voltage and, for the pixel system, turning on the preamplifiers. Shown is the luminosity as determined from counting rates measured by the luminosity detectors. The luminosity shown represents a preliminary 13 TeV luminosity calibration for the 2017 data based on van-der-Meer beam-separation scans in 2016.	pdf file
Integrated Luminosity by Day in 2017 Integrated luminosity per day time delivered to (green) and recorded by ATLAS (yellow) during stable beams for pp collisions at 13 TeV centre-of-mass energy in 2017. The data shown is identical to the data shown above, except not cumulative over the year.	pdf file
Peak Luminosity per Fill in 2017 The peak instantaneous luminosity delivered to ATLAS during stable beams for pp collisions at 13 TeV centre-of-mass energy is shown for each LHC fill as a function of time in 2017. The luminosity is determined using counting rates measured by the luminosity detectors, and is based on a preliminary analysis of van-der-Meer beam-separation scans during 2016.	pdf file
Peak Interactions per Crossing in 2017 The maximum number of inelastic collisions per beam crossing (µ) during stable beams for pp collisions at 13 TeV centre-of-mass energy is shown for each fill in 2017. The preliminary luminosity measurement is used to determine the number of interactions per beam crossing as µ = Lbunch x σinel / fr where Lbunch is the per-bunch instantaneous luminosity, σinel is the inelastic cross-section at 13 TeV, which is taken to be 80 mb, and fr is the LHC revolution frequency of 11.245 kHz. The number of interactions shown is averaged over all colliding bunch pairs, and only the peak value per fill during stable beams is shown.	pdf file
Total Stable Beam Time by Day in 2017 Total Stable Beams Time - shown is the amount of time in stable beams delivered by the LHC each calendar day integrated over 2017. Also shown is the stable beams time multiplied by the L1 livefraction to show the amount of stable beams time recorded by ATLAS.	pdf file
Stable Beam Time in 2017 Stable Beams Time per day - shown is the amount of time in stable beams delivered by the LHC for each calendar day. Also shown is the stable beams time multiplied by the L1 livefraction to show the amount of stable beams time recorded by ATLAS.	pdf file

Luminosity summary plots for 2016 pp data taking

These plots show the estimated integrated luminosity with the preliminary calibration update from February 2017.

Total Integrated Luminosity in 2016 Cumulative luminosity versus time delivered to (green) and recorded by ATLAS (yellow) during stable beams for pp collisions at 13 TeV centre-of-mass energy in 2016. The delivered luminosity accounts for luminosity delivered from the start of stable beams until the LHC requests ATLAS to put the detector in a safe standby mode to allow for a beam dump or beam studies. The recorded luminosity reflects the DAQ inefficiency, as well as the inefficiency of the so-called ‘warm start’: when the stable beam flag is raised, the tracking detectors undergo a ramp of the high-voltage and, for the pixel system, turning on the preamplifiers. Shown is the luminosity as determined from counting rates measured by the luminosity detectors. These detectors have been calibrated with the use of the van-der-Meer beam-separation method, where the two beams are scanned against each other in the horizontal and vertical planes to measure their overlap function. The luminosity shown represents the preliminary 13 TeV luminosity calibration based on van-der-Meer beam-separation scans in 2016.	pdf file
Integrated Luminosity by Day in 2016 Integrated luminosity per day time delivered to (green) and recorded by ATLAS (yellow) during stable beams for pp collisions at 13 TeV centre-of-mass energy in 2016. The data shown is identical to the data shown above, except not cumulative over the year.	pdf file
Peak Luminosity per Fill in 2016 The peak instantaneous luminosity delivered to ATLAS during stable beams for pp collisions at 13 TeV centre-of-mass energy is shown for each LHC fill as a function of time in 2016. The luminosity is determined using counting rates measured by the luminosity detectors, and is based on a preliminary analysis of van-der-Meer beam-separation scans during 2016.	pdf file
Peak Interactions per Crossing in 2016 The maximum number of inelastic collisions per beam crossing (µ) during stable beams for pp collisions at 13 TeV centre-of-mass energy is shown for each fill in 2016. The preliminary luminosity measurement is used to determine the number of interactions per beam crossing as µ = Lbunch x σinel / fr where Lbunch is the per-bunch instantaneous luminosity, σinel is the inelastic cross-section at 13 TeV, which is taken to be 80 mb, and fr is the LHC revolution frequency of 11.245 kHz. The number of interactions shown is averaged over all colliding bunch pairs, and only the peak value per fill during stable beams is shown.	pdf file
Total Stable Beam Time by Day in 2016 Total Stable Beams Time - shown is the amount of time in stable beams delivered by the LHC each calendar day integrated over 2016. Also shown is the stable beams time multiplied by the L1 livefraction to show the amount of stable beams time recorded by ATLAS.	pdf file
Stable Beam Time in 2016 Stable Beams Time per day - shown is the amount of time in stable beams delivered by the LHC for each calendar day. Also shown is the stable beams time multiplied by the L1 livefraction to show the amount of stable beams time recorded by ATLAS.	pdf file

Luminosity summary plots for 2016 pPb and Pbp data taking

Total Integrated Luminosity in 2016 Cumulative luminosity versus time delivered to (blue) and recorded by ATLAS (cyan) during stable beams for pPb and Pbp collisions at 5 TeV and 8 TeV centre-of-mass energy in 2016. The delivered luminosity accounts for luminosity delivered from the start of stable beams until the LHC requests ATLAS to put the detector in a safe standby mode to allow for a beam dump or beam studies. The recorded luminosity reflects the DAQ inefficiency, as well as the inefficiency of the so-called ‘warm start’: when the stable beam flag is raised, the tracking detectors undergo a ramp of the high-voltage and, for the pixel system, turning on the preamplifiers. Shown is the luminosity as determined from counting rates measured by the luminosity detectors using a preliminary calibration.

pdf file

Integrated Luminosity by Day in 2016 Integrated luminosity per day time delivered to (blue) and recorded by ATLAS (cyan) during stable beams for pPb and Pbp collisions at 5 TeV and 8 TeV centre-of-mass energy in 2016. The data shown is identical to the data shown above, except not cumulative over the running period.

pdf file

Luminosity Plots for the 2017 Analysis

• LUMI-2017-001 vdM scan, non-factorisation analysis, bunch train, mu-correction and long-term stability plots.
• LUMI-2017-002 Track-counting selection plots.
• LUMI-2017-003 Z-counting analysis and stability plots.

Luminosity Plots for the 2016 Analysis

Visible Interaction Rate during VdM Scan Visible interaction rate per bunch crossing and per unit bunch-population product, for the LUCID algorithm (lucBiHitOR), that provides the ATLAS luminosity, versus nominal beam separation during horizontal scan 1 in the May 2016 luminosity-calibration session. The total rate measured for a single colliding-bunch pair at position 872 in the fill pattern is shown as red circles, and the background-subtracted rate as magenta squares. The background is dominated by random counts from the radioactive Bismuth source used for phototube gain calibration (blue triangles), as estimated from the rate measured in the preceding unfilled bunch slot. Also shown is the beam-gas background (green triangles) measured using non-colliding bunches. The background-subtracted rate is fitted by a Gaussian multiplied by a sixth-order polynomial (dashed curve). The error bars are statistical only.	pdf file, eps file
Amplitude Distribution for LUCID PMT 1 Amplitude distribution for LUCID PMT 1 in the Bi-207 calibration run 282071.	pdf file, eps file
Amplitude Distribution for LUCID PMT 1 Amplitude distribution for LUCID PMT 1 in the low-μ physics run 282026. The trigger threshold at ~ 25 mV is apparent. The pile-up parameter μ was between 0.02 and 0.15 inelastic interactions per bunch crossing.	pdf file, eps file
Amplitude Distribution for LUCID PMT 1 Amplitude distribution for LUCID PMT 1 in the physics run 284420. The trigger threshold at ~ 25 mV is apparent. Over the course of this run, the pile-up parameter μ varied between 24 and 11 inelastic interactions per bunch crossing.	pdf file, eps file
Distribution of Pulse Amplitudes from one of the LUCID Photomultipliers Distribution of pulse amplitudes from one of the LUCID photomultipliers in a Bi calibration run (blue) and the physics run 305618 (red) in 2016. Over the course of the physics run, the pile-up parameter μ varied between 43 and 14 inelastic interactions per bunch crossing.	pdf file, eps file
Ratio of the Bunch-averaged Pile-up Parameter Ratio of the bunch-averaged pile-up parameter <μ_Tracking> reported by the track-counting luminosity algorithm, to the <μAlgo> value obtained using either the LUCID_HitOR or the TILE-D6 algorithms, as a function of <μ_Algo> during reference run 305618 . The square red points are parameterized by a first-order polynomial fit that is shown as a line and that is used to correct the LUCID luminosity for both calibration transfer and μ-dependence in all 2016 runs.	pdf file, eps file
Correction Factor Applied to the Track-Counting Luminosity Correction factor applied to the track-counting luminosity due to time-dependent effects on the track reconstruction and selection efficiency over 2016. This correction factor is derived from a tag-and-probe analysis of reconstructed Z ➝ μμ decays; only the reconstruction and selection efficiency of the muon in the Inner Detector is considered and the same quality selections as in the luminosity analysis are applied to the reconstructed muons. Since this tracking efficiency cannot be measured directly with this method in vdM fills due to lack of statistics, the correction has been normalized to unity in the high-luminosity reference physics run (indicated by a red square) that took place immediately after the first vdM run.	pdf file, eps file
Correction Factor Applied to the LUCID_HitOR Correction factor applied to the LUCID_HitOR luminosity to correct for changes in mean amplitude observed in the Bi-207 calibration runs over 2016. The correction has been normalized such that the mean amplitude is unity in the calibration reference run (indicated by a red square) that immediately follows the first vdM run.	pdf file, eps file
Pile-up Parameter μ as a Function of the Bunch-crossing Number Measured pile-up parameter μ as a function of the bunch-crossing number averaged over the duration of the run, in a physics fill in 2016. The plot shows that there are more than 3 orders of magnitude bewteen the μ measured for colliding BCIDs and the afterglow background in the non-colliding BCIDs.	pdf file, eps file
Ratio of the Luminosity Measured by the E4 Tile Scintillators to Track Counting Ratio of the luminosity measured by the E4 Tile scintillators to that from track counting, in the two vdM fills in 2016 and the two physics runs that follow them. The data has been normalized such that the run-integrated TILE luminosity agrees with the track-based luminosity in vdM fill 4954 (green triangles). Each point corresponds to 15 luminosity blocks (approximately 15 minutes). The luminosity-block numbers in the four runs, displayed on the horizontal axis, have been incremented by a run-dependent offset, in order to present the data as a continuous time sequence from which the no-beam periods have been supressed.	pdf file, eps file
Difference in Run-integrated Luminosity between Algorithms Fractional difference in run-integrated luminosity between the LUCID_HitOR algorithm, and the TILE, EMEC, FCal and track-counting algorithms. Each point corresponds to an ATLAS run recorded during 25 ns bunch-train running in 2016 at √s = 13 TeV. The luminosity measurements by TILE, EMEC, FCal and Tracking have been normalized to LUCID in a physics run recorded on August 4th, which is indicated by the red arrow. The data suggest that a -0.7% drift correction should be applied to the LUCID luminosity values in the period from June 1st to July 8th, indicated by the two vertical lines.	pdf file, eps file
Difference in Run-integrated Luminosity between Algorithms Fractional difference in run-integrated luminosity between the LUCID_HitOR algorithm, and the TILE, EMEC, FCal and track-counting algorithms. The LUCID luminosity in the period from June 1st to July 8th has been corrected down by 0.7% in this plot. Each point corresponds to an ATLAS run recorded during 25 ns bunch-train running in 2016 at √s = 13 TeV. The luminosity measurements by TILE, EMEC, FCal and Tracking have been normalized to LUCID in a physics run recorded on August 4th, which is indicated by the red arrow.	pdf file, eps file
Difference in Run-integrated Luminosity between Algorithms Fractional difference in run-integrated luminosity between the LUCID_HitOR algorithm, and the TILE, EMEC, FCal and track-counting algorithms. Only runs with more than 600 bunches are shown. The LUCID luminosity in the period from June 1st to July 8th has been corrected down by 0.7% in this plot. Each point corresponds to an ATLAS run recorded during 25 ns bunch-train running in 2016 at √s = 13 TeV. The luminosity measurements by TILE, EMEC, FCal and Tracking have been normalized to LUCID in a physics run recorded on August 4th, which is indicated by the red arrow.	pdf file, eps file
Difference in Run-integrated Luminosity between Algorithms Fractional difference in run-integrated luminosity between the LUCID_HitOR algorithm, and the TILE, EMEC, FCal and track-counting algorithms, as a function of the cumulative delivered luminosity (normalized to the 2016 total). The LUCID luminosity in the period from June 1st to July 8th has been corrected down by 0.7%. Each point corresponds to an ATLAS run recorded during 25 ns bunch-train running in 2016 at √s = 13 TeV. The luminosity measurements by TILE, EMEC, FCal and Tracking have been normalized to LUCID in a physics run recorded on August 4th, which is indicated by the red arrow.	pdf file, eps file
Difference in Run-integrated Luminosity between Algorithms Fractional difference in run-integrated luminosity between the LUCID_HitOR algorithm, and the TILE, EMEC, FCal and track-counting algorithms, as a function of the cumulative delivered luminosity (normalized to the 2016 total). Only runs with more than 600 bunches are shown. The LUCID luminosity in the period from June 1st to July 8th has been corrected down by 0.7%. Each point corresponds to an ATLAS run recorded during 25 ns bunch-train running in 2016 at √s = 13 TeV. The luminosity measurements by TILE, EMEC, FCal and Tracking have been normalized to LUCID in a physics run recorded on August 4th, which is indicated by the red arrow.	pdf file, eps file
Difference in Run-integrated Luminosity between Algorithms Fractional difference in run-integrated luminosity between track-counting and the LUCID, TILE, EMEC and FCal algorithms. Each point corresponds to an ATLAS run recorded during 25 ns bunch-train running in 2016 at √s = 13 TeV. The luminosity measurements by TILE, EMEC, FCal and Tracking have been normalized to LUCID in a physics run recorded on August 4th, which is indicated by the red arrow. The LUCID data in the period from June 1st to July 8th (indicated by the two vertical lines) have not been drift- corrected in this plot.	pdf file, eps file

Pixel Cluster Counting Luminosity Plots

Figure 1 Longitudinal cluster-size distributions in the most forward IBL 3D module on the negative-z side, obtained from simulated single-interaction minimum-bias events. Only clusters originating from primary particles are used. The broken or on-module-edge clusters are shorter than the unbroken off-module-edge clusters. On-module-edge clusters are identified on the basis of their position, length and width. If two clusters have a one-pixel gap along the z direction and their hits are in the same or adjacent rows along the azimuthal direction, they are identified as broken clusters from the same long cluster.	pdf file, eps file
Figure 3 Number of clusters in the 3D modules on the positive-z (red) and the negative-z (blue) side of the IBL as a function of the longitudinal position of the interaction, obtained from simulated single-interaction minimum-bias events. The distribution of all clusters is fitted with a second-order polynomial.	pdf file, eps file
Figure 4 Two-component fit to the cluster length distribution of whole clusters in the most forward IBL 3D module on the negative-z side. Clusters on the module edges and broken clusters have been removed. The data correspond to about one minute of data-taking and are extracted from randomly triggered events. The fit components are a Gaussian to describe the clusters from primary particles and a template derived from simulation to describe the clusters generated by particles from secondary interactions. Clusters shorter than three pixels are excluded from the fit to minimize the systematic uncertainty from background sources that are not simulated, such as noisy pixels.	pdf file, eps file
Figure 5 Azimuthal dependence of the number of primary clusters for the modules in the most forward IBL µ ring on the negative-z side. The data correspond to about one minute of data-taking and are extracted from randomly triggered events. A plain average of all modules at the same µ can be biased when a module has a transient problem. In order to exclude modules identified as having a transient problem, the azimuthal distribution of the number of clusters is fitted to a sinusoidal function, in order to account for the beams not being perfectly centered in the IBL. The area under the fitted curve is then taken as the correct cluster count. In this example, the module at azimuthal index 8 has been excluded.	pdf file, eps file
Figure 6 Dependence of the number of clusters on the luminous length. The black points show the number of clusters obtained in the simulated minimum-bias samples for different values of the luminous length σz but the same longitudinal position of the luminous centroid (µz = -2mm). A correction is applied to take into account the σz dependence; the green points show the number of clusters after correction. The correction is designed to return the ideal number of clusters that would have been observed if all interactions happened at the IBL center (µz = σz = 0) and therefore the corrected number of clusters is expected no longer to depend on µz or σz.	pdf file, eps file
Figure 7 Dependence of the number of clusters on the longitudinal position of the luminous centroid. The black points show the number of clusters obtained in the simulated minimum-bias samples for different longitudinal positions (µz) of the luminous centroid, but with the same luminous length (σz = 35mm). A correction is applied to take into account the µz dependence; the green points show the number of clusters after the correction. The correction is designed to return the ideal number of clusters that would have been observed if all interactions happened at the IBL center (µz = σz = 0) and therefore the corrected number of clusters is expected no longer to depend on µz or σz.	pdf file, eps file
Figure 8 Time stability of the PCC/LUCID luminosity ratio over the course of LHC fill 6024, after application of the luminous-region-dependent corrections illustrated in the previous two figures. LUCID is the baseline ATLAS luminometer. The rate of primary pixel clusters, integrated over the duration of the fill, is normalized to the LUCID-based integrated luminosity over the same period. Only statistical errors are shown.	pdf file, eps file

Annual plots

2018 pp Collisions

Pileup Interactions and Data Taking Efficiency

Number of Interactions per Crossing Shown is the luminosity-weighted distribution of the mean number of interactions per crossing for the 2018 pp collision data at 13 TeV centre-of-mass energy. All data recorded by ATLAS during stable beams is shown, and the integrated luminosity and the mean mu value are given in the figure. The mean number of interactions per crossing corresponds to the mean of the poisson distribution of the number of interactions per crossing calculated for each bunch. It is calculated from the instantaneous per bunch luminosity as μ=Lbunch x σinel / fr where Lbunch is the per bunch instantaneous luminosity, σinel is the inelastic cross section which we take to be 80 mb for 13 TeV collisions, and fr is the LHC revolution frequency. The luminosity shown represents the preliminary 13 TeV luminosity calibration for 2018, released in February 2019, that is based on van-der-Meer beam-separation scans. Data collected by ATLAS for the entire 2018 run through the end of October are shown.

pdf file eps file

Number of Interactions per Crossing Same as above, but additionally showing the 13 TeV data from 2015 -- 2018.

pdf file eps file

2017 pp Collisions

Pileup Interactions and Data Taking Efficiency

Number of Interactions per Crossing Shown is the luminosity-weighted distribution of the mean number of interactions per crossing for the 2017 pp collision data at 13 TeV centre-of-mass energy. All data recorded by ATLAS during stable beams is shown, and the integrated luminosity and the mean mu value are given in the figure. The mean number of interactions per crossing corresponds to the mean of the poisson distribution of the number of interactions per crossing calculated for each bunch. It is calculated from the instantaneous per bunch luminosity as μ=Lbunch x σinel / fr where Lbunch is the per bunch instantaneous luminosity, σinel is the inelastic cross section which we take to be 80 mb for 13 TeV collisions, and fr is the LHC revolution frequency. The luminosity shown represents the preliminary 13 TeV luminosity calibration released in February 2018, based on van-der-Meer beam-separation scans in 2017.

pdf file eps file

Number of Interactions per Crossing Same as above, but additionally showing the 13 TeV data from 2015 -- 2017.

pdf file eps file

2016 pp Collisions

Pileup Interactions and Data Taking Efficiency

Number of Interactions per Crossing Shown is the luminosity-weighted distribution of the mean number of interactions per crossing for the 2016 pp collision data at 13 TeV centre-of-mass energy. All data delivered to ATLAS during stable beams is shown, and the integrated luminosity and the mean mu value are given in the figure. The mean number of interactions per crossing corresponds to the mean of the poisson distribution of the number of interactions per crossing calculated for each bunch. It is calculated from the instantaneous per bunch luminosity as μ=Lbunch x σinel / fr where Lbunch is the per bunch instantaneous luminosity, σinel is the inelastic cross section which we take to be 80 mb for 13 TeV collisions, and fr is the LHC revolution frequency. The luminosity shown represents the preliminary 13 TeV luminosity calibration released in February 2017, based on van-der-Meer beam-separation scans in 2016.	pdf file eps file
Number of Interactions per Crossing Same as above, but showing the combined 13 TeV data from 2015 and 2016.	pdf file eps file
Number of Interactions per Crossing Shown is the luminosity-weighted distribution of the mean number of interactions per crossing for the 2016 pp collision data recorded from 16 April - 16 September at 13 TeV centre-of-mass energy. All data delivered to ATLAS during stable beams is shown, and the integrated luminosity and the mean mu value are given in the figure. The mean number of interactions per crossing corresponds to the mean of the poisson distribution of the number of interactions per crossing calculated for each bunch. It is calculated from the instantaneous per bunch luminosity as μ=Lbunch x σinel / fr where Lbunch is the per bunch instantaneous luminosity, σinel is the inelastic cross section which we take to be 80 mb for 13 TeV collisions, and fr is the LHC revolution frequency. The luminosity shown represents the preliminary 13 TeV luminosity calibration based on van-der-Meer beam-separation scans in 2016. This plot was first shown at the September 2016 LHCC meeting.	pdf file eps file
Number of Interactions per Crossing Same as above, but showing the combined 13 TeV data from 2015 and 2016.	pdf file eps file
Number of Interactions per Crossing Shown is the luminosity-weighted distribution of the mean number of interactions per crossing for the 2016 pp collision data recorded from 16 April - 25 July at 13 TeV centre-of-mass energy. All data delivered to ATLAS during stable beams is shown, and the integrated luminosity and the mean mu value are given in the figure. The mean number of interactions per crossing corresponds to the mean of the poisson distribution of the number of interactions per crossing calculated for each bunch. It is calculated from the instantaneous per bunch luminosity as μ=Lbunch x σinel / fr where Lbunch is the per bunch instantaneous luminosity, σinel is the inelastic cross section which we take to be 80 mb for 13 TeV collisions, and fr is the LHC revolution frequency. The luminosity shown represents the preliminary 13 TeV luminosity calibration based on van-der-Meer beam-separation scans in 2016. This plot was first shown at ICHEP 2016.	pdf file eps file
Number of Interactions per Crossing Same as above, but showing the combined 13 TeV data from 2015 and 2016.	pdf file eps file
Number of Interactions per Crossing Shown is the luminosity-weighted distribution of the mean number of interactions per crossing for the 2016 pp collision data recorded from 16 April - 13 June at 13 TeV centre-of-mass energy. All data delivered to ATLAS during stable beams is shown, and the integrated luminosity and the mean mu value are given in the figure. The mean number of interactions per crossing corresponds to the mean of the poisson distribution of the number of interactions per crossing calculated for each bunch. It is calculated from the instantaneous per bunch luminosity as μ=Lbunch x σinel / fr where Lbunch is the per bunch instantaneous luminosity, σinel is the inelastic cross section which we take to be 80 mb for 13 TeV collisions, and fr is the LHC revolution frequency. The luminosity shown represents the initial 2016 13 TeV luminosity calibration which is based on the 2015 calibration. This plot was first shown at LHCP 2016.	pdf file eps file
Number of Interactions per Crossing Same as above, but showing the combined 13 TeV data from 2015 and 2016.	pdf file eps file
Data Taking Efficiency per Day ATLAS data taking efficiency in 2016. The denominator is the luminosity delivered between the declaration of stable beams and the LHC request to turn the sensitive detectors off to allow a beam dump or beam studies. The numerator is the luminosity recorded by ATLAS. Each bin represents one day. The empty bins are due to days in which no stable beams were delivered by the LHC. The inefficiency accounts for the time needed to turn on the high-voltage of the Pixel, SCT, and some of the muon detectors at the start of an LHC fill and any inefficiencies due to deadtime or due to individual problems with a given sub detector that prevents the ATLAS data taking to proceed.	pdf file
Data Taking Efficiency per Week Same as above but per week.	pdf file

2015 pp Collisions

Pileup Interactions and Data Taking Efficiency

Number of Interactions per Crossing Shown is the luminosity-weighted distribution of the mean number of interactions per crossing for the 2015 pp collision data recorded from 3 June - 3 November at 13 TeV centre-of-mass energy. All data delivered to ATLAS during stable beams is shown, and the integrated luminosity and the mean mu value are given in the figure. The mean number of interactions per crossing corresponds to the mean of the poisson distribution of the number of interactions per crossing calculated for each bunch. It is calculated from the instantaneous per bunch luminosity as μ=Lbunch x σinel / fr where Lbunch is the per bunch instantaneous luminosity, σinel is the inelastic cross section which we take to be 80 mb for 13 TeV collisions, and fr is the LHC revolution frequency. The luminosity shown represents the preliminary 13 TeV luminosity calibration which was updated in December 2015.	pdf file eps file
Number of Interactions per Crossing Same as above, but with data delivered in fills with 50ns and 25ns bunch spacing shown separately.	pdf file eps file
Data Taking Efficiency per Day ATLAS data taking efficiency in 2015. The denominator is the luminosity delivered between the declaration of stable beams and the LHC request to turn the sensitive detectors off to allow a beam dump or beam studies. The numerator is the luminosity recorded by ATLAS. Each bin represents one day. The empty bins are due to days in which no stable beams were delivered by the LHC. The inefficiency accounts for the time needed to turn on the high-voltage of the Pixel, SCT, and some of the muon detectors at the start of an LHC fill and any inefficiencies due to deadtime or due to individual problems with a given sub detector that prevents the ATLAS data taking to proceed.	pdf file
Data Taking Efficiency per Week Same as above but per week.	pdf file

Pileup Interactions - LHCP dataset

Number of Interactions per Crossing - LHCP Dataset Shown is the luminosity-weighted distribution of the mean number of interactions per crossing for the 2015 pp collision data recorded from 3 June - 25 August at 13 TeV centre-of-mass energy (LHCP dataset). All data delivered to ATLAS during stable beams is shown, and the integrated luminosity and the mean mu value are given in the figure. The mean number of interactions per crossing corresponds to the mean of the poisson distribution of the number of interactions per crossing calculated for each bunch. It is calculated from the instantaneous per bunch luminosity as μ=Lbunch x σinel / fr where Lbunch is the per bunch instantaneous luminosity, σinel is the inelastic cross section which we take to be 80 mb for 13 TeV collisions, and fr is the LHC revolution frequency.

pdf file eps file

Number of Interactions per Crossing - LHCP Dataset Same as above, but with data delivered in fills with 50ns and 25ns bunch spacing shown separately.

pdf file eps file

Luminosity summary plots for 2015 pp data taking

These plots show the estimated integrated luminosity with the most recent offline calibration. (December 2015)

Total Integrated Luminosity and Data Quality in 2015 Cumulative luminosity versus time delivered to ATLAS (green), recorded by ATLAS (yellow), and certified to be good quality data (blue) during stable beams for pp collisions at 13 TeV centre-of-mass energy in 2015. The delivered luminosity accounts for the luminosity delivered from the start of stable beams until the LHC requests ATLAS to put the detector in a safe standby mode to allow a beam dump or beam studies. The recorded luminosity reflects the DAQ inefficiency, as well as the inefficiency of the so‐ called "warm start": when the stable beam flag is raised, the tracking detectors undergo a ramp of the high-voltage and, for the pixel system, turning on the preamplifiers. The data quality assessment shown corresponds to the All Good efficiency shown in the 2015 EOYE Dataset DQ table here. The All Good Data Quality criteria require all reconstructed physics objects to be of good data quality. The IBL was turned off for two runs, corresponding to 0.2 fb-1 and analyses that don’t rely on the IBL can use 3.4 fb-1 of data with a corresponding DQ efficiency of 93.1%. The luminosity shown represents the preliminary 13 TeV luminosity calibration which was updated in December 2015. The table corresponds to the DQ tag DetStatus-v73-pro19-08 with lumi tag OflLumi-13TeV-003.	pdf file For animations: delivered (png) delivered (pdf) recorded (png) recorded (pdf)
Total Integrated Luminosity in 2015 Cumulative luminosity versus time delivered to (green) and recorded by ATLAS (yellow) during stable beams for pp collisions at 13 TeV centre-of-mass energy in 2015. The delivered luminosity accounts for luminosity delivered from the start of stable beams until the LHC requests ATLAS to put the detector in a safe standby mode to allow for a beam dump or beam studies. The recorded luminosity reflects the DAQ inefficiency, as well as the inefficiency of the so-called ‘warm start’: when the stable beam flag is raised, the tracking detectors undergo a ramp of the high-voltage and, for the pixel system, turning on the preamplifiers. Shown is the luminosity as determined from counting rates measured by the luminosity detectors. These detectors have been calibrated with the use of the van-der-Meer beam-separation method, where the two beams are scanned against each other in the horizontal and vertical planes to measure their overlap function. The luminosity shown represents the preliminary 13 TeV luminosity calibration which was updated in December 2015.	pdf file
Integrated Luminosity by Day in 2015 Integrated luminosity per day time delivered to (green) and recorded by ATLAS (yellow) during stable beams for pp collisions at 13 TeV centre-of-mass energy in 2015. The data shown is identical to the data shown above, except not cumulative over the year.	pdf file
Peak Luminosity per Fill in 2015 The peak instantaneous luminosity delivered to ATLAS during stable beams for pp collisions at 13 TeV centre-of-mass energy is shown for each LHC fill as a function of time in 2015. The luminosity is determined using counting rates measured by the luminosity detectors, and is based on a preliminary 13 TeV calibration determined using van-der-Meer beam-separation scans.	pdf file
Peak Interactions per Crossing in 2015 The maximum number of inelastic collisions per beam crossing (µ) during stable beams for pp collisions at 13 TeV centre-of-mass energy is shown for each fill in 2015. The preliminary luminosity measurement is used to determine the number of interactions per beam crossing as µ = Lbunch x σinel / fr where Lbunch is the per-bunch instantaneous luminosity, σinel is the inelastic cross-section at 13 TeV, which is taken to be 80 mb, and fr is the LHC revolution frequency of 11.245 kHz. The number of interactions shown is averaged over all colliding bunch pairs, and only the peak value per fill during stable beams is shown.	pdf file
Luminosity Ratio for Different Algorithms Fractional difference in run-integrated luminosity between the LUCID Bi_EvtORA algorithm, and the TILE, EMEC and track-counting algorithms. Each point corresponds to an ATLAS run recorded during 50 ns or 25 ns bunch-train running in 2015 at √s = 13 TeV. The luminosity measurements by TILE, EMEC and TRACKS have been normalized to LUCID in a group of physics runs recorded before the van der Meer calibration run on August 24th.	pdf file
Luminosity Ratio for Different Algorithms Fractional difference in run-integrated luminosity between the LUCID Bi_EvtORA measurement and the average of the values reported by the TILE, EMEC and track-counting algorithms. Each point corresponds to an ATLAS run recorded during 50 ns or 25 ns bunch-train running in 2015 at √s = 13 TeV. If one of more of the three detectors were not available the comparison uses the available detectors.	pdf file
Luminosity Ratio for Different Algorithms Fractional difference in run-integrated luminosity between the LUCID Bi_Evt_ORA and track-counting algorithms. Each point corresponds to an ATLAS run recorded during 50 ns or 25 ns bunch-train running in 2015 at √s = 13 TeV. Radioactive Bi-207 sources are used to monitor the gain of the photomultipliers in frequent calibration runs during the year. These pulse-height measurements are used to adjust the high voltage so that the gain remains constant throughout the year. In a second step, the Bi-207 calibrations are also used offline to correct the measured luminosity. The Figure shows the LUCID data before (red squares) and after the offline gain correction (black circles).	pdf file
Luminosity Ratio for Different Algorithms Fractional difference in run-integrated luminosity between the LUCID Bi_Evt_ORA and track-counting algorithms. Each point corresponds to an ATLAS run recorded during 50 ns and 25 ns bunch-train running in 2015 at √s = 13 TeV. By the end of the data-taking period, the cumulative increase in high voltage that had been applied during the year to keep the photomultiplier gain constant, resulted in a significant decrease of the transit time through the photomultipliers. This, in turn, resulted in a loss of some events outside the timing window, and thereby in a decrease in detector efficiency. The impact of the transit time increase was different for different photomultipliers and was negligible for one of them. This photomultiplier was used to correct the luminosity measured by the others. The Figure shows the LUCID data before (red squares) and after the transit-time correction (black circles).	pdf file
van der Meer Calibration Visible interaction rate for the LUCID algorithm (lucBiEvtA), that provides the ATLAS luminosity, in one bunch crossing and per unit bunch population, versus nominal beam separation during horizontal scan 1 in the August 2015 luminosity-calibration session. The total rate measured for a single colliding bunch pair at position 891 in the fill pattern is shown as red circles, and the background-subtracted rate as magenta squares. The background is dominated by random counts from the radioactive Bismuth source used for phototube gain calibration (blue triangles), as estimated from the rate measured in the preceding unfilled bunch slot. Also shown is the beam-gas background (green triangles) measured using non-colliding bunches. The background subtracted rate is fitted by a Gaussian multiplied by a sixth-order polynomial (dashed curve). The error bars are statistical only.	pdf file

Luminosity summary plots for 2015 5 TeV pp data taking

These plots show the estimated integrated luminosity of the 5 TeV reference data with the online calibration.

Total Integrated Luminosity in 2015 Cumulative luminosity versus time delivered to (green) and recorded by ATLAS (yellow) during stable beams for pp collisions at 5 TeV centre-of-mass energy in 2015. The delivered luminosity accounts for luminosity delivered from the start of stable beams until the LHC requests ATLAS to put the detector in a safe standby mode to allow for a beam dump or beam studies. The recorded luminosity reflects the DAQ inefficiency, as well as the inefficiency of the so-called ‘warm start’: when the stable beam flag is raised, the tracking detectors undergo a ramp of the high-voltage and, for the pixel system, turning on the preamplifiers. Shown is the luminosity as determined from counting rates measured by the luminosity detectors. An online calibration based on Monte Carlo estimates has been used to set the luminosity scale.	pdf file
Integrated Luminosity by Day in 2015 Integrated luminosity per day time delivered to (green) and recorded by ATLAS (yellow) during stable beams for pp collisions at 5 TeV centre-of-mass energy in 2015. The data shown is identical to the data shown above, except not cumulative over the year.	pdf file
Peak Luminosity per Fill in 2015 The peak instantaneous luminosity delivered to ATLAS during stable beams for pp collisions at 5 TeV centre-of-mass energy is shown for each LHC fill as a function of time in 2015. An online calibration based on Monte Carlo estimates has been used to set the luminosity scale.	pdf file

Luminosity summary plots for 2015 PbPb data taking

These plots show the estimated integrated luminosity of the PbPb collisions at 5 TeV per nucleon. The luminosity shown is a preliminary estimation based on van-der-Meer beam-separation scans.

Total Integrated Luminosity in 2015 Cumulative luminosity versus time delivered to (dark blue) and recorded by ATLAS (light blue) during stable beams for PbPb collisions at 5 TeV centre-of-mass energy per nucleon in 2015. The delivered luminosity accounts for luminosity delivered from the start of stable beams until the LHC requests ATLAS to put the detector in a safe standby mode to allow for a beam dump or beam studies. The recorded luminosity reflects the DAQ inefficiency, as well as the inefficiency of the so-called ‘warm start’: when the stable beam flag is raised, the tracking detectors undergo a ramp of the high-voltage and, for the pixel system, turning on the preamplifiers. Shown is the luminosity as determined from counting rates measured by the luminosity detectors. These detectors have been calibrated with the use of the van-der-Meer beam-separation method, where the two beams are scanned against each other in the horizontal and vertical planes to measure their overlap function.	pdf file
Integrated Luminosity by Day in 2015 Integrated luminosity per day time delivered to (green) and recorded by ATLAS (yellow) during stable beams for PbPb collisions at 5 TeV centre-of-mass energy per nucleon in 2015. The data shown is identical to the data shown above, except not cumulative over the year.	pdf file
Peak Luminosity per Fill in 2015 The peak instantaneous luminosity delivered to ATLAS during stable beams for PbPb collisions at 5 TeV centre-of-mass energy per nucleon is shown for each LHC fill as a function of time in 2015. The luminosity is determined using counting rates measured by the luminosity detectors, and is based on a preliminary calibration determined using van-der-Meer beam-separation scans.	pdf file
Peak Interactions per Crossing in 2015 The maximum number of inelastic collisions per beam crossing (µ) during stable beams for PbPb collisions at 5 TeV centre-of-mass energy per nucleon is shown for each fill in 2015. The preliminary luminosity measurement is used to determine the number of interactions per beam crossing as µ = Lbunch x σinel / fr where Lbunch is the per-bunch instantaneous luminosity, σinel is the inelastic PbPb cross-section at 5 TeV, which is taken to be 7.7 barns, and fr is the LHC revolution frequency of 11.245 kHz. The number of interactions shown is averaged over all colliding bunch pairs, and only the peak value per fill during stable beams is shown.	pdf file

Luminosity Measurement Based on Pixel Clusters (2016)

Typical distribution of the pixel-cluster size in the direction parallel to the beam axis, in the secondto-last forward inner layer (IBL) module Typical distribution of the pixel-cluster size in the direction parallel to the beam axis, in the secondto-last forward inner layer (IBL) module. The IBL is a cylinder that consists of 14 azimuthal “staves”. Each stave contains 20 modules arranged along the beam axis and covers the pseudorapidity range |eta| < 3. The 12413 clusters that populate this plot originate from 10433 randomly-triggered events during ATLAS physics data-taking in 2015. The distribution is fit to the sum of a Gaussian signal (mean from fit is 9-pixels cluster length), plus an exponentially-falling background of shorter clusters. The Gaussian area is proportional to the number of charged particles originating from the luminous region and therefore proportional to the luminosity integrated during the approximately one-minute data-taking period. The exponential area contains contributions from secondary interactions and afterglow that will deviate from proportionality to luminosity, and is therefore treated as a background.	pdf file eps file
Comparison of longitudinal cluster-size distributions for the four most forward modules Comparison of longitudinal cluster-size distributions for the four most forward modules in an arbitrarily chosen inner layer (IBL) stave. The IBL is a cylinder that consists of 14 azimuthal “staves”, each of which contains 20 modules arranged along the beam axis and covers the pseudorapidity range |eta| < 3. The modules farther from the nominal collision point produce, on the average, longer clusters, while the shape of the falling background is approximately the same in all modules. This confirms that the length of signal clusters is sensitive to the particle incidence angle, as expected from simple geometrical arguments.	pdf file eps file
Afterglow in the IBL During LHC operation, the IBL detector material is activated by pp collision debris. The resulting low energy decay products, collectively known as afterglow, induce delayed signals in the detector and produce single or small pixel clusters, thereby contributing to the background component of the cluster-length distributions rather than to the Gaussian-shaped long-cluster signal. The figure displays the bunch-slot dependence of the signal and background components, which correspond to, respectively, the area under the Gaussian curve and that under the falling exponential. These signal and background levels are extracted from fits to the cluster-length distributions from a forward IBL module, recorded in 8 consecutive 25 ns-long bunch slots. Only the first slot (numbered 2674) contained a colliding-bunch pair (and therefore a luminosity signal); the remaining 7 were nominally empty. The measured signal (Gaussian) component is largest in the first bunch slot, and drops by 4 orders of magnitude within 25 ns. The measured background (exponential) component, in contrast, decays much more slowly, with a time dependence suggestive of a mixture of radioactive decays. We have not attempted to identify those decays in this study.	pdf file eps file
Azimuthal dependence of the long-cluster (Gaussian) signal for the forward-most modules of the IBL. Azimuthal dependence of the long-cluster (Gaussian) signal for the forward-most modules of the IBL. The IBL is a cylinder that consists of 14 azimuthal staves, each of which contains 20 modules arranged along the beam axis and covers the pseudorapidity range |eta|<3. The sinusoidal dependence arises because in the plane perpendicular to the average beam direction, the luminous region is not perfectly centered on the IBL axis. In order to avoid being affected by occasional underperforming or noisy modules, the measured azimuthal dependence of the long-cluster signal is fit to the function A*cos((2*pi/14)*x + B)+C. Outliers are excluded from the fit on the basis of internal consistency. In this example, the 12th module was inefficient during the run considered; it was excluded form the fit based on its residual exceeding 4 sigma. The area under the fitted curve (rather than the sum of the 14 individual measurements) is used as a measure of the total number of signal clusters.	pdf file eps file
Time evolution, during an ATLAS run, of the longitudinal position of the luminous region Time evolution, during an ATLAS run, of the longitudinal position of the luminous region either as determined from the average position of reconstructed pp-collision vertices (light blue circles), or as inferred from the forward-backward asymmetry of the pixel-cluster counts in the IBL (black squares). This asymmetry is computed from the long-cluster signals in the 4 outermost IBL modules on either side of the interaction point. It is sensitive to the longitudinal position of the luminous region because the acceptance of each module depends on its distance from the average collision point. The pixel-cluster-based luminosity measurement can be corrected for this geometric effect by using the beamspot position derived from the measured asymmetry of the pixel-cluster signal.	pdf file eps file
Time evolution, during an ATLAS run, of the pixel-cluster luminosity signal Time evolution, during an ATLAS run, of the pixel-cluster luminosity signal normalized to the luminosity as measured by the ATLAS baseline luminometer (top), and of the RMS luminous length inferred from the longitudinal distribution of reconstructed pp-collision vertices (bottom). The luminosity-normalized pixel-cluster signal exhibits a similar time dependence to that of the luminous length, because the acceptance of each module depends on its distance from the corresponding interaction vertex. The pixel-cluster-based luminosity measurement must therefore be corrected for this geometric effect, using the luminous length derived from the longitudinal distribution of pp-collision vertices.	pdf file eps file
Comparison of the pixel-cluster counting (PCC) algorithm and the LUCID_EvtORA_Bi, TILE, and track-counting algorithms Fractional difference in run-integrated luminosity between the pixel-cluster counting (PCC) algorithm and the LUCID_EvtORA_Bi, TILE, and track-counting algorithms, for the subset of ATLAS runs with 25 ns bunch spacing for which the PCC data are available. The absolute scale of the PCC-based luminosity is cross-calibrated to the luminosity from the comparison algorithm averaged over the runs taken from 11 to 13 September 2015.	pdf file eps file
Fractional deviation of the bunch-averaged pile-up parameter average mu Fractional deviation of the bunch-averaged pile-up parameter average mu, obtained using different algorithms, from the pixel-cluster counting (PCC) value, as a function of average mu during a physics run on September 25, 2015. The data are normalized such that all algorithms yield the same integrated luminosity in the run considered.	pdf file eps file

Responsible: EricTorrence
Subject: public