AtlasPublicTopicHeader.png

Approved plots for the EF Tracking project

Introduction


Approved plots that can be shown by ATLAS speakers at conferences and similar events.
Please do not add figures on your own. Contact the responsible project leader in case of questions and/or suggestions.

EF Tracking studies

ATL-COM-DAQ-2021-038 Stub Filtering and NN Fake/Overlap rejection performance

Stub filtering: number of clusters per eta region

Number of silicon hit clusters remaining after three different stub-filtering scenarios, for 1000 events of single muon simulation in the ITk with 200 pileup interactions overlaid, in the 0.1< η <0.3, 0.3< φ <0.5 region.


png pdf

Stub filtering: number of clusters per eta region, combined

Median number of silicon hit clusters remaining after three different stub-filtering scenarios, for 1000 events of single muon simulation in the ITk with 200 pileup interactions overlaid, in the 0.1 < η < 0.3, 0.7 < η < 0.9 and 2.0 < η < 2.2 regions (all with 0.3 < φ < 0.5). The ranges given are ± 1 σ from the median, i.e. including 68% of events.


png pdf

Stub filtering: number of clusters per layer per eta region

Average number of silicon hit clusters remaining in each logical layer after three different stub-filtering scenarios, for 1000 events of single muon simulation in the ITk with 200 pileup interactions overlaid, in the 0.1 < η < 0.3, 0.3 < φ < 0.5 region.


png pdf

Stub filtering: track candidate efficiency vs $p_\mathrm{T}$

Truth-matched track candidate efficiency as a function of muon $p_\mathrm{T}$, for three different stub-filtering scenarios followed by the Hough Transform, for 100k events of single muon simulation in the ITk with no pileup interactions, in the (a) 0.7 < η < 0.9 and (b) 0.1 < η < 0.3 regions (both with 0.3 < φ < 0.5). With no stub filtering, a tight selection requiring clusters from 7 out of 8 layers to fall in the same accumulator bin is imposed, while this can be loosened to 6 out of 8 layers in the stub filtering case to regain efficiency.



png, a pdf, a png, b pdf, b

Stub filtering: radiation damage emulation

Truth-matched track-candidate efficiency as a function of muon $p_\mathrm{T}$, with and without medium stub filtering, followed by the Hough Transform, with varying levels of emulated radiation damage (0, 2 and 5% of clusters removed at random, uniformly over the detector) for 100k events of single muon simulation in the ITk with no pileup interactions, in the region 0.1 < η < 0.3, 0.3 < φ < 0.5. With no stub filtering, a tight selection requiring clusters from 7 out of 8 layers to fall in the same accumulator bin is imposed, while this can be loosened to 6 out of 8 layers in the stub filtering case, resulting in similar overall sensitivity to this emulated radiation damage.


png pdf

Stub filtering: impact on Hardware Track Trigger

Truth-matched track efficiency (following the removal of duplicate track candidates) as a function of muon $p_\mathrm{T}$, for three different stub-filtering scenarios followed by the Hardware Track Trigger, for 100k events of single muon simulation in the ITk with no pileup interactions, in the 0.1 < η < 0.3, 0.3 < φ < 0.5 region.


png pdf

ROC Curves

Performance of the neural network (NN) based fake and overlap removal algorithms, in terms of track candidate efficiency versus the number of track candidates remaining, in the 0.1 < η < 0.3, 0.3 < φ < 0.5 region, in single muon simulation overlaid with $t\bar{t}$ plus 200 pileup interactions. Efficiency is the number of track candidates (identified by the Hough Transform) matched to truth tracks, relative to the number of truth tracks, where these truth tracks are in both cases required to match offline-reconstructed tracks and can arise from all particles in the event; two tracks match if at least 50% of their hits are shared. Both offline and truth tracks have $p_\mathrm{T}$ > 1 GeV. Results with and without stub filtering ("medium" level, and with the associated reduction in HT threshold as described earlier) are included.


