Precision Luminosity of LHC Proton-Proton Collisions at 13 TeV Using Hit-Counting with TPX Pixel Devices
Andre Sopczak (Institute of Experimental, Applied Physics, Czech, Technical University in Prague), Babar Ali, Thanawat Asawatavonvanich, Jakub, Begera, Benedikt Bergmann, Thomas Billoud, Petr Burian, Ivan Caicedo, Davide, Caforio, Erik Heijne, Josef Janecek, Claude Leroy

TL;DR
This paper demonstrates that a network of Timepix pixel detectors can measure LHC proton-proton collision luminosity at 13 TeV with high precision and stability, using hit-counting techniques during 2015 data-taking.
Contribution
It introduces a stand-alone TPX pixel detector network for precise luminosity measurement and analyzes its performance during LHC 13 TeV collisions.
Findings
Achieved 0.1% short-term precision in 10 s intervals
Long-term stability below 0.5% over data-taking period
Validated the capability to monitor luminosity reduction accurately
Abstract
A network of Timepix (TPX) devices installed in the ATLAS cavern measures the LHC luminosity as a function of time as a stand-alone system. The data were recorded from 13 TeV proton-proton collisions in 2015. Using two TPX devices, the number of hits created by particles passing the pixel matrices was counted. A van der Meer scan of the LHC beams was analysed using bunch-integrated luminosity averages over the different bunch profiles for an approximate absolute luminosity normalization. It is demonstrated that the TPX network has the capability to measure the reduction of LHC luminosity with precision. Comparative studies were performed among four sensors (two sensors in each TPX device) and the relative short-term precision of the luminosity measurement was determined to be 0.1% for 10 s time intervals. The internal long-term time stability of the measurements was below 0.5% for the…
| Device | TPX clusters per unit sensor area and | |||
| (mm) | (mm) | per unit luminosity | ||
| Layer-1 | Layer-2 | |||
| TPX02 | 3540 | 1115 | 104 | 123 |
| TPX12 | -3540 | 1146 | 97 | 113 |
| TPX | Layer | ||||
|---|---|---|---|---|---|
| () | () | () | () | ||
| 02 | 1 | 130.2 | 117.7 | 116.8 | 1495 |
| 02 | 2 | 130.2 | 118.6 | 115.9 | 2386 |
| 12 | 1 | 128.7 | 118.1 | 117.8 | 1386 |
| 12 | 2 | 128.3 | 118.7 | 117.5 | 2298 |
| Device | Layer | |
|---|---|---|
| (hits/) | ||
| TPX02 | 1 | 544.8 |
| TPX02 | 2 | 876.1 |
| TPX12 | 1 | 500.9 |
| TPX12 | 2 | 832.2 |
| Date | Fill | Start time | Colliding | |||||
|---|---|---|---|---|---|---|---|---|
| in 2015 | (unix time) | bunches | ||||||
| 29 Sep. | 4440 | 1443525360 | 1650 | 3360 | 24.8 | 1453 | 0.2815 | 0.1833 |
| 2-3 Oct. | 4449 | 1443785520 | 1607 | 3240 | 26.0 | 1453 | 0.2787 | 0.1615 |
| 6-7 Oct. | 4467 | 1444149360 | 1729 | 3700 | 24.1 | 1596 | 0.2958 | 0.1873 |
| 9-11 Oct. | 4479 | 1444427640 | 1950 | 4240 | 24.6 | 1813 | 0.3006 | 0.2194 |
| 30-31 Oct. | 4557 | 1446221040 | 2388 | 4450 | 24.7 | 2232 | 0.2576 | 0.1840 |
| 31 Oct.-1 Nov. | 4560 | 1446311100 | 2610 | 5020 | 24.5 | 2232 | 0.2659 | 0.1859 |
| Frames | (%) | |||||||
|---|---|---|---|---|---|---|---|---|
| used | TPX02 | TPX12 | TPX02 | TPX12 | ||||
| Layer-1 | Layer-2 | Layer-1 | Layer-2 | Layer-1 | Layer-2 | Layer-1 | Layer-2 | |
| 1 | 0.36 | 0.35 | 0.37 | 0.36 | 1.27 | 1.58 | 1.28 | 1.57 |
| 10 | 0.13 | 0.13 | 0.15 | 0.13 | 1.47 | 1.87 | 1.61 | 1.82 |
| 20 | 0.11 | 0.10 | 0.13 | 0.11 | 1.71 | 2.04 | 1.96 | 2.12 |
| 30 | 0.10 | 0.09 | 0.11 | 0.10 | 1.96 | 2.18 | 2.17 | 2.40 |
| 40 | 0.09 | 0.08 | 0.11 | 0.09 | 2.13 | 2.39 | 2.24 | 2.56 |
| Frames | (%) | |||
|---|---|---|---|---|
| used | TPX02 | TPX12 | TPX02 | TPX12 |
| 1 | 0.30 | 0.30 | 1.50 | 1.57 |
| 10 | 0.11 | 0.12 | 1.76 | 1.94 |
| 20 | 0.09 | 0.10 | 1.96 | 2.36 |
| 30 | 0.08 | 0.09 | 2.21 | 2.56 |
| 40 | 0.08 | 0.09 | 2.35 | 2.88 |
| Frames | (%) | |||
|---|---|---|---|---|
| used | TPX02 | TPX12 | TPX02 | TPX12 |
| 1 | 0.41 | 0.41 | 1.15 | 1.12 |
| 10 | 0.16 | 0.17 | 1.44 | 1.45 |
| 20 | 0.14 | 0.14 | 1.66 | 1.66 |
| 30 | 0.12 | 0.13 | 1.89 | 2.04 |
| 40 | 0.11 | 0.13 | 1.95 | 2.09 |
| TPX | Slope | Slope | Slope | Slope |
|---|---|---|---|---|
| () | () | (%/100d) | (%/100d) | |
| 02 | 1.71 | 0.15 | ||
| 12 | 1.62 | 0.14 |
| TPX | Slope | Slope | Slope | Slope |
| () | () | (%/100d) | (%/100d) | |
| 02/12 | 0.25 | 0.89 | 0.02 | 0.08 |
Peer Reviews
No public reviews on file for this paper yet. If you reviewed it on a platform where reviews are public (OpenReview, ICLR, NeurIPS, ICML), you can paste yours below so the community can read it here.
Videos
No videos yet. Explain this paper in a talk, walkthrough, or lecture? Add one.
Taxonomy
TopicsParticle Detector Development and Performance · Particle physics theoretical and experimental studies · Dark Matter and Cosmic Phenomena
**Precision Luminosity of LHC Proton-Proton Collisions at 13 TeV Using Hit-Counting with TPX Pixel Devices **
**André Sopczak1, Babar Ali1, Thanawat Asawatavonvanich1,
Jakub Begera1, Benedikt Bergmann1, Thomas Billoud2, Petr Burian1, Ivan Caicedo1, Davide Caforio1, Erik Heijne1, Josef Janeček1,
Claude Leroy2, Petr Mánek1, Kazuya Mochizuki2, Yesid Mora1, Josef Pacík1, Costa Papadatos2, Michal Platkevič1, Štěpán Polanský1, Stanislav Pospíšil1, Michal Suk1, Zdeněk Svoboda1
**
1Institute of Experimental and Applied Physics, Czech Technical University in Prague, Czech Republic
2Group of Particle Physics, University of Montreal, Canada
Abstract
A network of Timepix (TPX) devices installed in the ATLAS cavern measures the LHC luminosity as a function of time as a stand-alone system. The data were recorded from 13 TeV proton-proton collisions in 2015. Using two TPX devices, the number of hits created by particles passing the pixel matrices was counted. A van der Meer scan of the LHC beams was analysed using bunch-integrated luminosity averages over the different bunch profiles for an approximate absolute luminosity normalization. It is demonstrated that the TPX network has the capability to measure the reduction of LHC luminosity with precision. Comparative studies were performed among four sensors (two sensors in each TPX device) and the relative short-term precision of the luminosity measurement was determined to be 0.1% for 10 s time intervals. The internal long-term time stability of the measurements was below 0.5% for the data-taking period.
Presented at the IEEE 2016 Nuclear Science Symposium, Strasbourg, France
Abstract
A network of Timepix (TPX) devices installed in the ATLAS cavern measures the LHC luminosity as a function of time as a stand-alone system. The data were recorded from 13 TeV proton-proton collisions in 2015. Using two TPX devices, the number of hits created by particles passing the pixel matrices was counted. A van der Meer scan of the LHC beams was analysed using bunch-integrated luminosity averages over the different bunch profiles for an approximate absolute luminosity normalization. It is demonstrated that the TPX network has the capability to measure the reduction of LHC luminosity with precision. Comparative studies were performed among four sensors (two sensors in each TPX device) and the relative short-term precision of the luminosity measurement was determined to be 0.1% for 10 s time intervals. The internal long-term time stability of the measurements was below 0.5% for the data-taking period.
I Introduction
A TPX detector network [1] of sixteen devices was installed in the ATLAS cavern at CERN. Each TPX device consists of two stacked hybrid silicon pixel sensors. The silicon sensors have a matrix of pixels of pitch, and thickness of (further indicated as layer-1) and (layer-2) [2]. The readout chips connected to these sensors have the original Timepix design [3, 4]. The installation of the TPX devices took place during the LHC shutdown transition from Run-1 to Run-2 in 2013/2014. These double-layer TPX devices replaced the previously operational network that employed single-layer Medipix (MPX) assemblies [5, 6].
These devices measure the primary and secondary particle fluxes resulting from 13 TeV proton-proton collisions. The data were taken in 2015 during the first year of LHC Run-2 operation. Precision luminosity measurements are of particular importance for many physics analyses in high-energy physics.
The use of the TPX network for luminosity measurements has several advantages compared to the previous luminosity measurements [7] at LHC during Run-1 that used MPX devices. Regarding the luminosity monitoring, the two-layer hodoscope structure of the TPX devices doubles the measurement statistics and allows one to determine the precision and long-term time stability of individual TPX devices. The dead-time caused by the readout was reduced from about 6 s to 0.12 s allowing a much higher data acquisition rate. Also, the TPX devices are operated in three different modes [3, 4]: hit-counting, time-over-threshold (energy deposits and cluster-counting), and time-of-arrival (cluster-counting). Furthermore, the proton-proton collision energy increased from 8 TeV at LHC during Run-1 to 13 TeV at Run-2 which opened a new energy frontier for luminosity measurements in colliders.
The TPX network is self-sufficient for luminosity monitoring. It collects data independently of the ATLAS data-recording chain, and provides independent measurements of the bunch-integrated LHC luminosity. In particular, van der Meer (vdM) scans [8] can be used for absolute luminosity calibration.
The detection of charged particles in the TPX devices is based on the ionization energy deposited by particles passing through the silicon sensor. The signals are processed and digitized during an adjustable exposure time (frame acquisition time) for each pixel. Neutral particles, namely neutrons, however, need to be converted to charged particles before they can be detected. Therefore, a part of each silicon sensor is covered by 6LiF and polyethylene converters [9, 2].
Thirteen out of the sixteen installed devices have been used for the luminosity analysis. Two devices were found to be inoperational after the closing of the ATLAS detector and one device was intentionally located far away from the interaction point and therefore it was unusable for luminosity measurements. Table I lists the locations of the devices TPX02 and TPX12 used in this analysis, and their numbers of registered passing particles (clusters). It is noted that the number of clusters for the sensor is about 20% larger compared to the sensor. This percentage is lower than might be expected from the 40% larger sensitive volume, because the extended clusters induced by a single particle count only ‘one’ in the thin as well as in the thick sensor. The number of photon conversions and fast neutron interactions, however, will increase with the sensitive volume. The analysis described in this article is focused on the precision luminosity determination with the devices TPX02 and TPX12, which are operated with 1 s exposure time and analysed in hit-counting mode. As their positions are very similar in and coordinates on opposite sides of the proton-proton interaction point, their count rates are very similar. During 2015 LHC proton-proton collisions typical luminosities were 3-5 3000-5000 and the TPX count rate was a few hits/s per frame.
Figure 1 shows an example of the luminosity from hit-counting measured with TPX02 layer-2 for LHC fill 4449, taken on 2-3 October 2015. All times are in GMT.
This article is structured as follows. First, the concept of LHC luminosity monitoring from TPX hit-counting is introduced in Section II. The vdM scan analysis based on hit-counting (Section III) is summarized for an absolute luminosity calibration. In Section IV the LHC luminosity curve is determined by using the concept of averaged interactions per bunch-crossing, together with the TPX measurement precision. Section V describes the luminosity precision by evaluation of the difference between two layers of the same TPX device. The long-term luminosity precision is given in Section VI from the comparison of layer-1 and layer-2 luminosity of the same TPX device. The long-term luminosity precision from different TPX devices is given in Section VII. Finally, conclusions are given in Section VIII.
II LHC Luminosity from TPX Hit-Counting
The data from the TPX02 and TPX12 devices were used in hit-counting mode, both having similar count rates as specified in Table I. The devices measure the luminosity independently and their measurements are cross-checked with each other. A constant exposure time of 1 s was used for the entire 2015 data-taking.
A small number of pixels becoming weak or noisy (e.g. due to radiation damage) could have a significant effect on the luminosity measurement. Therefore, pixels with a count rate that is at least away from the mean, are excluded for each sensor region (uncovered and with converters). This requirement identifies about 7-13% of the pixels on layer-1 and layer-2 both for TPX02 and TPX12 per LHC fill, including 5-10% of pixels at the boundaries of the sensor regions and edges of the sensor matrix. Then, the logical OR of identified pixels per LHC fill was taken for all 2015 LHC fills to remove 19-22% of the total number of pixels of the sensors. The effect of the pixel removal on the analysis was also studied with and criteria, with the result that the analysis outcome regarding the LHC luminosity curve, measurement precision and long-term stability remained unchanged.
The hit rate for the four TPX sensors is normalized to units of luminosity by multiplying with a scaling factor as given in Section III.
The induced radioactivity of material in the ATLAS cavern has no significant effect on the luminosity determination as determined by a dedicated study.
The ATLAS and CMS collaborations have elaborate systems of luminosity measurements, described in [10], [11] (ATLAS) and [12], [13] (CMS). A comparative study of their results and the TPX luminosity monitoring is beyond the scope of this article.
In addition to the hit-counting, luminosity can be measured with the two other modes of TPX operation based on cluster-counting and summed energy deposits. These luminosity measurements will be addressed in a separate publication.
The relation between the number of hits and clusters (particles) is investigated in order to determine the statistical uncertainty of the luminosity measurement from hit-counting. The average ratio of hits per cluster is approximately , which was obtained with TPX data from a low-intensity LHC fill for which the clusters on the sensors were well separated. This factor is used for the statistical uncertainty determination in the following sections assuming that one cluster corresponds to one independent particle passing the device [7].
III Van der Meer Scans
Van der Meer (vdM) scans are used for absolute luminosity calibration at the LHC. This scan technique was pioneered by Simon van der Meer at CERN in the 1960s [8] to determine the luminosity calibration in a simple way. It involves scanning the LHC beams through one another to determine their sizes in terms of the horizontal and vertical widths of the beams at the point of collision. These width measurements are then combined with information of the number of circulating protons, allowing the determination of an absolute luminosity scale. The vdM scan analysis is based on the data taken on 24-25 August 2015 using TPX02 and TPX12 layer-1 and layer-2.
The LHC beam separation dependence of the measured TPX luminosity is well represented by the sum of a single Gaussian and a constant (Fig. 2). The absolute luminosity normalization is derived from the combination of the hit rate, the horizontal and vertical convoluted widths and the average bunch currents.
The measurement uncertainty of the TPX devices can be determined with respect to the expected statistical uncertainty. For this study, the pull distributions, as defined by (data-fit)/, were determined, where , and . Figure 3 shows the pull distribution for the first horizontal vdM scan in August 2015, as seen by TPX02 layer-2. The sigma of the pull distribution averaged over TPX02 and TPX12, layer-1 and layer-2 for both horizontal and vertical scans is , which indicates that additional uncertainties are present beyond the determined statistical uncertainties, or correlations in the statistical evaluation have a significant effect as discussed in Ref. [7]. Furthermore, transverse proton-bunch profiles are not expected to be perfectly Gaussian; and even if they were, a scan curve summed over Gaussian bunches of different widths would not be strictly Gaussian. Therefore, non-Gaussian contributions to the vdM-scan curves may contribute, at some level, to the widening of the pull distribution.
For TPX02 layer-2, the widths of the beam sizes (horizontal and vertical nominal beam separations) and their statistical uncertainties are and , respectively.
The luminosity can be calculated as:
[TABLE]
where is the number of bunch crossings producing collisions per machine revolution, and are the average bunch populations (number of protons) in beam 1 and beam 2, respectively, is the machine revolution frequency (11245.5 Hz), and and are the convoluted horizontal and vertical beam sizes. The LHC parameters for fill 4266 are [14]:
- •
number of bunches: ;
- •
average number of protons (in units ) per bunch in beam 1 and in beam 2: and , respectively.
Thus, the resulting luminosity is .
The specific luminosity is defined as:
[TABLE]
Table II summarizes the scan results for the first pair of vdM scans (horizontal and vertical) registered with TPX02 and TPX12 for both their layers.
For TPX02 layer 2, the fits of horizontal and vertical scans provide and hits/s, respectively, at the peak above the background. The average number is () hits/s. Thus, the normalization factor between the TPX02 layer-2 hit rate and the instantaneous LHC luminosity is
[TABLE]
The normalization factors for the other devices were calculated using the same procedure, and the results are summarized in Table III.
As already noted for the previous LHC Run-1 vdM scan analysis using MPX devices [7], the normalization factor for the absolute luminosity is only approximate since the TPX exposure time is much longer than the bunch spacing. Therefore, the bunch-integrated luminosity averages over the different bunch profiles. In order to estimate the resulting uncertainty a simulation with 29 overlapping Gaussian distributions was performed [7], which led to an estimate of the resulting uncertainty on the normalization factor (from this source only) of about 1%.
Although further uncertainties could arise from non-Gaussian shapes, this study shows that the Gaussian approximation of the sum of Gaussians is quite robust with the TPX system and the luminosity approximation by bunch integration is a sensible approach. No attempt was made for a precise determination of the total uncertainty which would require a dedicated study [10, 11].
IV LHC Luminosity Curve and TPX Precision
The TPX network has the capability to study the LHC luminosity curve with precision. Six LHC fills of proton-proton collisions were investigated in detail. As an example, details are given for the LHC fill 4449, taken on 3 October 2015.
First, the TPX luminosity is calculated using the normalization factors from Table III and it is then converted to an average number of inelastic interactions per bunch crossing by
[TABLE]
where colliding bunches, Hz and the inelastic cross-section mb [15]. Accelerator simulations [16] have shown that under routine physics conditions ( m), elastic proton-proton scattering contributes negligibly to the particle-loss rate. This is because the typical scattering angle is so small compared to the natural angular divergence of the beam that the protons remain with the dynamic aperture of the ring.
IV-A Fitted LHC Luminosity Curve
In a simple approximation, the loss rate of protons in the colliding beam is governed by:
[TABLE]
where is the initial number of protons, and and are constants related to beam-beam (burning-off the proton bunches) and single bunch (e.g. beam-gas) interactions, respectively. This equation has a known solution, which is used as fit function:
[TABLE]
with two well-known border cases:
[TABLE]
[TABLE]
Next, the expected mean lifetime of inelastic beam-beam interactions is calculated from the LHC beam parameters, as given in Table IV, and used as a fixed parameter to determine . A simultaneous fit of and did not converge. As already noted in the previous LHC Run-1 analysis [7], and are strongly anti-correlated. Compared to the data-taking at Run-1, the Run-2 LHC luminosity curve is flatter, making the fit less sensitive to the fit parameters.
The mean lifetime from inelastic beam-beam interactions is given by [17]:
[TABLE]
where is the initial number of protons per bunch ( protons [14]). For LHC fill 4440 the initial luminosity is [14], the number of experiments is (ATLAS [18] and CMS [19]). For the lifetime is obtained, thus
[TABLE]
The value depends on the initial luminosity and the initial number of protons, thus on the starting value of for the first fit. Since , one can write . Thus for the lower initial luminosity in the fit, a longer lifetime is expected from beam-beam interactions and therefore a smaller
[TABLE]
The frequent LHC small-amplitude beam-separation scans for optimisation of the luminosity made it necessary to adapt the fit function. Therefore, the data during the scans is removed and the LHC luminosity curve is fitted with a function having the values of reduced by for each time period between the scans. The values are calculated for the starting values for each region between the scans, and is the value for the start of the LHC fill.
Six long LHC fills with large luminosity are investigated as given in Table IV. Figure 4 shows the fit of TPX02 layer-2 data for two of these LHC fills.
The fit results indicate that the LHC luminosity reduction is predominantly reduced by beam-beam interactions since a larger value of corresponds to a shorter lifetime. In order to determine the and its uncertainty, the fit is performed for the six LHC fills and the four sensors separately, resulting in a large single-bunch lifetime :
[TABLE]
where the average is taken over 24 measurements, and the uncertainty is given as the square root of the variance.
IV-B Precision
In order to investigate the precision of the TPX luminosity measurements, the difference between the fit and the data is studied as a function of time. As an example, the data is analysed from the last continuous LHC curve taken on 3 October 2015 for about 4.5 hours starting 0:45.
A precision of 0.35% has been obtained with TPX02 layer-2 and similarly with other TPX sensors, as listed in Table V. The given uncertainties result from statistical and systematic uncertainties by the TPX measurements convoluted with uncertainties arising from fluctuations in the proton-proton collision rates.
It is noted that the TPX measurement precision is statistically limited by the number of hits per frame. Therefore, 10, 20, 30 and 40 frames are grouped together. Consequently, the statistical precision significantly increases. Figure 5 shows the residuals for groups of 30 frames. The four distributions show no particular uniform structure and therefore no LHC luminosity variation at the 0.1% level. Table V lists the obtained precisions for TPX02 and TPX12 layer-1 and layer-2. The fit results using the data of the four sensors are consistent.
In order to increase the statistical significance of each TPX device the luminosity measured by layer-1 and layer-2 is averaged, and presented in Fig. 6 for 10 frames combined. It shows the relative difference between data and fitted average number of interactions per bunch crossing as a function of time, seen by TPX02. The corresponding Gaussian fit is shown in Fig. 7. Figure 8 shows the pull distribution assuming statistical uncertainties only. Table VI lists the obtained uncertainties and the corresponding pull values for 1 frame, as well as for 10, 20, 30 and 40 frames combined. The resulting relative short-term luminosity measurement precision is 0.1% for 10 s time intervals. As a consistency check of the obtained precision, the data from 7 October 2015 (LHC fill 4467) from 5:30 to 10:00 was analysed in the same way, reproducing the results on the precision. Thus, the resulting luminosity precision of the TPX system is higher compared to the previous MPX luminosity measurement precision (0.3% for 60 s time interval) [7] for data taken at LHC during Run-1 operation.
V Short-term Precision of Individual TPX Devices
In order to determine the short-term precision of individual TPX devices for luminosity measurements, the relative difference in luminosity measured by layer-1 and layer-2 of the same TPX device is studied as a function of time. The statistical precision is increased by grouping 10, 20, 30 and 40 frames. Figure 9 shows the fit results for 10 frames combined, while Fig. 10 shows the corresponding precision as the width of the Gaussian fit. The resulting pull distribution is shown in Fig. 11. For single frames the width of the pull distribution is about unity, indicating that the statistical uncertainty is dominant. The width of the pull distribution is increasing as more frames are combined in order to decrease the statistical uncertainty, and the pull values indicate that in addition systematic uncertainties are present.
Table VII lists the obtained precisions for TPX02 and TPX12. As the difference of two measurements (from layer-1 and layer-2) is calculated and the statistical significance of each measurement is about the same, the uncertainty of each measurement is about of overall uncertainty, thus leading to a measurement precision for each TPX device of approximately 0.1% for 10 s time intervals.
VI Long-term Stability of Individual TPX Devices
The long-term time stability of the luminosity monitoring is determined for individual TPX devices by comparing the luminosity measured by the two separate sensitive layers of TPX02 and TPX12. For this analysis the frames are grouped corresponding to time periods of the 2015 LHC fills with instantaneous luminosity above . A linear fit is applied to the (TPX layer-1)/(TPX layer-2) luminosity ratio versus time for the August to November 2015 data-taking period, as given in Fig. 12. The slope of the linear fit is taken as a measure of time stability. The uncertainty is obtained from the fit. As the statistical uncertainty of the ratio measurements for the grouped frames is much less than the systematic uncertainties, each ratio is given equal weight in the fit. The obtained slope values and their uncertainties for TPX02 and TPX12 are summarized in Table VIII. The slope shows that the luminosity ratio measured by layer-1 and layer-2 slightly decreases with time. This could indicate a small relative change in sensitivity with time between the thinner and thicker sensors. The time-stability of the luminosity measurements between individual layers is about 0.5% per 100 days.
In addition, a study of the internal calibration transfer was performed. As described in Section III the normalizations of the TPX sensors were performed with a vdM scan using LHC fill 4266 (24-25 August 2015) with a peak luminosity of . In the same LHC fill, the luminosity was kept constant after the vertical and horizontal scans for about 5 hours. Using the data of this time period the (TPX layer-1)/(TPX layer-2) luminosity ratio was determined with TPX02 and TPX12, and found to be in agreement with the ratios at high luminosity within 0.5% uncertainty.
VII Long-term Stability of Different TPX Devices
The long-term time stability of the luminosity monitoring is determined for two TPX devices located about 7 m apart at opposite sides of the primary proton-proton interaction point. First, the frames are grouped into luminosity blocks of about one minute. This grouping of frames is necessary for a comparative study as the start times of the frames are not synchronized between the TPX devices. Then, the luminosity blocks are grouped into time periods corresponding to the LHC fills with instantaneous luminosity above . The luminosity ratio measured by TPX02 and TPX12 is calculated and a linear fit is applied for the August to November 2015 data-taking period, as given in Fig. 13. The slope of the linear fit is taken as a measure of time stability. The obtained slope value and its uncertainty is summarized in Table IX. The uncertainty is obtained from the fit. As the statistical uncertainty of the ratio measurements for the grouped time intervals is much less than the systematic uncertainties, each ratio is given equal weight in the fit. The fluctuations are much larger than the slope of 0.02% per 100 days, therefore, the largest fluctuations are used as an estimate of the long-term time stability. These fluctuation could either result from the TPX operation, or from small variations in the complex LHC radiation field depending on small changes in the colliding beam optics. Thus, conservatively, the study of two different TPX devices indicates an internal time stability of the luminosity measurement below 0.5% per 100 days.
VIII Conclusions
The network of TPX devices installed in the ATLAS detector cavern has successfully taken data at LHC during Run-2 with 13 TeV proton-proton collisions. An approximate absolute luminosity calibration was determined from a vdM scan in 2015. The TPX network measured the LHC luminosity curve with precision indicating that the luminosity reduction from single-bunch interactions was much less than from beam-beam interactions. The relative short-term precision of the TPX luminosity measurements was determined to be 0.1% for 10 s time intervals, and the internal long-term stability of the TPX system for luminosity measurements was below 0.5% for the 2015 data-taking period.
Acknowledgment
The authors would like to thank warmly the ATLAS Luminosity Group for useful discussions and interactions, and the Medipix Collaboration for providing the TPX assemblies. The project is supported by the Ministry of Education, Youth and Sports of the Czech Republic under projects number LG 15052 and LM 2015058, and the Natural Sciences and Engineering Research Council of Canada (NSERC). Calibration measurements were performed at the Prague Van-de-Graaff accelerator funded by the Ministry of Education, Youth and Sports of the Czech Republic under project number LM 2015077.
The reference list from the paper itself. Each links out to its DOI / PubMed record.
- 1[1] C. Leroy, S. Pospisil, M. Suk, and Z. Vykydal, “Proposal to Measure Radiation Field Characteristics, Luminosity and Induced Radioactivity in ATLAS with TIMEPIX Devices,” Project Proposal [Online]. Available: http://cds.cern.ch/record/1646970, 2014.
- 2[2] B. Bergmann, I. Caicedo, C. Leroy, S. Pospisil, and Z. Vykydal, “ATLAS-TPX: a two-layer pixel detector setup for neutron detection and radiation field characterization,” JINST , vol. 11, p. P 10002, 2016.
- 3[3] X. Llopart, R. Ballabriga, M. Campbell, L. Tlustos, and W. Wong, “Timepix, a 65 k programmable pixel readout chip for arrival time, energy and/or photon counting measurements,” Nucl. Instr. Meth , vol. A 581, pp. 485–494, 2007.
- 4[4] ——, “Erratum: Timepix, a 65 k programmable pixel readout chip for arrival time, energy and/or photon counting measurements,” Nucl. Instr. Meth , vol. A 585, pp. 106–108, 2008.
- 5[5] Z. Vykydal, J. Bouchami, M. Campbell, Z. Dolezal, D. Fiederle, M. Greiffenberg et al. , “The Medipix 2 - based network for measurement of spectral characteristics and composition of radiation in ATLAS detector,” Nucl. Instr. Meth , vol. A 607, pp. 35–37, 2009.
- 6[6] M. Campbell, E. Heijne, C. Leroy, J.-P. Martin, G. Mornacchi, M. Nessi et al. , “Analysis of Radiation Field in ATLAS Using 2008-2011 Data from the ATLAS-MPX Network,” ATL-GEN-PUB-2013-001, 2013.
- 7[7] A. Sopczak, B. Ali, N. Asbah, B. Bergmann, K. Bekhouche, D. Caforio et al. , “MPX Detectors as LHC Luminosity Monitor,” IEEE Trans. Nucl. Sci. , vol. 62, pp. 3225–3241, 2015.
- 8[8] S. van der Meer, “Calibration of the effective beam height in the ISR,” ISR-PO/68-31 CERN Report, 1968.
