Difference: FTKPublicResults (22 vs. 23)

Revision 232019-04-30 - DavidMStrom

Line: 1 to 1
 
META TOPICPARENT name="TriggerPublicResults"
AtlasPublicTopicHeader.png
Line: 109 to 109
 shown for (black dots) the FTK slice, (shaded red histogram) functional emulation of the FTK slice using FTKSim, and (dashed line) FTK refit. A single Data Formatter (DF) board provides partial coverage of Tower22, which spans -1.5 < η < 0 and 1.6 < φ < 2.0. The plot covers a
Changed:
<
<
subset of 380,000 events from Run 364485, a special high pile-up run with average interactions per crossing μ = 82, collected in October
>
>
subset of 380,000 events from Run 364485, a special high pile-up run with average interactions per crossing μ = 82, collected in October
 2018. FTK tracks with Insertable B-layer (IBL) hits were excluded, due to a FTK module ordering problem that caused incorrect hit positions in the run. The cause is understood and the fix is being implemented. FTK tracks are matched to offline tracks within Δ R < 0.02.
Line: 118 to 118
 
png pdf
Added:
>
>
FTK vs. offline track pseudo-rapidity (η) residuals from an FTK slice. The difference between the FTK and matched offline track η are shown for (black dots) the FTK slice, (shaded red histogram) functional emulation of the FTK slice using FTKSim, and (dashed line) FTK refit. A single Data Formatter (DF) board provides partial coverage of Tower22, which spans -1.5 < η < 0 and 1.6 < φ < 2.0. The plot covers a subset of 380,000 events from Run 364485, a special high pile-up run with average interactions per crossing μ = 82, collected in October 2018. FTK tracks with Insertable B-layer (IBL) hits were excluded, due to a FTK module ordering problem that caused incorrect hit positions in the run. The cause is understood and the fix is being implemented. FTK tracks are matched to offline tracks within Δ R < 0.02.


png pdf

FTK vs. offline track azimuthal angle (φ) residuals from an FTK slice. The difference between the FTK and matched offline track ϕ are shown for (black dots) the FTK slice, (shaded red histogram) functional emulation of the FTK slice using FTKSim, and (dashed line) FTK refit. A single Data Formatter (DF) board provides partial coverage of Tower22, which spans -1.5 < η < 0 and 1.6 < φ < 2.0. The plot covers a subset of 380,000 events from Run 364485, a special high pile-up run with average interactions per crossing μ = 82, collected in October 2018. FTK tracks with Insertable B-layer (IBL) hits were excluded, due to a FTK module ordering problem that caused incorrect hit positions in the run. The cause is understood and the fix is being implemented. FTK tracks are matched to offline tracks within &Detla; R < 0.02.
png pdf
 
 
This site is powered by the TWiki collaboration platform Powered by PerlCopyright & 2008-2019 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback