|
|
ATLAS Collaboration(Aad, G. et al), Amos, K. R., Aparisi Pozo, J. A., Bailey, A. J., Cabrera Urban, S., Cardillo, F., et al. (2022). Measurements of azimuthal anisotropies of jet production in Pb collisions at root(NN)-N-s=5.02 TeV with the ATLAS detector. Phys. Rev. C, 105(6), 064903–25pp.
Abstract: The azimuthal variation of jet yields in heavy-ion collisions provides information about the path-length dependence of the energy loss experienced by partons passing through the hot, dense nuclear matter known as the quark-gluon plasma. This paper presents the azimuthal anisotropy coefficients v(2), v(3), and v(4) measured for jets in Pb + Pb collisions at root(NN)-N-s =5.02 TeV using the ATLAS detector at the LHC. The measurement uses data collected in 2015 and 2018, corresponding to an integrated luminosity of 2.2 nb(-1). The v(n) values are measured as a function of the transverse momentum of the jets between 71 and 398 GeV and the event centrality. A nonzero value of v(2) is observed in all but the most central collisions. The value of v(2) is largest for jets with lower transverse momentum, with values up to 0.05 in mid-central collisions. A smaller, nonzero value of v(3) of approximately 0.01 is measured with no significant dependence on jet p(T) or centrality, suggesting that fluctuations in the initial state play a small but distinct role in jet energy loss. No significant deviation of v(4) from zero is observed in the measured kinematic region.
|
|
|
|
ATLAS Collaboration(Aad, G. et al), Alvarez Piqueras, D., Aparisi Pozo, J. A., Bailey, A. J., Barranco Navarro, L., Cabrera Urban, S., et al. (2020). Transverse momentum and process dependent azimuthal anisotropies in root S-NN=8.16 TeV p plus Pb collisions with the ATLAS detector. Eur. Phys. J. C, 80(1), 73–31pp.
Abstract: The azimuthal anisotropy of charged particles produced in sNN=8.16TeV p+Pb collisions is measured with the ATLAS detector at the LHC. The data correspond to an integrated luminosity of 165 nb-1 that was collected in 2016. Azimuthal anisotropy coefficients, elliptic v2 and triangular v3\, extracted using two-particle correlations with a non-flow template fit procedure, are presented as a function of particle transverse momentum (pT) between 0.5 and 50 GeV. The v2 results are also reported as a function of centrality in three different particle pTintervals. The results are reported from minimum-bias events and jet-triggered events, where two jet pT thresholds are used. The anisotropies for particles with pT less than about 2 GeV are consistent with hydrodynamic flow expectations, while the significant non-zero anisotropies for pT in the range 9-50 GeV are not explained within current theoretical frameworks. In the pTrange 2-9 GeV, the anisotropies are larger in minimum-bias than in jet-triggered events. Possible origins of these effects, such as the changing admixture of particles from hard scattering and the underlying event, are discussed.
|
|
|
|
ATLAS Collaboration(Aad, G. et al), Aparisi Pozo, J. A., Bailey, A. J., Cabrera Urban, S., Cardillo, F., Castillo Gimenez, V., et al. (2021). The ATLAS Fast TracKer system. J. Instrum., 16(7), P07006–61pp.
Abstract: The ATLAS Fast TracKer (FTK) was designed to provide full tracking for the ATLAS high-level trigger by using pattern recognition based on Associative Memory (AM) chips and fitting in high-speed field programmable gate arrays. The tracks found by the FTK are based on inputs from all modules of the pixel and silicon microstrip trackers. The as-built FTK system and components are described, as is the online software used to control them while running in the ATLAS data acquisition system. Also described is the simulation of the FTK hardware and the optimization of the AM pattern banks. An optimization for long-lived particles with large impact parameter values is included. A test of the FTK system with the data playback facility that allowed the FTK to be commissioned during the shutdown between Run 2 and Run 3 of the LHC is reported. The resulting tracks from part of the FTK system covering a limited eta-phi region of the detector are compared with the output from the FTK simulation. It is shown that FTK performance is in good agreement with the simulation.
|
|
|
|
ATLAS Collaboration(Aad, G. et al), Akiot, A., Amos, K. R., Aparisi Pozo, J. A., Bailey, A. J., Bouchhar, N., et al. (2023). Fast b-tagging at the high-level trigger of the ATLAS experiment in LHC Run 3. J. Instrum., 18(11), P11006–38pp.
Abstract: The ATLAS experiment relies on real-time hadronic jet reconstruction and b-tagging to record fully hadronic events containing b-jets. These algorithms require track reconstruction, which is computationally expensive and could overwhelm the high-level-trigger farm, even at the reduced event rate that passes the ATLAS first stage hardware-based trigger. In LHC Run 3, ATLAS has mitigated these computational demands by introducing a fast neural-network-based b-tagger, which acts as a low-precision filter using input from hadronic jets and tracks. It runs after a hardware trigger and before the remaining high-level-trigger reconstruction. This design relies on the negligible cost of neural-network inference as compared to track reconstruction, and the cost reduction from limiting tracking to specific regions of the detector. In the case of Standard Model HH -> b (b) over barb (b) over bar, a key signature relying on b-jet triggers, the filter lowers the input rate to the remaining high-level trigger by a factor of five at the small cost of reducing the overall signal efficiency by roughly 2%.
|
|
|
|
ATLAS Collaboration(Aad, G. et al), Aparisi Pozo, J. A., Bailey, A. J., Cabrera Urban, S., Castillo, F. L., Castillo Gimenez, V., et al. (2020). Operation of the ATLAS trigger system in Run 2. J. Instrum., 15(10), P10004–59pp.
Abstract: The ATLAS experiment at the Large Hadron Collider employs a two-level trigger system to record data at an average rate of 1 kHz from physics collisions, starting from an initial bunch crossing rate of 40 MHz. During the LHC Run 2 (2015-2018), the ATLAS trigger system operated successfully with excellent performance and flexibility by adapting to the various run conditions encountered and has been vital for the ATLAS Run-2 physics programme For proton-proton running, approximately 1500 individual event selections were included in a trigger menu which specified the physics signatures and selection algorithms used for the data-taking, and the allocated event rate and bandwidth. The trigger menu must reflect the physics goals for a given data collection period, taking into account the instantaneous luminosity of the LHC and limitations from the ATLAS detector readout, online processing farm, and offline storage. This document discusses the operation of the ATLAS trigger system during the nominal proton-proton data collection in Run 2 with examples of special data-taking runs. Aspects of software validation, evolution of the trigger selection algorithms during Run 2, monitoring of the trigger system and data quality as well as trigger configuration are presented.
|
|