png pdf

Fake and overlap rejection vs $\mathrm{p}_T$

Average percentage of Hough Transform identified track candidates retained after the application of two neural networks (NN), as a function of $p_{\text{T}}$, in the 0.1 < η < 0.3, 0.3 < φ < 0.5 region, in single muon events overlaid with $t\bar{t}$ plus 200 pileup interactions. "Hough Transform + NN Fake" refers to results after the application of an NN-based fake removal algorithm to all track candidates from the Hough Transform (with a threshold of 0.1 on the classifier). "Hough Transform + NN Fake + NN Overlap" refers to results after the further application of an NN-based overlap removal step with a threshold of 5 hits.


png pdf

Number of track candidates, with and without stub-filtering

Distribution of the number of track candidates per event with and without stub filtering ("medium" level) in the 0.1 < η < 0.3, 0.3 < φ < 0.5 region, in single muon simulation overlaid with $t\bar{t}$ plus 200 pileup interactions. The results are after applying a neural network (NN) based fake removal algorithm and a NN based overlap removal step with a threshold of 5 hits on all track candidates from the Hough Transform step. The NNs are retrained for events with and without stub filtering, and similar track candidate efficiencies are observed for both scenarios.


png pdf

ATL-COM-DAQ-2022-052 Neural Network fake rejection and duplicate removal for HL-LHC trigger tracking

Track reconstruction efficiency for a neural network (NN) based fake and overlap removal algorithm as a function of $p_T$ for $0.1<\eta<0.3$ The efficiencies are computed relative to the offline track reconstruction. “Hough Transformation (HT) only” refers to efficiency of the Hough Transformation algorithm step, while “HT & NN” refers to the efficiency after application of a neural network (NN) based fake removal algorithm (with a threshold of 0.005 on the classifier), and a NN based overlap removal step with a threshold of 5 hits. The average efficiency across the full range is provided in the legend. Detailed information on the HT and NN can be found in Ref. [1]


png pdf eps

Distribution of the number of track candidates per event using hits for $0.1<\eta<0.3$ “Hough Transformation (HT)” refers to number of track candidates after the Hough Transformation (HT) algorithm step, “HT + NN Fake” refers to results after the application of a neural network (NN) based fake removal algorithm (with a threshold of 0.005 on the classifier) and “HT + NN Fake + NN Overlap” refers to results after a further application of a NN based overlap removal step with a threshold of 5 hits. The average average number of tracks per event is provided in the legend. Detailed information on the HT and NN can be found in Ref. [1]


png pdf eps

Number of Fake tracks in the event retained after the application of two neural networks (NN), as a function of $p_{T}$, in the $0.1<\eta<0.3$, $0.3<\phi<0.5$ in single muon events overlaid with $t\bar{t}$ plus 200 pileup interactions. “Hough Transform + NN Fake” refers to results after the application of an NN-based fake removal algorithm to all track candidates from the Hough Transform (with a threshold of 0.005 on the classifier). “Hough Transform + NN Fake + NN Overlap” refers to results after the further application of an NN-based overlap removal step with a threshold of 5 hits. Detailed information on the HT and NN can be found in Ref. [1]


png pdf eps



Major updates:
-- BenedettoGorini - 2022-01-13

Responsible: BenedettoGorini
Subject: public


Latex rendering error!! dvi file was not created.

Edit | Attach | Watch | Print version | History: r3 < r2 < r1 | Backlinks | Raw View | WYSIWYG | More topic actions
Topic revision: r3 - 2022-06-30 - BenedettoGorini
 
    • Cern Search Icon Cern Search
    • TWiki Search Icon TWiki Search
    • Google Search Icon Google Search

    Atlas All webs login

This site is powered by the TWiki collaboration platform Powered by PerlCopyright &© 2008-2023 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
or Ideas, requests, problems regarding TWiki? use Discourse or Send feedback