Difference: FTKPublicResults (1 vs. 24)

Revision 242019-05-09 - DavidMStrom

Line: 1 to 1
 
META TOPICPARENT name="TriggerPublicResults"
AtlasPublicTopicHeader.png
Line: 137 to 137
 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.
Changed:
<
<
The cause is understood and the fix is being implemented. FTK tracks are matched to offline tracks within &Detla; R < 0.02.
>
>
The cause is understood and the fix is being implemented. FTK tracks are matched to offline tracks within Δ R < 0.02.
 

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
 

Revision 222019-04-25 - DavidMStrom

Line: 1 to 1
 
META TOPICPARENT name="TriggerPublicResults"
AtlasPublicTopicHeader.png
Line: 19 to 19
 Distribution of track transverse momentum (pT) from an FTK slice. 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
Changed:
<
<
average interactions per crossing ρ = 82, collected in October 2018. FTK tracks with Insertable B-layer (IBL) hits were excluded, due to a
>
>
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. The last bin contains the overflow.
Added:
>
>

png pdf
 
Added:
>
>
 
Added:
>
>
The distribution of FTK track pseudo-rapidity (η) vs. azimuthal angle ( φ) from an FTK slice. 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.
 
Changed:
<
<

>
>

pngpdf

Number of tracks produced per event from an FTK slice. 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. The last bin contains the overflow.


png pdf

The expected FTK tracking efficiency with respect to MC truth from functional emulation of the full FTK system using FTKSim, vs. the x position of the luminous centroid of the beamspot. A fully simulated sample of muons with longitudinal impact parameter |z0| < 110 cm and pseudo-rapidity |η| &\lt; 2.5 is used. The efficiency when treating FTK sectors as patterns (black points) is compared to the efficiency for the nominal patterns (red points) and the efficiencies after the first (green points) and second (blue points) tracking stages. The nominal beamspot used for training the sectors and constants and patterns has x = -0.5 mm and y = -0.9 mm.


png pdf

The expected FTK tracking efficiency with respect to MC truth from functional emulation of the full FTK system using FTKSim, vs. the x position of the luminous centroid of the beamspot. A fully simulated sample of muons with longitudinal impact parameter |z0| < 110 cm and pseudo-rapidity |η| < 2.5 is used. The colored dots represent patterns trained with the quoted beamspot x position.


png pdf

The expected FTK tracking efficiency with respect to MC truth from functional emulation of the full FTK system using FTKSim, vs. track transverse momentum pT and the transverse impact parameter d0. A specialized pattern bank is used, in which 30% of the patterns are dedicated to high momentum tracks with large d0. A fully simulated sample of muons with longitudinal impact parameter |z0| < 110 cm and pseudo-rapidity |η| < 2.5 is used.


png pdf

The resolution of the FTK track curvature, from functional emulation of FTK using FTKSim (FTK Full Simulation) and a parameterized uncertainty model (FTK Fast Simulation). The difference between the FTK reconstructed and true values of track charge divided by twice the track transverse momentum (&Deltaa; Q/2pT) is plotted. A fully simulated sample of muons with longitudinal impact parameter |z0| < 110 cm and pseudo-rapidity |η| < 2.5 is used. The resolution for the fast simulation is modeled as a double gaussian derived from full simulation.


png pdf

FTK vs. offline track transverse momentum (pT) residuals from an FTK slice. The difference between the FTK and matched offline track pT 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
 
Line: 1074 to 1166
 
META FILEATTACHMENT attachment="r00358407_Bitmask_vs_Time_NoneMiss-eps-converted-to.pdf" attr="" comment="2018 AUX->ROS plots" date="1536927579" name="r00358407_Bitmask_vs_Time_NoneMiss-eps-converted-to.pdf" path="r00358407_Bitmask_vs_Time_NoneMiss-eps-converted-to.pdf" size="92027" user="tompkins" version="1"
META FILEATTACHMENT attachment="r00358407_Bitmask_vs_Time_NoneMiss.png" attr="" comment="2018 AUX->ROS plots" date="1536927579" name="r00358407_Bitmask_vs_Time_NoneMiss.png" path="r00358407_Bitmask_vs_Time_NoneMiss.png" size="16810" user="tompkins" version="1"
META FILEATTACHMENT attachment="plotKinematics_pt_noIBL_histobugfix.png" attr="" comment="pT no IBL" date="1556185856" name="plotKinematics_pt_noIBL_histobugfix.png" path="plotKinematics_pt_noIBL_histobugfix.png" size="14404" user="strom" version="1"
Added:
>
>
META FILEATTACHMENT attachment="plotKinematics_pt_noIBL_histobugfix.pdf" attr="" comment="" date="1556197333" name="plotKinematics_pt_noIBL_histobugfix.pdf" path="plotKinematics_pt_noIBL_histobugfix.pdf" size="14577" user="strom" version="1"
META FILEATTACHMENT attachment="plotKinematics_etaphi_noIBL_histobugfix.pdf" attr="" comment="eta phi" date="1556197471" name="plotKinematics_etaphi_noIBL_histobugfix.pdf" path="plotKinematics_etaphi_noIBL_histobugfix.pdf" size="15928" user="strom" version="1"
META FILEATTACHMENT attachment="plotKinematics_etaphi_noIBL_histobugfix.png" attr="" comment="eta phi" date="1556197503" name="plotKinematics_etaphi_noIBL_histobugfix.png" path="plotKinematics_etaphi_noIBL_histobugfix.png" size="18778" user="strom" version="1"
META FILEATTACHMENT attachment="plotKinematics_ntrks_noIBL_histobugfix.pdf" attr="" comment="" date="1556198077" name="plotKinematics_ntrks_noIBL_histobugfix.pdf" path="plotKinematics_ntrks_noIBL_histobugfix.pdf" size="14510" user="strom" version="1"
META FILEATTACHMENT attachment="plotKinematics_ntrks_noIBL_histobugfix.png" attr="" comment="" date="1556198077" name="plotKinematics_ntrks_noIBL_histobugfix.png" path="plotKinematics_ntrks_noIBL_histobugfix.png" size="14641" user="strom" version="1"
META FILEATTACHMENT attachment="efficiency_stepbystep.pdf" attr="" comment="" date="1556198349" name="efficiency_stepbystep.pdf" path="efficiency_stepbystep.pdf" size="44718" user="strom" version="1"
META FILEATTACHMENT attachment="efficiency_stepbystep.png" attr="" comment="" date="1556198349" name="efficiency_stepbystep.png" path="efficiency_stepbystep.png" size="88232" user="strom" version="1"
META FILEATTACHMENT attachment="efficiency_beamspotx.pdf" attr="" comment="" date="1556198557" name="efficiency_beamspotx.pdf" path="efficiency_beamspotx.pdf" size="37453" user="strom" version="1"
META FILEATTACHMENT attachment="efficiency_beamspotx.png" attr="" comment="" date="1556198557" name="efficiency_beamspotx.png" path="efficiency_beamspotx.png" size="95626" user="strom" version="1"
META FILEATTACHMENT attachment="efficency_2D.pdf" attr="" comment="" date="1556198810" name="efficency_2D.pdf" path="efficency_2D.pdf" size="70387" user="strom" version="1"
META FILEATTACHMENT attachment="efficency_2D.png" attr="" comment="" date="1556198810" name="efficency_2D.png" path="efficency_2D.png" size="89564" user="strom" version="1"
META FILEATTACHMENT attachment="efficiency_2D.pdf" attr="" comment="" date="1556198939" name="efficiency_2D.pdf" path="efficiency_2D.pdf" size="70387" user="strom" version="1"
META FILEATTACHMENT attachment="efficiency_2D.png" attr="" comment="" date="1556198939" name="efficiency_2D.png" path="efficiency_2D.png" size="89564" user="strom" version="1"
META FILEATTACHMENT attachment="fastsim.pdf" attr="" comment="" date="1556199165" name="fastsim.pdf" path="fastsim.pdf" size="66611" user="strom" version="1"
META FILEATTACHMENT attachment="fastsim.png" attr="" comment="" date="1556199165" name="fastsim.png" path="fastsim.png" size="47868" user="strom" version="1"
META FILEATTACHMENT attachment="compare3Resolutions_eta_noIBL_deltaRplot.pdf" attr="" comment="" date="1556199613" name="compare3Resolutions_eta_noIBL_deltaRplot.pdf" path="compare3Resolutions_eta_noIBL_deltaRplot.pdf" size="17642" user="strom" version="1"
META FILEATTACHMENT attachment="compare3Resolutions_eta_noIBL_deltaRplot.png" attr="" comment="" date="1556199613" name="compare3Resolutions_eta_noIBL_deltaRplot.png" path="compare3Resolutions_eta_noIBL_deltaRplot.png" size="25966" user="strom" version="1"
META FILEATTACHMENT attachment="compare3Resolutions_phi_noIBL_deltaRplot.pdf" attr="" comment="" date="1556199613" name="compare3Resolutions_phi_noIBL_deltaRplot.pdf" path="compare3Resolutions_phi_noIBL_deltaRplot.pdf" size="17201" user="strom" version="1"
META FILEATTACHMENT attachment="compare3Resolutions_phi_noIBL_deltaRplot.png" attr="" comment="" date="1556199613" name="compare3Resolutions_phi_noIBL_deltaRplot.png" path="compare3Resolutions_phi_noIBL_deltaRplot.png" size="22998" user="strom" version="1"
META FILEATTACHMENT attachment="compare3Resolutions_pt_noIBL_deltaRplot.pdf" attr="" comment="" date="1556199613" name="compare3Resolutions_pt_noIBL_deltaRplot.pdf" path="compare3Resolutions_pt_noIBL_deltaRplot.pdf" size="17657" user="strom" version="1"
META FILEATTACHMENT attachment="compare3Resolutions_pt_noIBL_deltaRplot.png" attr="" comment="" date="1556199613" name="compare3Resolutions_pt_noIBL_deltaRplot.png" path="compare3Resolutions_pt_noIBL_deltaRplot.png" size="23060" user="strom" version="1"

Revision 212019-04-25 - DavidMStrom

Line: 1 to 1
 
META TOPICPARENT name="TriggerPublicResults"
AtlasPublicTopicHeader.png
Line: 11 to 11
  This page collects public results for the performance of the FTK system. The technical design report can be found here. Figures from the TDR are collected on this page.
Added:
>
>

April 2019 Run 2 results

Distribution of track transverse momentum (pT) from an FTK slice. 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. The last bin contains the overflow.


 

August 2018 12-layer event displays

Line: 1053 to 1073
 
META FILEATTACHMENT attachment="r00358407_Fraction_of_Matched_Events_ignoreGuessed_ignoreMSBs_8.png" attr="" comment="2018 AUX->ROS plots" date="1536927579" name="r00358407_Fraction_of_Matched_Events_ignoreGuessed_ignoreMSBs_8.png" path="r00358407_Fraction_of_Matched_Events_ignoreGuessed_ignoreMSBs_8.png" size="13855" user="tompkins" version="1"
META FILEATTACHMENT attachment="r00358407_Bitmask_vs_Time_NoneMiss-eps-converted-to.pdf" attr="" comment="2018 AUX->ROS plots" date="1536927579" name="r00358407_Bitmask_vs_Time_NoneMiss-eps-converted-to.pdf" path="r00358407_Bitmask_vs_Time_NoneMiss-eps-converted-to.pdf" size="92027" user="tompkins" version="1"
META FILEATTACHMENT attachment="r00358407_Bitmask_vs_Time_NoneMiss.png" attr="" comment="2018 AUX->ROS plots" date="1536927579" name="r00358407_Bitmask_vs_Time_NoneMiss.png" path="r00358407_Bitmask_vs_Time_NoneMiss.png" size="16810" user="tompkins" version="1"
Added:
>
>
META FILEATTACHMENT attachment="plotKinematics_pt_noIBL_histobugfix.png" attr="" comment="pT no IBL" date="1556185856" name="plotKinematics_pt_noIBL_histobugfix.png" path="plotKinematics_pt_noIBL_histobugfix.png" size="14404" user="strom" version="1"

Revision 202018-09-14 - TovaHolmes

Line: 1 to 1
 
META TOPICPARENT name="TriggerPublicResults"
AtlasPublicTopicHeader.png
Line: 12 to 12
 This page collects public results for the performance of the FTK system. The technical design report can be found here. Figures from the TDR are collected on this page.

August 2018 12-layer event displays

Added:
>
>
 
Added:
>
>
 Event display for two proton-proton collision events including FTK information
Changed:
<
<
recorded on 20th August 2018 showing the ATLAS inner detector in x-y (trans- verse) projection, top, and r-z (lateral) projection, bottom. One FTK tower was
>
>
recorded on 20th August 2018 showing the ATLAS inner detector in x-y (transverse) projection, top, and r-z (lateral) projection, bottom. One FTK tower was
 enabled covering 1/64 of the Inner Detector geometrical coverage. The red lines show trajectories corresponding to track parameters obtained from an offline fit to the cluster positions determined by FTK. The FTK cluster positions are shown
Line: 25 to 26
 

png
Changed:
<
<
>
>
 Event display for two proton-proton collision events including FTK information
Changed:
<
<
recorded on 20th August 2018 showing the ATLAS inner detector in x-y (trans- verse) projection, top, and r-z (lateral) projection, bottom. One FTK tower was
>
>
recorded on 20th August 2018 showing the ATLAS inner detector in x-y (transverse) projection, top, and r-z (lateral) projection, bottom. One FTK tower was
 enabled covering 1/64 of the Inner Detector geometrical coverage. The red lines show trajectories corresponding to track parameters obtained from an offline fit to the cluster positions determined by FTK. The FTK cluster positions are shown
Line: 37 to 36
 vertices determined from tracks reconstructed offline are shown in purple.

Changed:
<
<
png
>
>
png
 

August 2018 8-layer tracks AUX-ROS plots

Changed:
<
<
Number of 8-layer tracks produced per event from an FTK slice. The slice contains four
>
>

Number of 8-layer tracks produced per event from an FTK slice. The slice contains four

 Input Mezzanines, one Data Formatter board, one Auxiliary Card, and one Associative Memory Board. In this slice, instead of sending 8-layer track information to the second- stage board, the auxiliary card directly outputs to a ROS. The 8-layer track information consists of hit coordinates, pattern identification information, and which layers are
Changed:
<
<
included in the 8-layer track fit. The slice spans -0.2 < η < 1.2 and 2.4 < ɸ < 2.8. This plot covers a subset of
>
>
included in the 8-layer track fit. The slice spans -0.2 < η < 1.2 and 2.4 < ɸ < 2.8. This plot covers a subset of
 Run 358395, a 13 TeV pp run which began on August 15, 2018 in which 859196
Line: 61 to 60
 
png pdf
Changed:
<
<
>
>
  The Auxiliary Card fits 8-layer tracks with a minimum of 7 hits. This plot shows the fraction of tracks output by the FTK slice with missing hits in a Pixel layer
Changed:
<
<
(blue), in an SCT layer (red), and those with no missing hits. Fractions are plot- ted as a function of recorded event number. The slice contains four Input Mezza- nines, one Data Formatter board, one Auxiliary Card, and one Associative Mem- ory Board. In this slice, instead of sending 8-layer track information to the second-
>
>
(blue), in an SCT layer (red), and those with no missing hits. Fractions are plotted as a function of recorded event number. The slice contains four Input Mezzanines, one Data Formatter board, one Auxiliary Card, and one Associative Memory Board. In this slice, instead of sending 8-layer track information to the second-
 stage board, the Auxiliary Card directly outputs to a ROS. The 8-layer track information consists of hit coordinates, pattern identification information, and which layers are included in the 8-layer track fit. The slice spans
Changed:
<
<
>
>
 0.2
Changed:
<
<
< η <
>
>
< η <
 1.2 and 2.4
Changed:
<
<
< φ <
>
>
< φ <
 2.8. This plot covers a subset of Run 358395, a 13 TeV pp run
Line: 88 to 85
 
png pdf
Changed:
<
<

Fraction of FTK slice output tracks that are matched to tracks produced by run- ning FTK functional simulation (FTKSim) [ATL-DAQ-PROC-2014-030] on RAW
>
>
Fraction of FTK slice output tracks that are matched to tracks produced by running FTK functional simulation (FTKSim) [ATL-DAQ-PROC-2014-030] on RAW
 data. The RAW data corresponds to a subset of the events processed by the FTK slice. The slice contains four Input Mezzanines, one Data Formatter board, one
Changed:
<
<
Auxiliary Card, and one Associative Memory Board. In this slice, instead of send- ing 8-layer track information to the second-stage board, the Auxiliary Card di- rectly outputs to a ROS. The 8-layer track information consists of hit coordinates,
>
>
Auxiliary Card, and one Associative Memory Board. In this slice, instead of sending 8-layer track information to the second-stage board, the Auxiliary Card directly outputs to a ROS. The 8-layer track information consists of hit coordinates,
 pattern identification information, and which layers are included in the 8-layer track fit. The slice spans
Changed:
<
<
>
>
 0.2
Changed:
<
<
< η <
>
>
< η <
 1.2 and 2.4
Changed:
<
<
< φ <
>
>
< φ <
 2.8. This plot cov- ers a subset of Run 358395, a 13 TeV pp
Line: 114 to 106
 
png pdf
Changed:
<
<

>
>
 Fraction of tracks produced by running FTK functional simulation (FTKSim)
Changed:
<
<
[ATL-DAQ-PROC-2014-030] on RAW data that are matched to FTK slice out- put tracks. The RAW data corresponds to a subset of the events processed by the
>
>
[ATL-DAQ-PROC-2014-030] on RAW data that are matched to FTK slice output tracks. The RAW data corresponds to a subset of the events processed by the
 FTK slice. The slice contains four Input Mezzanines, one Data Formatter board, one Auxiliary Card, and one Associative Memory Board. In this slice, instead of sending 8-layer track information to the second-stage board, the Auxiliary Card
Changed:
<
<
directly outputs to a ROS. The 8-layer track information consists of hit coor- dinates, pattern identification information, and which layers are included in the
>
>
directly outputs to a ROS. The 8-layer track information consists of hit coordinates, pattern identification information, and which layers are included in the
 8-layer track fit. The slice spans
Changed:
<
<
>
>
 0.2
Changed:
<
<
< η <
>
>
< η <
 1.2 and 2.4
Changed:
<
<
< φ <
>
>
< φ <
 2.8. This plot covers a subset of Run 358395, a 13 TeV pp
Line: 140 to 128
 
png pdf
Changed:
<
<

>
>
 The p_T distribution of FTK functional simulation (FTKSim) [ATL-DAQ-PROC-
Line: 160 to 145
 stage board, the Auxiliary Card directly outputs to a ROS. The 8-layer track information consists of hit coordinates, pattern identification information, and which layers are included in the 8-layer track fit. The slice spans
Changed:
<
<
>
>
 0.2
Changed:
<
<
< η <
>
>
< η <
 1.2 and 2.4
Changed:
<
<
< φ <
>
>
< φ <
 2.8. Were processed by FTK at a rate of 63 kHz. This plot covers 500 events from Run 358395, a 13 TeV pp
Line: 176 to 161
 
png pdf
Changed:
<
<

The fraction of tracks output by the FTK slice that were matched to FTK func- tional simulation (FTKSim) [ATL-DAQ-PROC-2014-030] 8-layer tracks as a func- tion of
>
>
The fraction of tracks output by the FTK slice that were matched to FTK functional simulation (FTKSim) [ATL-DAQ-PROC-2014-030] 8-layer tracks as a function of
 p_T . RAW data corresponding to a subset of the events processed by the FTK slice is used as input to the simulation. Because the FTK slice output tracks do not contain track parameter information, the value of p_T is taken from FTKSim. The slice contains four Input Mezzanines, one Data Formatter board, one
Changed:
<
<
Auxiliary Card, and one Associative Memory Board. In this slice, instead of send- ing 8-layer track information to the second-stage board, the Auxiliary Card di- rectly outputs to a ROS. The 8-layer track information consists of hit coordinates,
>
>
Auxiliary Card, and one Associative Memory Board. In this slice, instead of sending 8-layer track information to the second-stage board, the Auxiliary Card directly outputs to a ROS. The 8-layer track information consists of hit coordinates,
 pattern identification information, and which layers are included in the 8-layer track fit. The slice spans
Changed:
<
<
>
>
 0.2
Changed:
<
<
< η <
>
>
< η <
 1.2 and 2.4
Changed:
<
<
< φ <
>
>
< φ <
 2.8. Were processed by FTK at a rate of 63 kHz. This plot covers 500 events from Run 358395, a 13 TeV pp
Changed:
<
<
run which began on August 15, 2018. These 500 events represent a sub- set of recorded events that were also included in the ATLAS bytestream.
>
>
run which began on August 15, 2018. These 500 events represent a subset of recorded events that were also included in the ATLAS bytestream.
 

png
Changed:
<
<
pdf
>
>
pdf
 

Wildcard Performance

Changed:
<
<
>
>
 Figure 1 shows the FTK track finding efficiency from FTK functional simulation [ATL-DAQ-PROC-2014-030] of Monte Carlo single muon events as a function of the muon pseudorapidity
Changed:
<
<
η
>
>
η
 . The black line shows the simulation output assuming perfect detector operation. The green line shows the simulation output when hits from the list of disabled pixel and
Line: 234 to 207
 

png
Changed:
<
<
pdf
>
>
pdf
 

2017 Pattern Bank Production Plots

Added:
>
>
 
Coverage distribution of the generated patterns. One billion patterns per tower are
Line: 259 to 231
 
png pdf
Changed:
<
<
>
>
 Distributions of the number NX of active ternary bits per AM address (top left), the number of generated patterns per AM address Ngen (top right), and the fraction of generated to encoded patterns per AM
Line: 297 to 269
 (Ngen/2NX png pdf)
Changed:
<
<
>
>
 Single muon track reconstruction efficiency in the FTK system as a function of the pseudorapidity η. The efficiencies are shown for the configuration (1+1)pix(1)sct of FTK,
Line: 307 to 279
 layers and no limit on the number NX of active ternary bits per AM address. The resulting efficiency (red) shows distinct drops
Changed:
<
<
near η=±1.2. These are related to a change of geometry
>
>
near η=1.2. These are related to a change of geometry
 of detector modules from a barrel-like to a disk-like orientation. The efficiency is levelled by iterating the assignment of patterns to AM addresses in bins of η.
Line: 320 to 292
 
png pdf
Changed:
<
<
>
>
 Distributions of the number NX of active ternary bits per AM address (top left), the number of generated patterns per AM address Ngen (top
Line: 364 to 336
 (Ngen/2NX png pdf)
Changed:
<
<
>
>
 Single muon track reconstruction efficiency in the FTK system as a function of the pseudorapidity η.
Line: 376 to 348
  layers and a limit on the number of active ternary bits NX<8 (NX<5) for the barrel (endcap) towers. The resulting efficiency (red) shows efficiency drops drops
Changed:
<
<
near η±1.2. These are related to a change of geometry
>
>
near η1.2. These are related to a change of geometry
  of detector modules from a barrel-like to a disk-like orientation. The efficiency is levelled by iterating the assignment of patterns to AM addresses in bins of η.
Line: 389 to 361
 
png pdf
Changed:
<
<
>
>
 Comparison of the single-muon reconstruction efficiency achieved with the FTK system for two different algorithms to determine the ternary bits in the pattern.
Line: 406 to 378
 
png pdf
Changed:
<
<
>
>
 Average number of FTK roads (i.e. patterns with hits on 7 or 8 planes) per tower as a function of the number of collisions per bunch crossing μ, determined from simulated
Line: 420 to 392
  (right) (1+1)pix(3)sct using 1 ternary bit for each of the two directions in each of the three pixel layers, 3 ternary bit for each of the five strip
Changed:
<
<
layers and limits N<>sub>X<8 (NX<5) for the barrel (endcap) towers.
>
>
layers and limits N<>sub>X<8 (NX<5) for the barrel (endcap) towers.
  For each algorithm, the average number of roads observed in the barrel (red) and the endcap (blue) towers is shown. The estimated limit on the average number of roads which can be processed
Line: 433 to 405
 pdf) ((1+1)pix(3)sct,NXbarr<8,NXec<5png pdf)
Changed:
<
<
>
>
 Average number of FTK eight-layer fits per tower as a function of the number of collisions per bunch crossing μ,
Line: 450 to 422
  using 1 ternary bit for each of the two directions in each of the three pixel layers, 3 ternary bit for each of the five strip
Changed:
<
<
layers and limits N<>sub>X<8 (NX<5)
>
>
layers and limits N<>sub>X<8 (NX<5)
  for the barrel (endcap) towers. For each algorithm, the average number of eight-layer fits observed in the barrel (red) and the endcap (blue) towers is shown.
Line: 464 to 436
 pdf) ((1+1)pix(3)sct,NXbarr<8,NXec<5png pdf)
Changed:
<
<
>
>
 Distributions of the encoded pattern multiplicity M for barrel (left) and endcap (right) towers, using two different algorithms to determine the ternary pattern bits.
Line: 476 to 448
  (1+1)pix(3)sct algorithm (blue) is using 1 ternary bit for each of the two directions in each of the three pixel layers, 3 ternary bit for each of the five strip
Changed:
<
<
layers and limits N<>sub>X<8 (NX<5) for the barrel (endcap) towers.
>
>
layers and limits N<>sub>X<8 (NX<5) for the barrel (endcap) towers.
  For the algorithm without cut on NX, patterns with identical non-ternary bits are always assigned to a single AM address, possibly at the cost of generating
Line: 496 to 468
 pdf) (endcappng pdf)
Changed:
<
<
>
>
 Comparison of the bank volume and the fraction of generated coverage loaded into the AM chip for different algorithms to set ternary bits. The barrel (endcap) results are shown as filled (open)
Line: 539 to 511
 

png
Changed:
<
<
pdf
>
>
pdf
 

2014 Performance Plots

Changed:
<
<
<!-- border=1 cellpadding=10 cellspacing=10>                                  -->
>
>
<!-- border=1 cellpadding=10 cellspacing=10>                                  -->
 
The ATLAS HLT beam spot finding and primary vertex reconstruction algorithm adapted for FTK tracks are used to find all primary vertices in the event. The resolution along the beam axis (z) of the FTK primary vertices is dependent on the number of tracks associated with the vertex. The plot
Line: 782 to 751
 Comparison of the χ 2 distribution for a single muon sample with no pile-up using the three different clustering algorithms. The ratio indicated by the blue markers is the ratio of the fully realistic implementation over the ideal, while the the red markers show the ratio of the partially realistic implementation over the ideal. The ideal clustering algorithm places no limits on the size of the cluster, while in the ideal centroid calculation the centroid is calculated as the ToT-weighted average of the cluster. On the realistic clustering implementation, the grid clustering is used, with a grid of 8 21 pixels, limiting the maximum cluster size, while in realistic centroid calculation the centroid is the center of a bounding box containing the cluster.
Changed:
<
<

Comparison of the χ 2 distribution for a tt̄ sample with pile-up 60 at √s = 14 TeV using the three different clustering algorithms. The ratio indicated by the blue markers is the ratio of the fully realistic implementation over the ideal, while the the red markers show the ratio of the partially realistic implementation over the ideal. The ideal clustering algorithm places no limits on the size of the cluster, while in the ideal centroid calculation the centroid is calculated as the ToT-weighted average of the cluster. On the realistic clustering implementation, the grid clustering is used, with a grid of 8 21 pixels, limiting the maximum cluster size, while in realistic centroid calculation the centroid is the center of a bounding box containing the cluster.
>
>

Comparison of the χ 2 distribution for a tt̄ sample with pile-up 60 at √s = 14 TeV using the three different clustering algorithms. The ratio indicated by the blue markers is the ratio of the fully realistic implementation over the ideal, while the the red markers show the ratio of the partially realistic implementation over the ideal. The ideal clustering algorithm places no limits on the size of the cluster, while in the ideal centroid calculation the centroid is calculated as the ToT -weighted average of the cluster. On the realistic clustering implementation, the grid clustering is used, with a grid of 8 21 pixels, limiting the maximum cluster size, while in realistic centroid calculation the centroid is the center of a bounding box containing the cluster.
 

2017 8-layer tracks AUX-ROS plots -- Superceeded by 2018 plots

Changed:
<
<
Number of 8-layer tracks produced per event from an FTK slice. The slice contains four
>
>
Number of 8-layer tracks produced per event from an FTK slice. The slice contains four
 Input Mezzanines, one Data Formatter board, one Auxiliary Card, and one Associative Memory Board. In this slice, instead of sending 8-layer track information to the second- stage board, the auxiliary card directly outputs to a ROS. The 8-layer track information consists of hit coordinates, pattern identification information, and which layers are
Changed:
<
<
included in the 8-layer track fit. The slice spans -0.2 < η < 1.2 and 2.4 < ɸ < 2.8. This
>
>
included in the 8-layer track fit. The slice spans -0.2 < η < 1.2 and 2.4 < ɸ < 2.8. This
 plot covers a subset of Run 340453, a 13 TeV pp run which began on November 9, 2017,
Line: 806 to 775
 
png pdf
Changed:
<
<
>
>
 Fraction of FTK slice output tracks that are matched to tracks produced by running FTK functional simulation (FTKSim) [ATL-DAQ-PROC-2014-030] on RAW data. The RAW data corresponds to a subset of the events processed by the FTK slice. The slice contains
Line: 815 to 783
 Associative Memory Board. In this slice, instead of sending 8-layer track information to the second-stage board, the auxiliary card directly outputs to a ROS. The 8-layer track information consists of hit coordinates, pattern identification information, and which
Changed:
<
<
layers are included in the 8-layer track fit. The slice spans -0.2 < η < 1.2 and 2.4 < ɸ <
>
>
layers are included in the 8-layer track fit. The slice spans -0.2 < η < 1.2 and 2.4 < ɸ <
 2.8. This plot covers 100 events from Run 340453, a 13 TeV pp run which began on
Line: 829 to 797
 
png pdf
Changed:
<
<

>
>
 The p T distribution of FTK functional simulation (FTKSim) [ATL-DAQ-PROC-2014-030]
Line: 847 to 813
 layer track information to the second-stage board, the auxiliary card directly outputs to a ROS. The 8-layer track information consists of hit coordinates, pattern identification information, and which layers are included in the 8-layer track fit. The slice spans -0.2
Changed:
<
<
< η < 1.2 and 2.4 < ɸ < 2.8. Were processed by FTK at a rate of 35 kHz.
>
>
< η < 1.2 and 2.4 < ɸ < 2.8. Were processed by FTK at a rate of 35 kHz.
 This plot covers 100 events from Run 340453, a 13 TeV pp run which began on November 9, 2017. These 100 events represent a subset of recorded events that were also included in the
Line: 860 to 826
 
png pdf
Changed:
<
<

>
>
 The
Changed:
<
<
ɸ
>
>
ɸ
  distribution of FTK functional simulation (FTKSim) [ATL-DAQ-PROC-2014-030] 8-layer tracks that were matched to tracks output by the FTK slice. RAW data corresponding to a subset of the events processed by the FTK slice is used as input to the simulation. Because the FTK slice output tracks do not contain track parameter information, the value of
Changed:
<
<
ɸ
>
>
ɸ
  is taken from FTKSim. The distribution of matched simulated tracks (grey) is compared to all simulated tracks for the same events (purple). The slice contains four Input Mezzanines, one Data Formatter board, one
Line: 878 to 842
 layer track information to the second-stage board, the auxiliary card directly outputs to a ROS. The 8-layer track information consists of hit coordinates, pattern identification information, and which layers are included in the 8-layer track fit. The slice spans -0.2
Changed:
<
<
< η < 1.2 and 2.4 < ɸ < 2.8. This plot covers 100 events from Run 340453, a 13 TeV
>
>
< η < 1.2 and 2.4 < ɸ < 2.8. This plot covers 100 events from Run 340453, a 13 TeV
 pp run which began on November 9, 2017. These 100 events represent a subset of recorded events that were also included in the ATLAS bytestream.
Line: 890 to 854
 
png pdf
Changed:
<
<

>
>
 The
Changed:
<
<
η
>
>
η
  distribution of FTK functional simulation (FTKSim) [ATL-DAQ-PROC-2014-030] 8-layer tracks that were matched to tracks output by the FTK slice. RAW data corresponding to a subset of the events processed by the FTK slice is used as input to the simulation. Because the FTK slice output tracks do not contain track parameter information, the value of
Changed:
<
<
η
>
>
η
  is taken from FTKSim. The distribution of matched simulated tracks (grey) is compared to all simulated tracks for the same events (purple). The slice contains four Input Mezzanines, one Data Formatter board, one
Line: 909 to 870
 layer track information to the second-stage board, the auxiliary card directly outputs to a ROS. The 8-layer track information consists of hit coordinates, pattern identification information, and which layers are included in the 8-layer track fit. The slice spans -0.2
Changed:
<
<
< η < 1.2 and 2.4 < ɸ < 2.8. This plot covers 100 events from Run 340453, a 13 TeV
>
>
< η < 1.2 and 2.4 < ɸ < 2.8. This plot covers 100 events from Run 340453, a 13 TeV
 pp run which began on November 9, 2017. These 100 events represent a subset of recorded events that were also included in the ATLAS bytestream.
Line: 921 to 882
 
png pdf
Changed:
<
<

>
>
 The auxiliary card fits 8-layer tracks with a minimum of 7 hits. This plot shows the fraction of tracks output by the FTK slice with missing hits in a Pixel layer (blue), in an SCT layer (red), and those with no missing hits. Fractions are plotted as a function of
Line: 933 to 891
 sending 8-layer track information to the second-stage board, the auxiliary card directly outputs to a ROS. The 8-layer track information consists of hit coordinates, pattern identification information, and which layers are included in the 8-layer track fit. The
Changed:
<
<
slice spans -0.2 < η < 1.2 and 2.4 < ɸ < 2.8. This plot covers a subset of Run 340453, a
>
>
slice spans -0.2 < η < 1.2 and 2.4 < ɸ < 2.8. This plot covers a subset of Run 340453, a
 13 TeV pp run which began on November 9, 2017, in which 6247 events were processed
Line: 945 to 903
 

png
Changed:
<
<
pdf

>
>
pdf
 
<!-- ********************************************************* -->
<!-- Do NOT remove the remaining lines, but add requested info as appropriate-->
<!-- ********************************************************* -->

Revision 192018-09-14 - LaurenTompkins

Line: 1 to 1
 
META TOPICPARENT name="TriggerPublicResults"
AtlasPublicTopicHeader.png
Line: 11 to 11
  This page collects public results for the performance of the FTK system. The technical design report can be found here. Figures from the TDR are collected on this page.
Changed:
<
<

8-layer tracks AUX-ROS plots

>
>

August 2018 12-layer event displays

Event display for two proton-proton collision events including FTK information recorded on 20th August 2018 showing the ATLAS inner detector in x-y (trans- verse) projection, top, and r-z (lateral) projection, bottom. One FTK tower was enabled covering 1/64 of the Inner Detector geometrical coverage. The red lines show trajectories corresponding to track parameters obtained from an offline fit to the cluster positions determined by FTK. The FTK cluster positions are shown in white points and, for SCT strips in the lateral projection, lines. The primary vertices determined from tracks reconstructed offline are shown in purple.


png
Event display for two proton-proton collision events including FTK information recorded on 20th August 2018 showing the ATLAS inner detector in x-y (trans- verse) projection, top, and r-z (lateral) projection, bottom. One FTK tower was enabled covering 1/64 of the Inner Detector geometrical coverage. The red lines show trajectories corresponding to track parameters obtained from an offline fit to the cluster positions determined by FTK. The FTK cluster positions are shown in white points and, for SCT strips in the lateral projection, lines. The primary vertices determined from tracks reconstructed offline are shown in purple.
png

August 2018 8-layer tracks AUX-ROS plots

 
Number of 8-layer tracks produced per event from an FTK slice. The slice contains four Input Mezzanines, one Data Formatter board, one Auxiliary Card, and one Associative
Line: 22 to 51
 η < 1.2 and 2.4 < ɸ
Changed:
<
<
< 2.8. This plot covers a subset of Run 340453, a 13 TeV
>
>
< 2.8. This plot covers a subset of Run 358395, a 13 TeV
 pp
Changed:
<
<
run which began on November 9, 2017, in which 6247 events were processed by FTK at a rate of 35 kHz.
>
>
run which began on August 15, 2018 in which 859196 events were processed by FTK at a rate of 63 kHz.
 
Changed:
<
<

png pdf
>
>

png pdf
 
Changed:
<
<
Fraction of FTK slice output tracks that are matched to tracks produced by running FTK functional simulation (FTKSim) [ATL-DAQ-PROC-2014-030] on RAW data. The RAW data corresponds to a subset of the events processed by the FTK slice. The slice contains four Input Mezzanines, one Data Formatter board, one Auxiliary Card, and one Associative Memory Board. In this slice, instead of sending 8-layer track information to the second-stage board, the auxiliary card directly outputs to a ROS. The 8-layer track information consists of hit coordinates, pattern identification information, and which layers are included in the 8-layer track fit. The slice spans -0.2 < η < 1.2 and 2.4 < ɸ < 2.8. This plot covers 100 events from Run 340453, a 13 TeV
>
>
The Auxiliary Card fits 8-layer tracks with a minimum of 7 hits. This plot shows the fraction of tracks output by the FTK slice with missing hits in a Pixel layer (blue), in an SCT layer (red), and those with no missing hits. Fractions are plot- ted as a function of recorded event number. The slice contains four Input Mezza- nines, one Data Formatter board, one Auxiliary Card, and one Associative Mem- ory Board. In this slice, instead of sending 8-layer track information to the second- stage board, the Auxiliary Card directly outputs to a ROS. The 8-layer track information consists of hit coordinates, pattern identification information, and which layers are included in the 8-layer track fit. The slice spans − 0.2 < η < 1.2 and 2.4 < φ < 2.8. This plot covers a subset of Run 358395, a 13 TeV
 pp
Changed:
<
<
run which began on November 9, 2017. These 100 events represent a subset of recorded events that were also included in the ATLAS bytestream.

png pdf
>
>
run which began on August 15, 2018 in which 859196 events were processed by FTK at a rate of 63 kHz.

png pdf
 

Changed:
<
<
The p T distribution of FTK functional simulation (FTKSim) [ATL-DAQ-PROC-2014-030] 8-layer tracks that were matched to tracks output by the FTK slice. RAW data corresponding to a subset of the events processed by the FTK slice is used as input to the simulation. Because the FTK slice output tracks do not contain track parameter information, the value of p T is taken from FTKSim. The distribution of matched simulated tracks (grey) is compared to all simulated tracks for the same events (purple). The slice contains four Input Mezzanines, one Data Formatter board, one Auxiliary Card, and one Associative Memory Board. In this slice, instead of sending 8- layer track information to the second-stage board, the auxiliary card directly outputs to a ROS. The 8-layer track information consists of hit coordinates, pattern identification information, and which layers are included in the 8-layer track fit. The slice spans -0.2 < η < 1.2 and 2.4 < ɸ < 2.8. Were processed by FTK at a rate of 35 kHz. This plot covers 100 events from Run 340453, a 13 TeV pp run which began on November 9, 2017. These 100 events represent a subset of recorded events that were also included in the ATLAS bytestream.
>
>
Fraction of FTK slice output tracks that are matched to tracks produced by run- ning FTK functional simulation (FTKSim) [ATL-DAQ-PROC-2014-030] on RAW data. The RAW data corresponds to a subset of the events processed by the FTK slice. The slice contains four Input Mezzanines, one Data Formatter board, one Auxiliary Card, and one Associative Memory Board. In this slice, instead of send- ing 8-layer track information to the second-stage board, the Auxiliary Card di- rectly outputs to a ROS. The 8-layer track information consists of hit coordinates, pattern identification information, and which layers are included in the 8-layer track fit. The slice spans − 0.2 < η < 1.2 and 2.4 < φ < 2.8. This plot cov- ers a subset of Run 358395, a 13 TeV pp run which began on August 15, 2018 in which 859196 events were processed by FTK at a rate of 63 kHz.
 
Changed:
<
<

png pdf
>
>

png pdf
 

Changed:
<
<
The ɸ distribution of FTK functional simulation (FTKSim) [ATL-DAQ-PROC-2014-030] 8-layer tracks that were matched to tracks output by the FTK slice. RAW data corresponding to a subset of the events processed by the FTK slice is used as input to the simulation. Because the FTK slice output tracks do not contain track parameter information, the value of ɸ is taken from FTKSim. The distribution of matched simulated tracks (grey) is compared to all simulated tracks for the same events (purple). The slice contains four Input Mezzanines, one Data Formatter board, one Auxiliary Card, and one Associative Memory Board. In this slice, instead of sending 8- layer track information to the second-stage board, the auxiliary card directly outputs to a ROS. The 8-layer track information consists of hit coordinates, pattern identification information, and which layers are included in the 8-layer track fit. The slice spans -0.2 < η < 1.2 and 2.4 < ɸ < 2.8. This plot covers 100 events from Run 340453, a 13 TeV
>
>
Fraction of tracks produced by running FTK functional simulation (FTKSim) [ATL-DAQ-PROC-2014-030] on RAW data that are matched to FTK slice out- put tracks. The RAW data corresponds to a subset of the events processed by the FTK slice. The slice contains four Input Mezzanines, one Data Formatter board, one Auxiliary Card, and one Associative Memory Board. In this slice, instead of sending 8-layer track information to the second-stage board, the Auxiliary Card directly outputs to a ROS. The 8-layer track information consists of hit coor- dinates, pattern identification information, and which layers are included in the 8-layer track fit. The slice spans − 0.2 < η < 1.2 and 2.4 < φ < 2.8. This plot covers a subset of Run 358395, a 13 TeV
 pp
Changed:
<
<
run which began on November 9, 2017. These 100 events represent a subset of recorded events that were also included in the ATLAS bytestream.
>
>
run which began on August 15, 2018 in which 859196 events were processed by FTK at a rate of 63 kHz.
 
Changed:
<
<

png pdf
>
>

png pdf
 

The
Changed:
<
<
η distribution of FTK functional simulation (FTKSim) [ATL-DAQ-PROC-2014-030] 8-layer tracks that were matched to tracks output by the FTK slice. RAW data corresponding to a subset of the events processed by the FTK slice is used as input to the simulation. Because the FTK slice output tracks do not contain track parameter information, the value of η is taken from FTKSim. The distribution of matched simulated tracks (grey) is compared to all simulated tracks for the same events (purple). The slice contains four Input Mezzanines, one Data Formatter board, one Auxiliary Card, and one Associative Memory Board. In this slice, instead of sending 8- layer track information to the second-stage board, the auxiliary card directly outputs to a ROS. The 8-layer track information consists of hit coordinates, pattern identification information, and which layers are included in the 8-layer track fit. The slice spans -0.2 < η < 1.2 and 2.4 < ɸ < 2.8. This plot covers 100 events from Run 340453, a 13 TeV
>
>
p_T distribution of FTK functional simulation (FTKSim) [ATL-DAQ-PROC- 2014-030] 8-layer tracks that were matched to tracks output by the FTK slice. RAW data corresponding to a subset of the events processed by the FTK slice is used as input to the simulation. Because the FTK slice output tracks do not contain track parameter information, the value of p_T is taken from FTKSim. The distribution of matched simulated tracks (grey) is compared to all simulated tracks for the same events (purple). The slice contains four Input Mezzanines, one Data Formatter board, one Auxiliary Card, and one Associative Memory Board. In this slice, instead of sending 8-layer track information to the second- stage board, the Auxiliary Card directly outputs to a ROS. The 8-layer track information consists of hit coordinates, pattern identification information, and which layers are included in the 8-layer track fit. The slice spans − 0.2 < η < 1.2 and 2.4 < φ < 2.8. Were processed by FTK at a rate of 63 kHz. This plot covers 500 events from Run 358395, a 13 TeV
 pp
Changed:
<
<
run which began on November 9, 2017. These 100 events represent a subset of recorded events that were also included in the ATLAS bytestream.

png pdf
>
>
run which began on August 15, 2018. These 500 events represent a subset of recorded events that were also included in the ATLAS bytestream.

png pdf
 

Changed:
<
<
The auxiliary card fits 8-layer tracks with a minimum of 7 hits. This plot shows the fraction of tracks output by the FTK slice with missing hits in a Pixel layer (blue), in an SCT layer (red), and those with no missing hits. Fractions are plotted as a function of recorded event number. The slice contains four Input Mezzanines, one Data Formatter board, one Auxiliary Card, and one Associative Memory Board. In this slice, instead of sending 8-layer track information to the second-stage board, the auxiliary card directly outputs to a ROS. The 8-layer track information consists of hit coordinates, pattern identification information, and which layers are included in the 8-layer track fit. The slice spans -0.2 < η < 1.2 and 2.4 < ɸ < 2.8. This plot covers a subset of Run 340453, a 13 TeV
>
>
The fraction of tracks output by the FTK slice that were matched to FTK func- tional simulation (FTKSim) [ATL-DAQ-PROC-2014-030] 8-layer tracks as a func- tion of p_T . RAW data corresponding to a subset of the events processed by the FTK slice is used as input to the simulation. Because the FTK slice output tracks do not contain track parameter information, the value of p_T is taken from FTKSim. The slice contains four Input Mezzanines, one Data Formatter board, one Auxiliary Card, and one Associative Memory Board. In this slice, instead of send- ing 8-layer track information to the second-stage board, the Auxiliary Card di- rectly outputs to a ROS. The 8-layer track information consists of hit coordinates, pattern identification information, and which layers are included in the 8-layer track fit. The slice spans − 0.2 < η < 1.2 and 2.4 < φ < 2.8. Were processed by FTK at a rate of 63 kHz. This plot covers 500 events from Run 358395, a 13 TeV
 pp
Changed:
<
<
run which began on November 9, 2017, in which 6247 events were processed by FTK at a rate of 35 kHz
>
>
run which began on August 15, 2018. These 500 events represent a sub- set of recorded events that were also included in the ATLAS bytestream.
 
Changed:
<
<

png pdf
>
>

png pdf
 
Line: 746 to 785
 
Comparison of the χ 2 distribution for a tt̄ sample with pile-up 60 at √s = 14 TeV using the three different clustering algorithms. The ratio indicated by the blue markers is the ratio of the fully realistic implementation over the ideal, while the the red markers show the ratio of the partially realistic implementation over the ideal. The ideal clustering algorithm places no limits on the size of the cluster, while in the ideal centroid calculation the centroid is calculated as the ToT-weighted average of the cluster. On the realistic clustering implementation, the grid clustering is used, with a grid of 8 21 pixels, limiting the maximum cluster size, while in realistic centroid calculation the centroid is the center of a bounding box containing the cluster.
Added:
>
>

2017 8-layer tracks AUX-ROS plots -- Superceeded by 2018 plots

Number of 8-layer tracks produced per event from an FTK slice. The slice contains four Input Mezzanines, one Data Formatter board, one Auxiliary Card, and one Associative Memory Board. In this slice, instead of sending 8-layer track information to the second- stage board, the auxiliary card directly outputs to a ROS. The 8-layer track information consists of hit coordinates, pattern identification information, and which layers are included in the 8-layer track fit. The slice spans -0.2 < η < 1.2 and 2.4 < ɸ < 2.8. This plot covers a subset of Run 340453, a 13 TeV pp run which began on November 9, 2017, in which 6247 events were processed by FTK at a rate of 35 kHz.


png pdf
Fraction of FTK slice output tracks that are matched to tracks produced by running FTK functional simulation (FTKSim) [ATL-DAQ-PROC-2014-030] on RAW data. The RAW data corresponds to a subset of the events processed by the FTK slice. The slice contains four Input Mezzanines, one Data Formatter board, one Auxiliary Card, and one Associative Memory Board. In this slice, instead of sending 8-layer track information to the second-stage board, the auxiliary card directly outputs to a ROS. The 8-layer track information consists of hit coordinates, pattern identification information, and which layers are included in the 8-layer track fit. The slice spans -0.2 < η < 1.2 and 2.4 < ɸ < 2.8. This plot covers 100 events from Run 340453, a 13 TeV pp run which began on November 9, 2017. These 100 events represent a subset of recorded events that were also included in the ATLAS bytestream.
png pdf
The p T distribution of FTK functional simulation (FTKSim) [ATL-DAQ-PROC-2014-030] 8-layer tracks that were matched to tracks output by the FTK slice. RAW data corresponding to a subset of the events processed by the FTK slice is used as input to the simulation. Because the FTK slice output tracks do not contain track parameter information, the value of p T is taken from FTKSim. The distribution of matched simulated tracks (grey) is compared to all simulated tracks for the same events (purple). The slice contains four Input Mezzanines, one Data Formatter board, one Auxiliary Card, and one Associative Memory Board. In this slice, instead of sending 8- layer track information to the second-stage board, the auxiliary card directly outputs to a ROS. The 8-layer track information consists of hit coordinates, pattern identification information, and which layers are included in the 8-layer track fit. The slice spans -0.2 < η < 1.2 and 2.4 < ɸ < 2.8. Were processed by FTK at a rate of 35 kHz. This plot covers 100 events from Run 340453, a 13 TeV pp run which began on November 9, 2017. These 100 events represent a subset of recorded events that were also included in the ATLAS bytestream.
png pdf
The ɸ distribution of FTK functional simulation (FTKSim) [ATL-DAQ-PROC-2014-030] 8-layer tracks that were matched to tracks output by the FTK slice. RAW data corresponding to a subset of the events processed by the FTK slice is used as input to the simulation. Because the FTK slice output tracks do not contain track parameter information, the value of ɸ is taken from FTKSim. The distribution of matched simulated tracks (grey) is compared to all simulated tracks for the same events (purple). The slice contains four Input Mezzanines, one Data Formatter board, one Auxiliary Card, and one Associative Memory Board. In this slice, instead of sending 8- layer track information to the second-stage board, the auxiliary card directly outputs to a ROS. The 8-layer track information consists of hit coordinates, pattern identification information, and which layers are included in the 8-layer track fit. The slice spans -0.2 < η < 1.2 and 2.4 < ɸ < 2.8. This plot covers 100 events from Run 340453, a 13 TeV pp run which began on November 9, 2017. These 100 events represent a subset of recorded events that were also included in the ATLAS bytestream.
png pdf
The η distribution of FTK functional simulation (FTKSim) [ATL-DAQ-PROC-2014-030] 8-layer tracks that were matched to tracks output by the FTK slice. RAW data corresponding to a subset of the events processed by the FTK slice is used as input to the simulation. Because the FTK slice output tracks do not contain track parameter information, the value of η is taken from FTKSim. The distribution of matched simulated tracks (grey) is compared to all simulated tracks for the same events (purple). The slice contains four Input Mezzanines, one Data Formatter board, one Auxiliary Card, and one Associative Memory Board. In this slice, instead of sending 8- layer track information to the second-stage board, the auxiliary card directly outputs to a ROS. The 8-layer track information consists of hit coordinates, pattern identification information, and which layers are included in the 8-layer track fit. The slice spans -0.2 < η < 1.2 and 2.4 < ɸ < 2.8. This plot covers 100 events from Run 340453, a 13 TeV pp run which began on November 9, 2017. These 100 events represent a subset of recorded events that were also included in the ATLAS bytestream.
png pdf
The auxiliary card fits 8-layer tracks with a minimum of 7 hits. This plot shows the fraction of tracks output by the FTK slice with missing hits in a Pixel layer (blue), in an SCT layer (red), and those with no missing hits. Fractions are plotted as a function of recorded event number. The slice contains four Input Mezzanines, one Data Formatter board, one Auxiliary Card, and one Associative Memory Board. In this slice, instead of sending 8-layer track information to the second-stage board, the auxiliary card directly outputs to a ROS. The 8-layer track information consists of hit coordinates, pattern identification information, and which layers are included in the 8-layer track fit. The slice spans -0.2 < η < 1.2 and 2.4 < ɸ < 2.8. This plot covers a subset of Run 340453, a 13 TeV pp run which began on November 9, 2017, in which 6247 events were processed by FTK at a rate of 35 kHz
png pdf

 
<!-- ********************************************************* -->
<!-- Do NOT remove the remaining lines, but add requested info as appropriate-->
<!-- ********************************************************* -->
Line: 878 to 1083
 
META FILEATTACHMENT attachment="r00340465_Fraction_of_Real_Events_ignoreGuessed_ignoreMSBs_8.png" attr="" comment="AUX ROS plots" date="1527826509" name="r00340465_Fraction_of_Real_Events_ignoreGuessed_ignoreMSBs_8.png" path="r00340465_Fraction_of_Real_Events_ignoreGuessed_ignoreMSBs_8.png" size="80005" user="tompkins" version="1"
META FILEATTACHMENT attachment="r00340465_Tracks_per_Event.pdf" attr="" comment="AUX ROS plots" date="1527826550" name="r00340465_Tracks_per_Event.pdf" path="r00340465_Tracks_per_Event.pdf" size="27302" user="tompkins" version="1"
META FILEATTACHMENT attachment="r00340465_Tracks_per_Event.png" attr="" comment="AUX ROS plots" date="1527826550" name="r00340465_Tracks_per_Event.png" path="r00340465_Tracks_per_Event.png" size="71509" user="tompkins" version="1"
Added:
>
>
META FILEATTACHMENT attachment="r00358407_Tracks_per_Event-eps-converted-to1.pdf" attr="" comment="2018 AUX->ROS plots" date="1536926707" name="r00358407_Tracks_per_Event-eps-converted-to1.pdf" path="r00358407_Tracks_per_Event-eps-converted-to1.pdf" size="90755" user="tompkins" version="1"
META FILEATTACHMENT attachment="r00358407_Tracks_per_Event.eps" attr="" comment="2018 AUX->ROS plots" date="1536926708" name="r00358407_Tracks_per_Event.eps" path="r00358407_Tracks_per_Event.eps" size="2021255" user="tompkins" version="1"
META FILEATTACHMENT attachment="r00358407_Fraction_of_Matched_Events_vs_pt_ignoreGuessed_ignoreMSBs_separately-eps-converted-to1.pdf" attr="" comment="2018 AUX->ROS plots" date="1536926708" name="r00358407_Fraction_of_Matched_Events_vs_pt_ignoreGuessed_ignoreMSBs_separately-eps-converted-to1.pdf" path="r00358407_Fraction_of_Matched_Events_vs_pt_ignoreGuessed_ignoreMSBs_separately-eps-converted-to1.pdf" size="90689" user="tompkins" version="1"
META FILEATTACHMENT attachment="r00358407_Fraction_of_Matched_Events_vs_pt_ignoreGuessed_ignoreMSBs_separately.eps" attr="" comment="2018 AUX->ROS plots" date="1536926708" name="r00358407_Fraction_of_Matched_Events_vs_pt_ignoreGuessed_ignoreMSBs_separately.eps" path="r00358407_Fraction_of_Matched_Events_vs_pt_ignoreGuessed_ignoreMSBs_separately.eps" size="2021489" user="tompkins" version="1"
META FILEATTACHMENT attachment="JiveXML_358656_962058206_Hashed-EventInfo-YX-RZ-2018-09-09-09-54-02.png" attr="" comment="2018 AUX->ROS plots" date="1536926708" name="JiveXML_358656_962058206_Hashed-EventInfo-YX-RZ-2018-09-09-09-54-02.png" path="JiveXML_358656_962058206_Hashed-EventInfo-YX-RZ-2018-09-09-09-54-02.png" size="388624" user="tompkins" version="1"
META FILEATTACHMENT attachment="JiveXML_358656_913511153_Hashed-EventInfo-YX-RZ-2018-09-09-09-50-44.png" attr="" comment="2018 AUX->ROS plots" date="1536926708" name="JiveXML_358656_913511153_Hashed-EventInfo-YX-RZ-2018-09-09-09-50-44.png" path="JiveXML_358656_913511153_Hashed-EventInfo-YX-RZ-2018-09-09-09-50-44.png" size="385030" user="tompkins" version="1"
META FILEATTACHMENT attachment="r00358407_Tracks_per_Event-eps-converted-to.pdf" attr="" comment="2018 AUX->ROS plots" date="1536926708" name="r00358407_Tracks_per_Event-eps-converted-to.pdf" path="r00358407_Tracks_per_Event-eps-converted-to.pdf" size="90755" user="tompkins" version="1"
META FILEATTACHMENT attachment="r00358407_Tracks_per_Event.png" attr="" comment="2018 AUX->ROS plots" date="1536926708" name="r00358407_Tracks_per_Event.png" path="r00358407_Tracks_per_Event.png" size="13568" user="tompkins" version="1"
META FILEATTACHMENT attachment="r00358407_Fraction_of_Real_Events_ignoreGuessed_ignoreMSBs_8-eps-converted-to.pdf" attr="" comment="2018 AUX->ROS plots" date="1536926708" name="r00358407_Fraction_of_Real_Events_ignoreGuessed_ignoreMSBs_8-eps-converted-to.pdf" path="r00358407_Fraction_of_Real_Events_ignoreGuessed_ignoreMSBs_8-eps-converted-to.pdf" size="91396" user="tompkins" version="1"
META FILEATTACHMENT attachment="r00358407_Fraction_of_Real_Events_ignoreGuessed_ignoreMSBs_8.png" attr="" comment="2018 AUX->ROS plots" date="1536926708" name="r00358407_Fraction_of_Real_Events_ignoreGuessed_ignoreMSBs_8.png" path="r00358407_Fraction_of_Real_Events_ignoreGuessed_ignoreMSBs_8.png" size="14260" user="tompkins" version="1"
META FILEATTACHMENT attachment="r00358407_Fraction_of_Matched_Events_vs_pt_ignoreGuessed_ignoreMSBs-eps-converted-to.pdf" attr="" comment="2018 AUX->ROS plots" date="1536927579" name="r00358407_Fraction_of_Matched_Events_vs_pt_ignoreGuessed_ignoreMSBs-eps-converted-to.pdf" path="r00358407_Fraction_of_Matched_Events_vs_pt_ignoreGuessed_ignoreMSBs-eps-converted-to.pdf" size="90939" user="tompkins" version="1"
META FILEATTACHMENT attachment="r00358407_Fraction_of_Matched_Events_vs_pt_ignoreGuessed_ignoreMSBs_separately-eps-converted-to.pdf" attr="" comment="2018 AUX->ROS plots" date="1536927579" name="r00358407_Fraction_of_Matched_Events_vs_pt_ignoreGuessed_ignoreMSBs_separately-eps-converted-to.pdf" path="r00358407_Fraction_of_Matched_Events_vs_pt_ignoreGuessed_ignoreMSBs_separately-eps-converted-to.pdf" size="90691" user="tompkins" version="1"
META FILEATTACHMENT attachment="r00358407_Fraction_of_Matched_Events_vs_pt_ignoreGuessed_ignoreMSBs_separately.png" attr="" comment="2018 AUX->ROS plots" date="1536927579" name="r00358407_Fraction_of_Matched_Events_vs_pt_ignoreGuessed_ignoreMSBs_separately.png" path="r00358407_Fraction_of_Matched_Events_vs_pt_ignoreGuessed_ignoreMSBs_separately.png" size="17386" user="tompkins" version="1"
META FILEATTACHMENT attachment="r00358407_Fraction_of_Matched_Events_vs_pt_ignoreGuessed_ignoreMSBs.png" attr="" comment="2018 AUX->ROS plots" date="1536927579" name="r00358407_Fraction_of_Matched_Events_vs_pt_ignoreGuessed_ignoreMSBs.png" path="r00358407_Fraction_of_Matched_Events_vs_pt_ignoreGuessed_ignoreMSBs.png" size="13430" user="tompkins" version="1"
META FILEATTACHMENT attachment="r00358407_Fraction_of_Matched_Events_ignoreGuessed_ignoreMSBs_8-eps-converted-to.pdf" attr="" comment="2018 AUX->ROS plots" date="1536927579" name="r00358407_Fraction_of_Matched_Events_ignoreGuessed_ignoreMSBs_8-eps-converted-to.pdf" path="r00358407_Fraction_of_Matched_Events_ignoreGuessed_ignoreMSBs_8-eps-converted-to.pdf" size="91514" user="tompkins" version="1"
META FILEATTACHMENT attachment="r00358407_Fraction_of_Matched_Events_ignoreGuessed_ignoreMSBs_8.png" attr="" comment="2018 AUX->ROS plots" date="1536927579" name="r00358407_Fraction_of_Matched_Events_ignoreGuessed_ignoreMSBs_8.png" path="r00358407_Fraction_of_Matched_Events_ignoreGuessed_ignoreMSBs_8.png" size="13855" user="tompkins" version="1"
META FILEATTACHMENT attachment="r00358407_Bitmask_vs_Time_NoneMiss-eps-converted-to.pdf" attr="" comment="2018 AUX->ROS plots" date="1536927579" name="r00358407_Bitmask_vs_Time_NoneMiss-eps-converted-to.pdf" path="r00358407_Bitmask_vs_Time_NoneMiss-eps-converted-to.pdf" size="92027" user="tompkins" version="1"
META FILEATTACHMENT attachment="r00358407_Bitmask_vs_Time_NoneMiss.png" attr="" comment="2018 AUX->ROS plots" date="1536927579" name="r00358407_Bitmask_vs_Time_NoneMiss.png" path="r00358407_Bitmask_vs_Time_NoneMiss.png" size="16810" user="tompkins" version="1"

Revision 182018-06-01 - LaurenTompkins

Line: 1 to 1
 
META TOPICPARENT name="TriggerPublicResults"
AtlasPublicTopicHeader.png
Line: 29 to 29
 in which 6247 events were processed by FTK at a rate of 35 kHz.

Changed:
<
<
test
>
>

pngpdf

Fraction of FTK slice output tracks that are matched to tracks produced by running FTK functional simulation (FTKSim) [ATL-DAQ-PROC-2014-030] on RAW data. The RAW data corresponds to a subset of the events processed by the FTK slice. The slice contains four Input Mezzanines, one Data Formatter board, one Auxiliary Card, and one Associative Memory Board. In this slice, instead of sending 8-layer track information to the second-stage board, the auxiliary card directly outputs to a ROS. The 8-layer track information consists of hit coordinates, pattern identification information, and which layers are included in the 8-layer track fit. The slice spans -0.2 < η < 1.2 and 2.4 < ɸ < 2.8. This plot covers 100 events from Run 340453, a 13 TeV pp run which began on November 9, 2017. These 100 events represent a subset of recorded events that were also included in the ATLAS bytestream.
png pdf
The p T distribution of FTK functional simulation (FTKSim) [ATL-DAQ-PROC-2014-030] 8-layer tracks that were matched to tracks output by the FTK slice. RAW data corresponding to a subset of the events processed by the FTK slice is used as input to the simulation. Because the FTK slice output tracks do not contain track parameter information, the value of p T is taken from FTKSim. The distribution of matched simulated tracks (grey) is compared to all simulated tracks for the same events (purple). The slice contains four Input Mezzanines, one Data Formatter board, one Auxiliary Card, and one Associative Memory Board. In this slice, instead of sending 8- layer track information to the second-stage board, the auxiliary card directly outputs to a ROS. The 8-layer track information consists of hit coordinates, pattern identification information, and which layers are included in the 8-layer track fit. The slice spans -0.2 < η < 1.2 and 2.4 < ɸ < 2.8. Were processed by FTK at a rate of 35 kHz. This plot covers 100 events from Run 340453, a 13 TeV pp run which began on November 9, 2017. These 100 events represent a subset of recorded events that were also included in the ATLAS bytestream.
png pdf
The ɸ distribution of FTK functional simulation (FTKSim) [ATL-DAQ-PROC-2014-030] 8-layer tracks that were matched to tracks output by the FTK slice. RAW data corresponding to a subset of the events processed by the FTK slice is used as input to the simulation. Because the FTK slice output tracks do not contain track parameter information, the value of ɸ is taken from FTKSim. The distribution of matched simulated tracks (grey) is compared to all simulated tracks for the same events (purple). The slice contains four Input Mezzanines, one Data Formatter board, one Auxiliary Card, and one Associative Memory Board. In this slice, instead of sending 8- layer track information to the second-stage board, the auxiliary card directly outputs to a ROS. The 8-layer track information consists of hit coordinates, pattern identification information, and which layers are included in the 8-layer track fit. The slice spans -0.2 < η < 1.2 and 2.4 < ɸ < 2.8. This plot covers 100 events from Run 340453, a 13 TeV pp run which began on November 9, 2017. These 100 events represent a subset of recorded events that were also included in the ATLAS bytestream.
png pdf
The η distribution of FTK functional simulation (FTKSim) [ATL-DAQ-PROC-2014-030] 8-layer tracks that were matched to tracks output by the FTK slice. RAW data corresponding to a subset of the events processed by the FTK slice is used as input to the simulation. Because the FTK slice output tracks do not contain track parameter information, the value of η is taken from FTKSim. The distribution of matched simulated tracks (grey) is compared to all simulated tracks for the same events (purple). The slice contains four Input Mezzanines, one Data Formatter board, one Auxiliary Card, and one Associative Memory Board. In this slice, instead of sending 8- layer track information to the second-stage board, the auxiliary card directly outputs to a ROS. The 8-layer track information consists of hit coordinates, pattern identification information, and which layers are included in the 8-layer track fit. The slice spans -0.2 < η < 1.2 and 2.4 < ɸ < 2.8. This plot covers 100 events from Run 340453, a 13 TeV pp run which began on November 9, 2017. These 100 events represent a subset of recorded events that were also included in the ATLAS bytestream.
png pdf
The auxiliary card fits 8-layer tracks with a minimum of 7 hits. This plot shows the fraction of tracks output by the FTK slice with missing hits in a Pixel layer (blue), in an SCT layer (red), and those with no missing hits. Fractions are plotted as a function of recorded event number. The slice contains four Input Mezzanines, one Data Formatter board, one Auxiliary Card, and one Associative Memory Board. In this slice, instead of sending 8-layer track information to the second-stage board, the auxiliary card directly outputs to a ROS. The 8-layer track information consists of hit coordinates, pattern identification information, and which layers are included in the 8-layer track fit. The slice spans -0.2 < η < 1.2 and 2.4 < ɸ < 2.8. This plot covers a subset of Run 340453, a 13 TeV pp run which began on November 9, 2017, in which 6247 events were processed by FTK at a rate of 35 kHz
png pdf
 
Deleted:
<
<

2017 Pattern Bank Production Plots

 
Added:
>
>

Wildcard Performance

Figure 1 shows the FTK track finding efficiency from FTK functional simulation [ATL-DAQ-PROC-2014-030] of Monte Carlo single muon events as a function of the muon pseudorapidity η . The black line shows the simulation output assuming perfect detector operation. The green line shows the simulation output when hits from the list of disabled pixel and SCT modules from 2017 running are excluded from the pattern recognition and track finding, emulating typical detector operation. A drop in the efficiency can be seen when disabled modules are taken into account. The red line shows the efficiency using the WildCards algorithm, in which disabled modules are assumed to always have hits in the pattern recognition stage. The track fitting stage is unchanged by the algorithm. Using this algorithm, the efficiency improves significantly.
png pdf

2017 Pattern Bank Production Plots

 
Coverage distribution of the generated patterns. One billion patterns per tower are
Line: 600 to 766
 
Deleted:
<
<
 
META FILEATTACHMENT attachment="VertexNTrks_vs_VertexZerr_profile.pdf" attr="" comment="Primary vertex pdf" date="1401096780" name="VertexNTrks_vs_VertexZerr_profile.pdf" path="VertexNTrks_vs_VertexZerr_profile.pdf" size="15698" user="tompkins" version="1"
META FILEATTACHMENT attachment="VertexNTrks_vs_VertexZerr_profile.png" attr="" comment="Vertex png" date="1401097808" name="VertexNTrks_vs_VertexZerr_profile.png" path="VertexNTrks_vs_VertexZerr_profile.png" size="12671" user="tompkins" version="2"
Line: 698 to 863
 
META FILEATTACHMENT attachment="r00340465_Fraction_of_Matched_Events_vs_eta_ignoreGuessed_ignoreMSBs_separately.eps" attr="" comment="AUX-ROS plots" date="1527742216" name="r00340465_Fraction_of_Matched_Events_vs_eta_ignoreGuessed_ignoreMSBs_separately.eps" path="r00340465_Fraction_of_Matched_Events_vs_eta_ignoreGuessed_ignoreMSBs_separately.eps" size="2020093" user="tompkins" version="1"
META FILEATTACHMENT attachment="r00340465_Bitmask_vs_Time_NoneMiss.eps" attr="" comment="AUX-ROS plots" date="1527742222" name="r00340465_Bitmask_vs_Time_NoneMiss.eps" path="r00340465_Bitmask_vs_Time_NoneMiss.eps" size="2019597" user="tompkins" version="1"
META FILEATTACHMENT attachment="r00340465_Fraction_of_Matched_Events_vs_pt_ignoreGuessed_ignoreMSBs_separately1.eps" attr="" comment="AUX-ROS plots" date="1527742240" name="r00340465_Fraction_of_Matched_Events_vs_pt_ignoreGuessed_ignoreMSBs_separately1.eps" path="r00340465_Fraction_of_Matched_Events_vs_pt_ignoreGuessed_ignoreMSBs_separately1.eps" size="2020033" user="tompkins" version="1"
Added:
>
>
META FILEATTACHMENT attachment="efficiency.eps" attr="" comment="Wildcard Efficiencies" date="1527826443" name="efficiency.eps" path="efficiency.eps" size="34658" user="tompkins" version="1"
META FILEATTACHMENT attachment="efficiency.pdf" attr="" comment="Wildcard Efficiencies" date="1527826444" name="efficiency.pdf" path="efficiency.pdf" size="22560" user="tompkins" version="1"
META FILEATTACHMENT attachment="efficiency.png" attr="" comment="Wildcard Efficiencies" date="1527826444" name="efficiency.png" path="efficiency.png" size="27325" user="tompkins" version="1"
META FILEATTACHMENT attachment="r00340465_Bitmask_vs_Time_NoneMiss.pdf" attr="" comment="AUX ROS plots" date="1527826507" name="r00340465_Bitmask_vs_Time_NoneMiss.pdf" path="r00340465_Bitmask_vs_Time_NoneMiss.pdf" size="35396" user="tompkins" version="1"
META FILEATTACHMENT attachment="r00340465_Bitmask_vs_Time_NoneMiss.png" attr="" comment="AUX ROS plots" date="1527826508" name="r00340465_Bitmask_vs_Time_NoneMiss.png" path="r00340465_Bitmask_vs_Time_NoneMiss.png" size="157662" user="tompkins" version="1"
META FILEATTACHMENT attachment="r00340465_Fraction_of_Matched_Events_vs_eta_ignoreGuessed_ignoreMSBs_separately.pdf" attr="" comment="AUX ROS plots" date="1527826508" name="r00340465_Fraction_of_Matched_Events_vs_eta_ignoreGuessed_ignoreMSBs_separately.pdf" path="r00340465_Fraction_of_Matched_Events_vs_eta_ignoreGuessed_ignoreMSBs_separately.pdf" size="56281" user="tompkins" version="1"
META FILEATTACHMENT attachment="r00340465_Fraction_of_Matched_Events_vs_eta_ignoreGuessed_ignoreMSBs_separately.png" attr="" comment="AUX ROS plots" date="1527826508" name="r00340465_Fraction_of_Matched_Events_vs_eta_ignoreGuessed_ignoreMSBs_separately.png" path="r00340465_Fraction_of_Matched_Events_vs_eta_ignoreGuessed_ignoreMSBs_separately.png" size="110735" user="tompkins" version="1"
META FILEATTACHMENT attachment="r00340465_Fraction_of_Matched_Events_vs_phi_ignoreGuessed_ignoreMSBs_separately.pdf" attr="" comment="AUX ROS plots" date="1527826509" name="r00340465_Fraction_of_Matched_Events_vs_phi_ignoreGuessed_ignoreMSBs_separately.pdf" path="r00340465_Fraction_of_Matched_Events_vs_phi_ignoreGuessed_ignoreMSBs_separately.pdf" size="56689" user="tompkins" version="1"
META FILEATTACHMENT attachment="r00340465_Fraction_of_Matched_Events_vs_phi_ignoreGuessed_ignoreMSBs_separately.png" attr="" comment="AUX ROS plots" date="1527826509" name="r00340465_Fraction_of_Matched_Events_vs_phi_ignoreGuessed_ignoreMSBs_separately.png" path="r00340465_Fraction_of_Matched_Events_vs_phi_ignoreGuessed_ignoreMSBs_separately.png" size="119348" user="tompkins" version="1"
META FILEATTACHMENT attachment="r00340465_Fraction_of_Matched_Events_vs_pt_ignoreGuessed_ignoreMSBs_separately.pdf" attr="" comment="AUX ROS plots" date="1527826509" name="r00340465_Fraction_of_Matched_Events_vs_pt_ignoreGuessed_ignoreMSBs_separately.pdf" path="r00340465_Fraction_of_Matched_Events_vs_pt_ignoreGuessed_ignoreMSBs_separately.pdf" size="35398" user="tompkins" version="1"
META FILEATTACHMENT attachment="r00340465_Fraction_of_Matched_Events_vs_pt_ignoreGuessed_ignoreMSBs_separately.png" attr="" comment="AUX ROS plots" date="1527826509" name="r00340465_Fraction_of_Matched_Events_vs_pt_ignoreGuessed_ignoreMSBs_separately.png" path="r00340465_Fraction_of_Matched_Events_vs_pt_ignoreGuessed_ignoreMSBs_separately.png" size="109543" user="tompkins" version="1"
META FILEATTACHMENT attachment="r00340465_Fraction_of_Real_Events_ignoreGuessed_ignoreMSBs_8.pdf" attr="" comment="AUX ROS plots" date="1527826509" name="r00340465_Fraction_of_Real_Events_ignoreGuessed_ignoreMSBs_8.pdf" path="r00340465_Fraction_of_Real_Events_ignoreGuessed_ignoreMSBs_8.pdf" size="29088" user="tompkins" version="1"
META FILEATTACHMENT attachment="r00340465_Fraction_of_Real_Events_ignoreGuessed_ignoreMSBs_8.png" attr="" comment="AUX ROS plots" date="1527826509" name="r00340465_Fraction_of_Real_Events_ignoreGuessed_ignoreMSBs_8.png" path="r00340465_Fraction_of_Real_Events_ignoreGuessed_ignoreMSBs_8.png" size="80005" user="tompkins" version="1"
META FILEATTACHMENT attachment="r00340465_Tracks_per_Event.pdf" attr="" comment="AUX ROS plots" date="1527826550" name="r00340465_Tracks_per_Event.pdf" path="r00340465_Tracks_per_Event.pdf" size="27302" user="tompkins" version="1"
META FILEATTACHMENT attachment="r00340465_Tracks_per_Event.png" attr="" comment="AUX ROS plots" date="1527826550" name="r00340465_Tracks_per_Event.png" path="r00340465_Tracks_per_Event.png" size="71509" user="tompkins" version="1"

Revision 172018-05-31 - LaurenTompkins

Line: 1 to 1
 
META TOPICPARENT name="TriggerPublicResults"
AtlasPublicTopicHeader.png
Line: 693 to 693
 
META FILEATTACHMENT attachment="ftkPlots170303_fig9b.png" attr="" comment="Duplicate patterns multiplicity" date="1488628803" name="ftkPlots170303_fig9b.png" path="ftkPlots170303_fig9b.png" size="41617" user="sschmitt" version="1"
META FILEATTACHMENT attachment="ftkPlots170303_fig10.pdf" attr="" comment="Survey of parameter space with and with out cut on NX" date="1488628870" name="ftkPlots170303_fig10.pdf" path="ftkPlots170303_fig10.pdf" size="6874" user="sschmitt" version="1"
META FILEATTACHMENT attachment="ftkPlots170303_fig10.png" attr="" comment="Survey of parameter space with and with out cut on NX" date="1488628871" name="ftkPlots170303_fig10.png" path="ftkPlots170303_fig10.png" size="84058" user="sschmitt" version="1"
Added:
>
>
META FILEATTACHMENT attachment="r00340465_Fraction_of_Real_Events_ignoreGuessed_ignoreMSBs_8.eps" attr="" comment="AUX-ROS plots" date="1527742205" name="r00340465_Fraction_of_Real_Events_ignoreGuessed_ignoreMSBs_8.eps" path="r00340465_Fraction_of_Real_Events_ignoreGuessed_ignoreMSBs_8.eps" size="2018516" user="tompkins" version="1"
META FILEATTACHMENT attachment="r00340465_Fraction_of_Matched_Events_vs_phi_ignoreGuessed_ignoreMSBs_separately.eps" attr="" comment="AUX-ROS plots" date="1527742210" name="r00340465_Fraction_of_Matched_Events_vs_phi_ignoreGuessed_ignoreMSBs_separately.eps" path="r00340465_Fraction_of_Matched_Events_vs_phi_ignoreGuessed_ignoreMSBs_separately.eps" size="2019412" user="tompkins" version="1"
META FILEATTACHMENT attachment="r00340465_Fraction_of_Matched_Events_vs_eta_ignoreGuessed_ignoreMSBs_separately.eps" attr="" comment="AUX-ROS plots" date="1527742216" name="r00340465_Fraction_of_Matched_Events_vs_eta_ignoreGuessed_ignoreMSBs_separately.eps" path="r00340465_Fraction_of_Matched_Events_vs_eta_ignoreGuessed_ignoreMSBs_separately.eps" size="2020093" user="tompkins" version="1"
META FILEATTACHMENT attachment="r00340465_Bitmask_vs_Time_NoneMiss.eps" attr="" comment="AUX-ROS plots" date="1527742222" name="r00340465_Bitmask_vs_Time_NoneMiss.eps" path="r00340465_Bitmask_vs_Time_NoneMiss.eps" size="2019597" user="tompkins" version="1"
META FILEATTACHMENT attachment="r00340465_Fraction_of_Matched_Events_vs_pt_ignoreGuessed_ignoreMSBs_separately1.eps" attr="" comment="AUX-ROS plots" date="1527742240" name="r00340465_Fraction_of_Matched_Events_vs_pt_ignoreGuessed_ignoreMSBs_separately1.eps" path="r00340465_Fraction_of_Matched_Events_vs_pt_ignoreGuessed_ignoreMSBs_separately1.eps" size="2020033" user="tompkins" version="1"

Revision 162018-05-31 - LaurenTompkins

Line: 1 to 1
 
META TOPICPARENT name="TriggerPublicResults"
AtlasPublicTopicHeader.png
Line: 11 to 11
  This page collects public results for the performance of the FTK system. The technical design report can be found here. Figures from the TDR are collected on this page.
Added:
>
>

8-layer tracks AUX-ROS plots

Number of 8-layer tracks produced per event from an FTK slice. The slice contains four Input Mezzanines, one Data Formatter board, one Auxiliary Card, and one Associative Memory Board. In this slice, instead of sending 8-layer track information to the second- stage board, the auxiliary card directly outputs to a ROS. The 8-layer track information consists of hit coordinates, pattern identification information, and which layers are included in the 8-layer track fit. The slice spans -0.2 < η < 1.2 and 2.4 < ɸ < 2.8. This plot covers a subset of Run 340453, a 13 TeV pp run which began on November 9, 2017, in which 6247 events were processed by FTK at a rate of 35 kHz.

test
 

2017 Pattern Bank Production Plots

Revision 152017-03-04 - StefanSchmitt

Line: 1 to 1
 
META TOPICPARENT name="TriggerPublicResults"
AtlasPublicTopicHeader.png
Line: 11 to 11
  This page collects public results for the performance of the FTK system. The technical design report can be found here. Figures from the TDR are collected on this page.
Added:
>
>

2017 Pattern Bank Production Plots

Coverage distribution of the generated patterns. One billion patterns per tower are generated using the FTK fit constants. Each pattern corresponds to 15-bit hit coordinates measured in eight detector planes (three pixel detector planes and five strip detector planes). Each pixel coordinate encodes information along two directions in a single 15-bit word. There are 32 barrel (|η|<1.6) and 32 endcap (|η|>1.6) towers. Within the 109 patterns generated, there may be duplicates. The coverage is defined as the multiplicity at which a particular pattern is generated. The coverage distribution is shown separately for barrel and endcap towers. Patterns with large coverage are the most important for achieving good pattern recognition efficiencies.
png pdf
Distributions of the number NX of active ternary bits per AM address (top left), the number of generated patterns per AM address Ngen (top right), and the fraction of generated to encoded patterns per AM address Ngen/2NX (lower row). The distributions are shown separately for barrel (|η|<1.6) and endcap (|η|>1.6) towers. For each of the 64 towers 16.8 million AM addresses are available, whereas 109 patterns have been generated. Each AM address holds eight 15-bit words of information about hits in the eight detector planes. Each 15-bit word has up to three ternary bits, which encode the information 0, 1 or X, where X means the ternary bit is "active" and the values 0 or 1 are both valid. The ternary bits allow for large numbers (2NX) of patterns to be encoded at a single AM address. For this figure, ternary bit patterns are generated for the configuration (1+1)pix(1)sct with 1 ternary bit for each of the two directions in each of the three pixel (pix) layers and with 1 ternary bit for each of the five strip (sct) layers. The generated patterns are ordered by decreasing coverage and are assigned to AM addresses. The resulting NX distribution exhibits tails to large NX, corresponding to AM addresses which encode a large number of possible patterns and thus are susceptible to random coincidences. Such patterns are also reflected by low values of Ngen/2NX.
png pdf (NXpng pdf) (Ngenpng pdf) (Ngen/2NX png pdf)
Single muon track reconstruction efficiency in the FTK system as a function of the pseudorapidity η. The efficiencies are shown for the configuration (1+1)pix(1)sct of FTK, using 1 ternary bit for each of the two directions in each of the three pixel (pix) layers, 1 ternary bit for each of the five strip (sct) layers and no limit on the number NX of active ternary bits per AM address. The resulting efficiency (red) shows distinct drops near η=±1.2. These are related to a change of geometry of detector modules from a barrel-like to a disk-like orientation. The efficiency is levelled by iterating the assignment of patterns to AM addresses in bins of η. For each iteration, the number of available AM addresses is increased for low-efficiency bins and decreased for high-efficiency bins, such that the total number of AM addresses per tower is kept constant. The result is satisfactory after one iteration (blue) and does not improve much when adding another iteration (dark yellow).
png pdf
Distributions of the number NX of active ternary bits per AM address (top left), the number of generated patterns per AM address Ngen (top right), and the fraction of generated to encoded patterns per AM address Ngen/2NX (lower row). The distributions are shown separately for barrel (|η|<1.6) and endcap (|η>1.6) towers. For each of the 64 towers 16.8 million AM addresses are available, whereas 109 patterns have been generated. Each AM address holds eight 15-bit words of information of the eight detector planes. Each 15-bit word has up to three ternary bits, which encode the information 0, 1 or X, where X means the ternary bit is active and the values 0 or 1 are both valid. The ternary bits allow for large numbers 2NX of patterns to be encoded at a single AM address, where NX is the total number of ternary bits in status X at a given AM address. For this figure, ternary bit patterns are generated for the configuration (1+1)pix(3)sct with 1 ternary bit for each of the two directions in each of the three pixel (pix) layers and with 3 ternary bit for each of the five strip (sct) layers. The generated 109 patterns are ordered by decreasing coverage and are assigned to AM addresses. When assigning patterns to AM addresses, limits on NX are introduced, NX<8 for barrel towers and NX<5 for endcap towers, respectively. The resulting NX distribution shows that many patterns have NX values near the cut-off. The limit in NX is also reflected in the distribution Ngen, which falls off steeply.
png pdf (NXpng pdf) (Ngenpng pdf) (Ngen/2NX png pdf)
Single muon track reconstruction efficiency in the FTK system as a function of the pseudorapidity η. The efficiencies are shown for ternary bits calculated using the configuration (1+1)pix(3)sct, using 1 ternary bit for each of the two directions in each of the three pixel (pix) layers, 3 ternary bit for each of the five strip (sct) layers and a limit on the number of active ternary bits NX<8 (NX<5) for the barrel (endcap) towers. The resulting efficiency (red) shows efficiency drops drops near η±1.2. These are related to a change of geometry of detector modules from a barrel-like to a disk-like orientation. The efficiency is levelled by iterating the assignment of patterns to AM addresses in bins of η. For each iteration, the number of available AM addresses is increased for low-efficiency bins and decreased for high-efficiency bins, such that the total number of AM addresses per tower is kept constant. The result is satisfactory after one iteration (blue) and does not improve much when adding another iteration (dark yellow).
png pdf
Comparison of the single-muon reconstruction efficiency achieved with the FTK system for two different algorithms to determine the ternary bits in the pattern. The algorithm (1+1)pix(1)sct (blue) is using 1 ternary bit for each of the two directions in each of the three pixel (pix) layers, 1 ternary bit for each of the five strip (sct) layers and no limit on the number NX of active ternary bits per AM address. The preferred algorithm (1+1)pix(3)sct (red) is using 1 ternary bit for each of the two directions in each of the three pixel layers, 3 ternary bit for each of the five strip layers and limits NX<8 (NX<5) for the barrel (endcap) towers.
png pdf
Average number of FTK roads (i.e. patterns with hits on 7 or 8 planes) per tower as a function of the number of collisions per bunch crossing μ, determined from simulated pp→ttX events at a centre-of-mass energy √s=13 TeV. Pattern banks resulting from two different algorithms to determine ternary pattern bits are compared: (left) (1+1)pix(1)sct, using 1 ternary bit for each of the two directions in each of the three pixel (pix) layers, 1 ternary bit for each of the five strip (sct) layers and no limit on the number NX of active ternary bits per AM address; (right) (1+1)pix(3)sct using 1 ternary bit for each of the two directions in each of the three pixel layers, 3 ternary bit for each of the five strip layers and limits N<>sub>X<8 (NX<5) for the barrel (endcap) towers. For each algorithm, the average number of roads observed in the barrel (red) and the endcap (blue) towers is shown. The estimated limit on the average number of roads which can be processed by a single tower is indicated.
png pdf ((1+1)pix(1)sctpng pdf) ((1+1)pix(3)sct,NXbarr<8,NXec<5png pdf)
Average number of FTK eight-layer fits per tower as a function of the number of collisions per bunch crossing μ, determined from simulated pp→ttX events at a centre-of-mass energy √s=13 TeV. Pattern banks resulting from two different algorithms to determine ternary pattern bits are compared: (left) (1+1)pix(1)sct, using 1 ternary bit for each of the two directions in each of the three pixel (pix) layers, 1 ternary bit for each of the five strip (sct) layers and no limit on the number NX of active ternary bits per AM address; (right) (1+1)pix(3)sct using 1 ternary bit for each of the two directions in each of the three pixel layers, 3 ternary bit for each of the five strip layers and limits N<>sub>X<8 (NX<5) for the barrel (endcap) towers. For each algorithm, the average number of eight-layer fits observed in the barrel (red) and the endcap (blue) towers is shown. The estimated limit on the average number of eight-layer fits which can be processed by a single tower is indicated.
png pdf ((1+1)pix(1)sctpng pdf) ((1+1)pix(3)sct,NXbarr<8,NXec<5png pdf)
Distributions of the encoded pattern multiplicity M for barrel (left) and endcap (right) towers, using two different algorithms to determine the ternary pattern bits. The (1+1)pix(1)sct algorithm (red) is using 1 ternary bit for each of the two directions in each of the three pixel (pix) layers, 1 ternary bit for each of the five strip (sct) layers and no limit on the number NX of active ternary bits per AM address ; the (1+1)pix(3)sct algorithm (blue) is using 1 ternary bit for each of the two directions in each of the three pixel layers, 3 ternary bit for each of the five strip layers and limits N<>sub>X<8 (NX<5) for the barrel (endcap) towers. For the algorithm without cut on NX, patterns with identical non-ternary bits are always assigned to a single AM address, possibly at the cost of generating large NX. Each encoded pattern, after expanding all ternary bits, is stored only once (M=1). In contrast, for the algorithm with limit on the number NX, patterns with identical non-ternary bits may be assigned to several distinct AM addresses, if the overlap in the ternary bits is small and the resulting NX thus would exceed the limit. This procedure avoids large NX but does create duplicate patterns. As visible from the blue curve, a moderate level of duplicate patterns (M>1) is created.
png pdf (barrelpng pdf) (endcappng pdf)
Comparison of the bank volume and the fraction of generated coverage loaded into the AM chip for different algorithms to set ternary bits. The barrel (endcap) results are shown as filled (open) circles. The bank volume is defined as the average number of patterns encoded at a given AM address, 〈2NX〉. The fraction of generated coverage corresponds to the fraction of the originally generated 109 tracks per tower which are processed in sequence before all available AM addresses are filled. Two classes of algorithms are compared: algorithms without limit on the number NX of ternary bits (blue squares) and algorithms with a limit on NX (red circles). For the algorithms shown with blue squares, the number of available ternary bits per detector plane is indicated for each single point. For example, the configuration (1+1)pix(1)4(2)1 is using 1 ternary bit for each of the two directions of the 3 pixel (pix) planes, 1 ternary bit for the innermost 4 strip planes and 2 ternary bits for the outermost strip plane. The configuration (1+1)pix(2)sct is using 1 ternary bit for each of the two directions of the 3 pixel planes and 2 ternary bits of each of the five strip (sct) planes. For each of the red points the configuration of ternary bits per detector plane is fixed to (1+1)pix(3)sct, but the corresponding limit on NX varies and is indicated. In the limit NX<1, the ternary bits behave as normal bits, because the value X is never assigned to a ternary bit. The corresponding bank volume thus is equal to unity. Increasing fractions of generated coverage correspond to better track reconstruction efficiencies. Increasing bank volumes correspond to an increased level of random coincidences, and challenge the dataflow. The endcap towers generally require a much smaller bank volume as compared to barrel towers, when looking at the same fraction of coverage. This is related to the geometrical tower definition and is intentional, as the endcap patterns correspond to tracks passing regions of high hit densities. When comparing algorithms with and without limits on NX at a similar fraction of coverage, the algorithms with limits on NX result in a smaller bank volume and thus perform better.
png pdf
 

2014 Performance Plots

<!-- border=1 cellpadding=10 cellspacing=10>                                  -->
Line: 321 to 628
 
META FILEATTACHMENT attachment="ftkPlots170302_fig2b.pdf" attr="h" comment="" date="1488479666" name="ftkPlots170302_fig2b.pdf" path="ftkPlots170302_fig2b.pdf" size="13768" user="sschmitt" version="1"
META FILEATTACHMENT attachment="ftkPlots170302_fig2c.png" attr="h" comment="" date="1488479666" name="ftkPlots170302_fig2c.png" path="ftkPlots170302_fig2c.png" size="58024" user="sschmitt" version="1"
META FILEATTACHMENT attachment="ftkPlots170302_fig2c.pdf" attr="h" comment="" date="1488479666" name="ftkPlots170302_fig2c.pdf" path="ftkPlots170302_fig2c.pdf" size="10039" user="sschmitt" version="1"
Added:
>
>
META FILEATTACHMENT attachment="ftkPlots170303_fig1.pdf" attr="" comment="Coverage distribution" date="1488628156" name="ftkPlots170303_fig1.pdf" path="ftkPlots170303_fig1.pdf" size="7041" user="sschmitt" version="1"
META FILEATTACHMENT attachment="ftkPlots170303_fig1.png" attr="" comment="Coverage distribution" date="1488628157" name="ftkPlots170303_fig1.png" path="ftkPlots170303_fig1.png" size="56592" user="sschmitt" version="1"
META FILEATTACHMENT attachment="ftkPlots170303_fig2.pdf" attr="" comment="Contro plots (1+1)pix(1)sct, no cut on NX" date="1488628247" name="ftkPlots170303_fig2.pdf" path="ftkPlots170303_fig2.pdf" size="10096" user="sschmitt" version="1"
META FILEATTACHMENT attachment="ftkPlots170303_fig2.png" attr="" comment="Contro plots (1+1)pix(1)sct, no cut on NX" date="1488628248" name="ftkPlots170303_fig2.png" path="ftkPlots170303_fig2.png" size="88059" user="sschmitt" version="1"
META FILEATTACHMENT attachment="ftkPlots170303_fig2a.pdf" attr="" comment="Contro plots (1+1)pix(1)sct, no cut on NX" date="1488628248" name="ftkPlots170303_fig2a.pdf" path="ftkPlots170303_fig2a.pdf" size="4002" user="sschmitt" version="1"
META FILEATTACHMENT attachment="ftkPlots170303_fig2a.png" attr="" comment="Contro plots (1+1)pix(1)sct, no cut on NX" date="1488628248" name="ftkPlots170303_fig2a.png" path="ftkPlots170303_fig2a.png" size="41135" user="sschmitt" version="1"
META FILEATTACHMENT attachment="ftkPlots170303_fig2b.pdf" attr="" comment="Contro plots (1+1)pix(1)sct, no cut on NX" date="1488628248" name="ftkPlots170303_fig2b.pdf" path="ftkPlots170303_fig2b.pdf" size="7275" user="sschmitt" version="1"
META FILEATTACHMENT attachment="ftkPlots170303_fig2b.png" attr="" comment="Contro plots (1+1)pix(1)sct, no cut on NX" date="1488628248" name="ftkPlots170303_fig2b.png" path="ftkPlots170303_fig2b.png" size="55091" user="sschmitt" version="1"
META FILEATTACHMENT attachment="ftkPlots170303_fig2c.pdf" attr="" comment="Contro plots (1+1)pix(1)sct, no cut on NX" date="1488628248" name="ftkPlots170303_fig2c.pdf" path="ftkPlots170303_fig2c.pdf" size="4264" user="sschmitt" version="1"
META FILEATTACHMENT attachment="ftkPlots170303_fig2c.png" attr="" comment="Contro plots (1+1)pix(1)sct, no cut on NX" date="1488628248" name="ftkPlots170303_fig2c.png" path="ftkPlots170303_fig2c.png" size="44010" user="sschmitt" version="1"
META FILEATTACHMENT attachment="ftkPlots170303_fig3.pdf" attr="" comment="Efficiency for: (1+1)pix(1sct), no cut on NX" date="1488628341" name="ftkPlots170303_fig3.pdf" path="ftkPlots170303_fig3.pdf" size="10365" user="sschmitt" version="1"
META FILEATTACHMENT attachment="ftkPlots170303_fig3.png" attr="" comment="Efficiency for: (1+1)pix(1sct), no cut on NX" date="1488628341" name="ftkPlots170303_fig3.png" path="ftkPlots170303_fig3.png" size="83086" user="sschmitt" version="1"
META FILEATTACHMENT attachment="ftkPlots170303_fig4.pdf" attr="" comment="Control plots: (1+1)pix(3)sct) with cuts NX<8 (barrel), NX<5 (endcap)" date="1488628425" name="ftkPlots170303_fig4.pdf" path="ftkPlots170303_fig4.pdf" size="8033" user="sschmitt" version="1"
META FILEATTACHMENT attachment="ftkPlots170303_fig4.png" attr="" comment="Control plots: (1+1)pix(3)sct) with cuts NX<8 (barrel), NX<5 (endcap)" date="1488628425" name="ftkPlots170303_fig4.png" path="ftkPlots170303_fig4.png" size="86059" user="sschmitt" version="1"
META FILEATTACHMENT attachment="ftkPlots170303_fig4a.pdf" attr="" comment="Control plots: (1+1)pix(3)sct) with cuts NX<8 (barrel), NX<5 (endcap)" date="1488628425" name="ftkPlots170303_fig4a.pdf" path="ftkPlots170303_fig4a.pdf" size="4157" user="sschmitt" version="1"
META FILEATTACHMENT attachment="ftkPlots170303_fig4a.png" attr="" comment="Control plots: (1+1)pix(3)sct) with cuts NX<8 (barrel), NX<5 (endcap)" date="1488628426" name="ftkPlots170303_fig4a.png" path="ftkPlots170303_fig4a.png" size="45379" user="sschmitt" version="1"
META FILEATTACHMENT attachment="ftkPlots170303_fig4b.pdf" attr="" comment="Control plots: (1+1)pix(3)sct) with cuts NX<8 (barrel), NX<5 (endcap)" date="1488628426" name="ftkPlots170303_fig4b.pdf" path="ftkPlots170303_fig4b.pdf" size="5311" user="sschmitt" version="1"
META FILEATTACHMENT attachment="ftkPlots170303_fig4b.png" attr="" comment="Control plots: (1+1)pix(3)sct) with cuts NX<8 (barrel), NX<5 (endcap)" date="1488628426" name="ftkPlots170303_fig4b.png" path="ftkPlots170303_fig4b.png" size="51133" user="sschmitt" version="1"
META FILEATTACHMENT attachment="ftkPlots170303_fig4c.pdf" attr="" comment="Control plots: (1+1)pix(3)sct) with cuts NX<8 (barrel), NX<5 (endcap)" date="1488628426" name="ftkPlots170303_fig4c.pdf" path="ftkPlots170303_fig4c.pdf" size="4190" user="sschmitt" version="1"
META FILEATTACHMENT attachment="ftkPlots170303_fig4c.png" attr="" comment="Control plots: (1+1)pix(3)sct) with cuts NX<8 (barrel), NX<5 (endcap)" date="1488628426" name="ftkPlots170303_fig4c.png" path="ftkPlots170303_fig4c.png" size="44381" user="sschmitt" version="1"
META FILEATTACHMENT attachment="ftkPlots170303_fig5.pdf" attr="" comment="Efficiency: (1+1)pix(3)sct with cut NX<8 (barrel) and NX<5 (endcap)" date="1488628498" name="ftkPlots170303_fig5.pdf" path="ftkPlots170303_fig5.pdf" size="10035" user="sschmitt" version="1"
META FILEATTACHMENT attachment="ftkPlots170303_fig5.png" attr="" comment="Efficiency: (1+1)pix(3)sct with cut NX<8 (barrel) and NX<5 (endcap)" date="1488628498" name="ftkPlots170303_fig5.png" path="ftkPlots170303_fig5.png" size="75200" user="sschmitt" version="1"
META FILEATTACHMENT attachment="ftkPlots170303_fig6.pdf" attr="" comment="Efficiency comparison: algorithms with and without cuts on NX" date="1488628567" name="ftkPlots170303_fig6.pdf" path="ftkPlots170303_fig6.pdf" size="8646" user="sschmitt" version="1"
META FILEATTACHMENT attachment="ftkPlots170303_fig6.png" attr="" comment="Efficiency comparison: algorithms with and without cuts on NX" date="1488628567" name="ftkPlots170303_fig6.png" path="ftkPlots170303_fig6.png" size="65754" user="sschmitt" version="1"
META FILEATTACHMENT attachment="ftkPlots170303_fig7.pdf" attr="" comment="Number of roads: algorithms with and without cuts on NX" date="1488628634" name="ftkPlots170303_fig7.pdf" path="ftkPlots170303_fig7.pdf" size="6171" user="sschmitt" version="1"
META FILEATTACHMENT attachment="ftkPlots170303_fig7.png" attr="" comment="Number of roads: algorithms with and without cuts on NX" date="1488628635" name="ftkPlots170303_fig7.png" path="ftkPlots170303_fig7.png" size="56286" user="sschmitt" version="1"
META FILEATTACHMENT attachment="ftkPlots170303_fig7a.pdf" attr="" comment="Number of roads: algorithms with and without cuts on NX" date="1488628635" name="ftkPlots170303_fig7a.pdf" path="ftkPlots170303_fig7a.pdf" size="4724" user="sschmitt" version="1"
META FILEATTACHMENT attachment="ftkPlots170303_fig7a.png" attr="" comment="Number of roads: algorithms with and without cuts on NX" date="1488628635" name="ftkPlots170303_fig7a.png" path="ftkPlots170303_fig7a.png" size="62354" user="sschmitt" version="1"
META FILEATTACHMENT attachment="ftkPlots170303_fig7b.pdf" attr="" comment="Number of roads: algorithms with and without cuts on NX" date="1488628635" name="ftkPlots170303_fig7b.pdf" path="ftkPlots170303_fig7b.pdf" size="4759" user="sschmitt" version="1"
META FILEATTACHMENT attachment="ftkPlots170303_fig7b.png" attr="" comment="Number of roads: algorithms with and without cuts on NX" date="1488628635" name="ftkPlots170303_fig7b.png" path="ftkPlots170303_fig7b.png" size="63652" user="sschmitt" version="1"
META FILEATTACHMENT attachment="ftkPlots170303_fig8.pdf" attr="" comment="Number of 8-layer fits: algorithms with and without cut on NX" date="1488628718" name="ftkPlots170303_fig8.pdf" path="ftkPlots170303_fig8.pdf" size="6264" user="sschmitt" version="1"
META FILEATTACHMENT attachment="ftkPlots170303_fig8.png" attr="" comment="Number of 8-layer fits: algorithms with and without cut on NX" date="1488628718" name="ftkPlots170303_fig8.png" path="ftkPlots170303_fig8.png" size="55623" user="sschmitt" version="1"
META FILEATTACHMENT attachment="ftkPlots170303_fig8a.pdf" attr="" comment="Number of 8-layer fits: algorithms with and without cut on NX" date="1488628718" name="ftkPlots170303_fig8a.pdf" path="ftkPlots170303_fig8a.pdf" size="4823" user="sschmitt" version="1"
META FILEATTACHMENT attachment="ftkPlots170303_fig8a.png" attr="" comment="Number of 8-layer fits: algorithms with and without cut on NX" date="1488628718" name="ftkPlots170303_fig8a.png" path="ftkPlots170303_fig8a.png" size="63740" user="sschmitt" version="1"
META FILEATTACHMENT attachment="ftkPlots170303_fig8b.pdf" attr="" comment="Number of 8-layer fits: algorithms with and without cut on NX" date="1488628718" name="ftkPlots170303_fig8b.pdf" path="ftkPlots170303_fig8b.pdf" size="4852" user="sschmitt" version="1"
META FILEATTACHMENT attachment="ftkPlots170303_fig8b.png" attr="" comment="Number of 8-layer fits: algorithms with and without cut on NX" date="1488628719" name="ftkPlots170303_fig8b.png" path="ftkPlots170303_fig8b.png" size="62153" user="sschmitt" version="1"
META FILEATTACHMENT attachment="ftkPlots170303_fig9.pdf" attr="" comment="Duplicate patterns multiplicity" date="1488628802" name="ftkPlots170303_fig9.pdf" path="ftkPlots170303_fig9.pdf" size="5970" user="sschmitt" version="1"
META FILEATTACHMENT attachment="ftkPlots170303_fig9.png" attr="" comment="Duplicate patterns multiplicity" date="1488628803" name="ftkPlots170303_fig9.png" path="ftkPlots170303_fig9.png" size="39513" user="sschmitt" version="1"
META FILEATTACHMENT attachment="ftkPlots170303_fig9a.pdf" attr="" comment="Duplicate patterns multiplicity" date="1488628803" name="ftkPlots170303_fig9a.pdf" path="ftkPlots170303_fig9a.pdf" size="4657" user="sschmitt" version="1"
META FILEATTACHMENT attachment="ftkPlots170303_fig9a.png" attr="" comment="Duplicate patterns multiplicity" date="1488628803" name="ftkPlots170303_fig9a.png" path="ftkPlots170303_fig9a.png" size="41352" user="sschmitt" version="1"
META FILEATTACHMENT attachment="ftkPlots170303_fig9b.pdf" attr="" comment="Duplicate patterns multiplicity" date="1488628803" name="ftkPlots170303_fig9b.pdf" path="ftkPlots170303_fig9b.pdf" size="4660" user="sschmitt" version="1"
META FILEATTACHMENT attachment="ftkPlots170303_fig9b.png" attr="" comment="Duplicate patterns multiplicity" date="1488628803" name="ftkPlots170303_fig9b.png" path="ftkPlots170303_fig9b.png" size="41617" user="sschmitt" version="1"
META FILEATTACHMENT attachment="ftkPlots170303_fig10.pdf" attr="" comment="Survey of parameter space with and with out cut on NX" date="1488628870" name="ftkPlots170303_fig10.pdf" path="ftkPlots170303_fig10.pdf" size="6874" user="sschmitt" version="1"
META FILEATTACHMENT attachment="ftkPlots170303_fig10.png" attr="" comment="Survey of parameter space with and with out cut on NX" date="1488628871" name="ftkPlots170303_fig10.png" path="ftkPlots170303_fig10.png" size="84058" user="sschmitt" version="1"

Revision 142017-03-03 - StefanSchmitt

Line: 1 to 1
 
META TOPICPARENT name="TriggerPublicResults"
AtlasPublicTopicHeader.png
Line: 11 to 11
  This page collects public results for the performance of the FTK system. The technical design report can be found here. Figures from the TDR are collected on this page.
Deleted:
<
<
<!--

2017 Pattern Bank Production Plots

Coverage distribution of the generated patterns. One billion patterns per tower are generated using the FTK fit constants. Each pattern corresponds to 15-bit hit coordinates measured in eight detector planes (three pixel detector planes and five strip detector planes). Each pixel coordinate encodes information along two directions in a single 15-bit word. There are 32 barrel (|η|<1.6) and 32 endcap (|η|>1.6) towers. Within the 109 patterns generated, there may be duplicates. The coverage is defined as the multiplicity at which a particular pattern is generated. The coverage distribution is shown separately for barrel and endcap towers. Patterns with large coverage are the most important for achieving good pattern recognition efficiencies.
png pdf
Distributions of the number NX of active ternary bits per AM address (top left), the number of generated patterns per AM address Ngen (top right), and the fraction of generated to encoded patterns per AM address Ngen/2NX (lower row). The distributions are shown separately for barrel (|η|<1.6) and endcap (|η|>1.6) towers. For each of the 64 towers 16.8 million AM addresses are available, whereas 109 patterns have been generated. Each AM address holds eight 15-bit words of information about hits in the eight detector planes. Each 15-bit word has up to three ternary bits, which encode the information 0, 1 or X, where X means the ternary bit is "active" and the values 0 or 1 are both valid. The ternary bits allow for large numbers (2NX) of patterns to be encoded at a single AM address. For this figure, ternary bit patterns are generated for the configuration (1+1)pix(1)sct with 1 ternary bit for each of the two directions in each of the three pixel (pix) layers and with 1 ternary bit for each of the five strip (sct) layers. The generated patterns are ordered by decreasing coverage and are assigned to AM addresses. The resulting NX distribution exhibits tails to large NX, corresponding to AM addresses which encode a large number of possible patterns and thus are susceptible to random coincidences. Such patterns are also reflected by low values of Ngen/2NX.
png pdf (NXpng pdf) (Ngenpng pdf) (Ngen/2NXpng pdf)
-->
 

2014 Performance Plots

<!-- border=1 cellpadding=10 cellspacing=10>                                  -->

Revision 132017-03-03 - StefanSchmitt

Line: 1 to 1
 
META TOPICPARENT name="TriggerPublicResults"
AtlasPublicTopicHeader.png
Line: 375 to 375
 
META FILEATTACHMENT attachment="muons_eta.png" attr="" comment="" date="1464603826" name="muons_eta.png" path="muons_eta.png" size="25011" user="sgkait" version="1"
META FILEATTACHMENT attachment="ttbar_chi2.png" attr="" comment="" date="1464603826" name="ttbar_chi2.png" path="ttbar_chi2.png" size="22808" user="sgkait" version="1"
META FILEATTACHMENT attachment="ttbar_eta.png" attr="" comment="" date="1464603826" name="ttbar_eta.png" path="ttbar_eta.png" size="25632" user="sgkait" version="1"
Changed:
<
<
META FILEATTACHMENT attachment="ftkPlots170302_fig1.png" attr="" comment="bank production coverage distribution" date="1488479068" name="ftkPlots170302_fig1.png" path="ftkPlots170302_fig1.png" size="59620" user="sschmitt" version="1"
META FILEATTACHMENT attachment="ftkPlots170302_fig1.pdf" attr="" comment="bank production coverage distribution" date="1488479068" name="ftkPlots170302_fig1.pdf" path="ftkPlots170302_fig1.pdf" size="16175" user="sschmitt" version="1"
META FILEATTACHMENT attachment="ftkPlots170302_fig2.png" attr="" comment="" date="1488479666" name="ftkPlots170302_fig2.png" path="ftkPlots170302_fig2.png" size="83530" user="sschmitt" version="1"
META FILEATTACHMENT attachment="ftkPlots170302_fig2.pdf" attr="" comment="" date="1488479666" name="ftkPlots170302_fig2.pdf" path="ftkPlots170302_fig2.pdf" size="16896" user="sschmitt" version="1"
META FILEATTACHMENT attachment="ftkPlots170302_fig2a.png" attr="" comment="" date="1488479666" name="ftkPlots170302_fig2a.png" path="ftkPlots170302_fig2a.png" size="53560" user="sschmitt" version="1"
META FILEATTACHMENT attachment="ftkPlots170302_fig2a.pdf" attr="" comment="" date="1488479666" name="ftkPlots170302_fig2a.pdf" path="ftkPlots170302_fig2a.pdf" size="9640" user="sschmitt" version="1"
META FILEATTACHMENT attachment="ftkPlots170302_fig2b.png" attr="" comment="" date="1488479666" name="ftkPlots170302_fig2b.png" path="ftkPlots170302_fig2b.png" size="65105" user="sschmitt" version="1"
META FILEATTACHMENT attachment="ftkPlots170302_fig2b.pdf" attr="" comment="" date="1488479666" name="ftkPlots170302_fig2b.pdf" path="ftkPlots170302_fig2b.pdf" size="13768" user="sschmitt" version="1"
META FILEATTACHMENT attachment="ftkPlots170302_fig2c.png" attr="" comment="" date="1488479666" name="ftkPlots170302_fig2c.png" path="ftkPlots170302_fig2c.png" size="58024" user="sschmitt" version="1"
META FILEATTACHMENT attachment="ftkPlots170302_fig2c.pdf" attr="" comment="" date="1488479666" name="ftkPlots170302_fig2c.pdf" path="ftkPlots170302_fig2c.pdf" size="10039" user="sschmitt" version="1"
>
>
META FILEATTACHMENT attachment="ftkPlots170302_fig1.png" attr="h" comment="bank production coverage distribution" date="1488479068" name="ftkPlots170302_fig1.png" path="ftkPlots170302_fig1.png" size="59620" user="sschmitt" version="1"
META FILEATTACHMENT attachment="ftkPlots170302_fig1.pdf" attr="h" comment="bank production coverage distribution" date="1488479068" name="ftkPlots170302_fig1.pdf" path="ftkPlots170302_fig1.pdf" size="16175" user="sschmitt" version="1"
META FILEATTACHMENT attachment="ftkPlots170302_fig2.png" attr="h" comment="" date="1488479666" name="ftkPlots170302_fig2.png" path="ftkPlots170302_fig2.png" size="83530" user="sschmitt" version="1"
META FILEATTACHMENT attachment="ftkPlots170302_fig2.pdf" attr="h" comment="" date="1488479666" name="ftkPlots170302_fig2.pdf" path="ftkPlots170302_fig2.pdf" size="16896" user="sschmitt" version="1"
META FILEATTACHMENT attachment="ftkPlots170302_fig2a.png" attr="h" comment="" date="1488479666" name="ftkPlots170302_fig2a.png" path="ftkPlots170302_fig2a.png" size="53560" user="sschmitt" version="1"
META FILEATTACHMENT attachment="ftkPlots170302_fig2a.pdf" attr="h" comment="" date="1488479666" name="ftkPlots170302_fig2a.pdf" path="ftkPlots170302_fig2a.pdf" size="9640" user="sschmitt" version="1"
META FILEATTACHMENT attachment="ftkPlots170302_fig2b.png" attr="h" comment="" date="1488479666" name="ftkPlots170302_fig2b.png" path="ftkPlots170302_fig2b.png" size="65105" user="sschmitt" version="1"
META FILEATTACHMENT attachment="ftkPlots170302_fig2b.pdf" attr="h" comment="" date="1488479666" name="ftkPlots170302_fig2b.pdf" path="ftkPlots170302_fig2b.pdf" size="13768" user="sschmitt" version="1"
META FILEATTACHMENT attachment="ftkPlots170302_fig2c.png" attr="h" comment="" date="1488479666" name="ftkPlots170302_fig2c.png" path="ftkPlots170302_fig2c.png" size="58024" user="sschmitt" version="1"
META FILEATTACHMENT attachment="ftkPlots170302_fig2c.pdf" attr="h" comment="" date="1488479666" name="ftkPlots170302_fig2c.pdf" path="ftkPlots170302_fig2c.pdf" size="10039" user="sschmitt" version="1"

Revision 122017-03-02 - StefanSchmitt

Line: 1 to 1
 
META TOPICPARENT name="TriggerPublicResults"
AtlasPublicTopicHeader.png
Line: 11 to 11
  This page collects public results for the performance of the FTK system. The technical design report can be found here. Figures from the TDR are collected on this page.
Added:
>
>
<!--
 

2017 Pattern Bank Production Plots

Added:
>
>
Coverage distribution of the generated patterns. One billion patterns per tower are generated using the FTK fit constants. Each pattern corresponds to 15-bit hit coordinates measured in eight detector planes (three pixel detector planes and five strip detector planes). Each pixel coordinate encodes information along two directions in a single 15-bit word. There are 32 barrel (|η|<1.6) and 32 endcap (|η|>1.6) towers. Within the 109 patterns generated, there may be duplicates. The coverage is defined as the multiplicity at which a particular pattern is generated. The coverage distribution is shown separately for barrel and endcap towers. Patterns with large coverage are the most important for achieving good pattern recognition efficiencies.

png pdf
 Distributions of the number NX of active ternary bits per AM address (top left), the number of generated patterns per AM address Ngen (top right), and the fraction of generated to encoded patterns per AM address Ngen/2NX (lower row). The distributions are shown separately for barrel (|η|<1.6) and endcap
Changed:
<
<
(|η>1.6) towers.
>
>
(|η|>1.6) towers.
 For each of the 64 towers 16.8 million AM addresses are available, whereas 109 patterns have been generated. Each AM address holds eight 15-bit words
Line: 41 to 62
  possible patterns and thus are susceptible to random coincidences. Such patterns are also reflected by low values of Ngen/2NX.
Changed:
<
<

png pdf
>
>

png pdf (NXpng pdf) (Ngenpng pdf) (Ngen/2NXpng pdf)
 
Added:
>
>
-->
 

2014 Performance Plots

Line: 347 to 375
 
META FILEATTACHMENT attachment="muons_eta.png" attr="" comment="" date="1464603826" name="muons_eta.png" path="muons_eta.png" size="25011" user="sgkait" version="1"
META FILEATTACHMENT attachment="ttbar_chi2.png" attr="" comment="" date="1464603826" name="ttbar_chi2.png" path="ttbar_chi2.png" size="22808" user="sgkait" version="1"
META FILEATTACHMENT attachment="ttbar_eta.png" attr="" comment="" date="1464603826" name="ttbar_eta.png" path="ttbar_eta.png" size="25632" user="sgkait" version="1"
Added:
>
>
META FILEATTACHMENT attachment="ftkPlots170302_fig1.png" attr="" comment="bank production coverage distribution" date="1488479068" name="ftkPlots170302_fig1.png" path="ftkPlots170302_fig1.png" size="59620" user="sschmitt" version="1"
META FILEATTACHMENT attachment="ftkPlots170302_fig1.pdf" attr="" comment="bank production coverage distribution" date="1488479068" name="ftkPlots170302_fig1.pdf" path="ftkPlots170302_fig1.pdf" size="16175" user="sschmitt" version="1"
META FILEATTACHMENT attachment="ftkPlots170302_fig2.png" attr="" comment="" date="1488479666" name="ftkPlots170302_fig2.png" path="ftkPlots170302_fig2.png" size="83530" user="sschmitt" version="1"
META FILEATTACHMENT attachment="ftkPlots170302_fig2.pdf" attr="" comment="" date="1488479666" name="ftkPlots170302_fig2.pdf" path="ftkPlots170302_fig2.pdf" size="16896" user="sschmitt" version="1"
META FILEATTACHMENT attachment="ftkPlots170302_fig2a.png" attr="" comment="" date="1488479666" name="ftkPlots170302_fig2a.png" path="ftkPlots170302_fig2a.png" size="53560" user="sschmitt" version="1"
META FILEATTACHMENT attachment="ftkPlots170302_fig2a.pdf" attr="" comment="" date="1488479666" name="ftkPlots170302_fig2a.pdf" path="ftkPlots170302_fig2a.pdf" size="9640" user="sschmitt" version="1"
META FILEATTACHMENT attachment="ftkPlots170302_fig2b.png" attr="" comment="" date="1488479666" name="ftkPlots170302_fig2b.png" path="ftkPlots170302_fig2b.png" size="65105" user="sschmitt" version="1"
META FILEATTACHMENT attachment="ftkPlots170302_fig2b.pdf" attr="" comment="" date="1488479666" name="ftkPlots170302_fig2b.pdf" path="ftkPlots170302_fig2b.pdf" size="13768" user="sschmitt" version="1"
META FILEATTACHMENT attachment="ftkPlots170302_fig2c.png" attr="" comment="" date="1488479666" name="ftkPlots170302_fig2c.png" path="ftkPlots170302_fig2c.png" size="58024" user="sschmitt" version="1"
META FILEATTACHMENT attachment="ftkPlots170302_fig2c.pdf" attr="" comment="" date="1488479666" name="ftkPlots170302_fig2c.pdf" path="ftkPlots170302_fig2c.pdf" size="10039" user="sschmitt" version="1"

Revision 112017-03-02 - StefanSchmitt

Line: 1 to 1
 
META TOPICPARENT name="TriggerPublicResults"
AtlasPublicTopicHeader.png
Line: 11 to 11
  This page collects public results for the performance of the FTK system. The technical design report can be found here. Figures from the TDR are collected on this page.
Added:
>
>

2017 Pattern Bank Production Plots

Distributions of the number NX of active ternary bits per AM address (top left), the number of generated patterns per AM address Ngen (top right), and the fraction of generated to encoded patterns per AM address Ngen/2NX (lower row). The distributions are shown separately for barrel (|η|<1.6) and endcap (|η>1.6) towers. For each of the 64 towers 16.8 million AM addresses are available, whereas 109 patterns have been generated. Each AM address holds eight 15-bit words of information about hits in the eight detector planes. Each 15-bit word has up to three ternary bits, which encode the information 0, 1 or X, where X means the ternary bit is "active" and the values 0 or 1 are both valid. The ternary bits allow for large numbers (2NX) of patterns to be encoded at a single AM address. For this figure, ternary bit patterns are generated for the configuration (1+1)pix(1)sct with 1 ternary bit for each of the two directions in each of the three pixel (pix) layers and with 1 ternary bit for each of the five strip (sct) layers. The generated patterns are ordered by decreasing coverage and are assigned to AM addresses. The resulting NX distribution exhibits tails to large NX, corresponding to AM addresses which encode a large number of possible patterns and thus are susceptible to random coincidences. Such patterns are also reflected by low values of Ngen/2NX.
png pdf
 

2014 Performance Plots

<!-- border=1 cellpadding=10 cellspacing=10>                                  -->

Revision 102016-07-12 - LaurenTompkins

Line: 1 to 1
 
META TOPICPARENT name="TriggerPublicResults"
AtlasPublicTopicHeader.png
Line: 13 to 13
 

2014 Performance Plots

Changed:
<
<
border=1 cellpadding=10 cellspacing=10>
>
>
<!-- border=1 cellpadding=10 cellspacing=10>                                  -->
 
Changed:
<
<
>
>
  The ATLAS HLT beam spot finding and primary vertex reconstruction algorithm adapted for FTK tracks are used to find all primary vertices in the event. The resolution along the beam axis (z) of the FTK primary vertices is dependent on the number of tracks associated with the vertex. The plot shows the z resolution as a function of the number of FTK tracks per primary vertex for all primary vertices in the event. For a 20-track vertex the z-resolution is  40m. The sample used is tt MC with
Line: 115 to 115
  The FTK selection at HLT requires N_tracks (deltaR < 0.1) <= 3 and N_tracks (0.1< deltaR < 0.4) <= 2 while the calorimeter clusters selection requires clusters with E_T>25 GeV, f_core0.079 where f_core is ratio of the transverse energy in a cone of radius 0.2 to the transverse energy in a cone of radius 0.4 around the tau direction and R_cal = (Sigma E_T * dR)/ (Sigma E_T). In both cases, the selections have be tuned to give the same background rejection factor of 2 per Level-1 tau candidate (with p_T > 12 GeV and calorimetric isolation of 4 GeV). This plot is an update and a summary with respect to figure 39 of the FTK TDR [CERN-LHCC-2013-007] that now includes the use of IBL.
Added:
>
>
 
png pdf
Line: 126 to 127
  The red upwards pointing triangle show the per event efficiency for applying the FTK selection at HLT and the primary vertex consistency requirement. The black star shows the efficiency of applying the calorimeter cluster selection (f_core < 0.59 and R_cal>0.079 where f_core is ratio of the transverse energy in a cone of radius 0.2 to the transverse energy in a cone of radius 0.4 around the tau direction and R_cal = ( Sigma E_T * dR )/ (Sigma E_T) ) and adding the requirement that both the Level-1 tau candidates have E_T > 32 GeV. The black triangle shows the efficiency for the same selection described above but with Level-1 tau candidates satisfying E_T >40 GeV for the first and E_T > 25 GeV for the second. The plot summarizes tau studies in the FTK TDR [CERN-LHCC-2013-007] that have been updated and now include the use of the IBL. The Level-1 seed has been updated to the one expected in the 2015 run and the background sample changed from WH-> lnuqq to the multijet sample (with =60).
Changed:
<
<
>
>
 
png pdf

Revision 92016-06-30 - StamatiosGkaitatzis

Line: 1 to 1
 
META TOPICPARENT name="TriggerPublicResults"
AtlasPublicTopicHeader.png
Line: 6 to 7
 
<!-- this line is optional -->
Deleted:
<
<
 

Introduction

Deleted:
<
<
This page collects public results for the performance of the FTK system. The technical design report can be found here. Figures from the TDR are collected on this page.
 
Added:
>
>
This page collects public results for the performance of the FTK system. The technical design report can be found here. Figures from the TDR are collected on this page.
 

2014 Performance Plots

Deleted:
<
<
 
Added:
>
>
border=1 cellpadding=10 cellspacing=10>
 
Changed:
<
<
>
>
  The ATLAS HLT beam spot finding and primary vertex reconstruction algorithm adapted for FTK tracks are used to find all primary vertices in the event. The resolution along the beam axis (z) of the FTK primary vertices is dependent on the number of tracks associated with the vertex. The plot shows the z resolution as a function of the number of FTK tracks per primary vertex for all primary
Changed:
<
<
vertices in the event. For a 20-track vertex the z-resolution is  40m. The sample used is tt MC with
>
>
vertices in the event. For a 20-track vertex the z-resolution is  40m. The sample used is tt MC with
 IBL for 14 TeV pp collisions with an average of 60 overlapping pp interaction. This plot is an update
Changed:
<
<
of figure 28 of the FTK TDR [CERN-LHCC-2013-007] which showed a z-resolution of  70m for a
>
>
of figure 28 of the FTK TDR [CERN-LHCC-2013-007] which showed a z-resolution of  70m for a
 20-track vertex.

<!-- Fast TracKer (FTK) updates to TDR for IBL (ATL-COM-DAQ-2014-014) -->
Changed:
<
<
>
>
 
Changed:
<
<

>
>

 png pdf
Changed:
<
<

>
>
 
Changed:
<
<
Track multiplicities of  candidates computed with FTK tracks for a signal cone with dR < 0.1 (top) and for an isolation ring with 0.1 < dR < 0.4 (bottom). A signal sample of  from gluon fusion H -> tautau -> hadhad events is shown in blue, and a multijet QCD background sample is shown in red. Both
>
>
Track multiplicities of  candidates computed with FTK tracks for a signal cone with d?R < 0.1 (top) and for an isolation ring with 0.1 < ?dR < 0.4 (bottom). A signal sample of  from gluon fusion H -> tautau -> hadhad events is shown in blue, and a multijet QCD background sample is shown in red. Both
 signal and background samples are produced with = 60 at sqrt(s) = 14 TeV. The Level-1 trigger used is TAU12I, which requires a  candidate with less than 4 GeV of calorimetric isolation energy and a pT threshold of 12 GeV. The track multiplicities in the signal cone and in the isolation ring are
Changed:
<
<
defined as follows: the leading track within dR < 0.2 from the Level-1  direction is determined; the track multiplicity in the signal cone (N_SC) is obtained by counting all tracks within dR_SC < 0.1 from the
>
>
defined as follows: the leading track within d?R < 0.2 from the Level-1  direction is determined; the track multiplicity in the signal cone (N_SC) is obtained by counting all tracks within ?dR_SC < 0.1 from the
 leading track direction; the track multiplicity in the isolation ring (N_IR) is obtained by counting all tracks
Changed:
<
<
at a distance 0.1 <dR_IR < 0.4 from the leading tracks direction; if no leading track is found, the Level-1
>
>
at a distance 0.1 <d?R_IR < 0.4 from the leading tracks direction; if no leading track is found, the Level-1
  direction is used as the reference direction to define the track multiplicity in the isolation ring. The tracks considered to calculate the multiplicities N_SC and N_IR are required to fulfill the following criteria:
Changed:
<
<
pT > 1 GeV; |d0| < 2 mm; |z0|<150 mm; chi^2/N_dof < 4; the di ffrence between the z_0 of the track and z_0 of the leading track in the cone < 2 mm. For the signal, only Level-1 taus matching within dR < 0.1
>
>
pT > 1 GeV; |d0| < 2 mm; |z0|<150 mm; chi^2/N_dof < 4; the di ffrence between the z_0 of the track and z_0 of the leading track in the cone < 2 mm. For the signal, only Level-1 taus matching within ?dR < 0.1
 to a truth tau have been considered. As expected, the N_IR distribution is much broader for the multijet QCD background than for the signal. This plot is an update and a summary with respect to figures 35 and 37 of the FTK TDR [CERN-LHCC-2013-007] that now includes the use of IBL. The Level-1 seed has been updated to the expected 2015 trigger configuration and the background sample changed from
Changed:
<
<
WH -> lnu qq to the multijet sample (with = 60). The signal cone and isolation ring definitions and the track selection have also been optimized to find the best background rejection at signal eciency
>
>
WH -> lnu qq to the multijet sample (with = 60). The signal cone and isolation ring definitions and the track selection have also been optimized to find the best background rejection at signal e ciency
 larger than 90%.
Changed:
<
<

>
>

 png pdf
Changed:
<
<

>
>

 png pdf
Changed:
<
<

>
>
 
Changed:
<
<
The plot shows the  identification eciency measured in a signal sample of gluon fusion H ->tautau-> hadhad (red triangles, blue circles) and a multijet background sample (black triangles) for a cut-based FTK HLT selection. The HLT-FTK selection is defined as: N_tracks(dR < 0.1) < = 3 and N_tracks(0.1 <d R < 0.4) <=  2. The signal eciency with respect to truth (red triangles) is defined as the fraction of Level-1 taus matched to a true hadronic tau decay and to an offline-tau that pass the HLT-FTK selection; the efficiency with respect to the offline selection (blue circles) is defined as the fraction of Level-1 taus matched to a true hadronic tau decay and to an offline-tau identified with the offline loose Boosted
>
>
The plot shows the  identification e ciency measured in a signal sample of gluon fusion H ->tautau-> hadhad (red triangles, blue circles) and a multijet background sample (black triangles) for a cut-based FTK HLT selection. The HLT-FTK selection is defined as: N_tracks(?dR < 0.1) < = 3 and N_tracks(0.1 <d ?R < 0.4) <= 2. The signal e ciency with respect to truth (red triangles) is defined as the fraction of Level-1 taus matched to a true hadronic tau decay and to an o ffline-tau that pass the HLT-FTK selection; the e fficiency with respect to the o ffline selection (blue circles) is defined as the fraction of Level-1 taus matched to a true hadronic tau decay and to an offl ine-tau identified with the o ffline loose Boosted
 Decision Tree (BDT) [ATLAS-CONF-2013-064] that pass the HLT-FTK selection. The background
Changed:
<
<
efficiency (black triangles) is obtained from a multijet QCD sample and is defined as the fraction of Level-1 taus matched to an offline-tau that pass the HLT-FTK selection. The matching of the Level-1  tau with the true hadronic tau or with the offline-tau is satisfied if it is within dR < 0.2 from the Level-1  direction. In both the signal and background samples, an offline tau match is found for > 97% of the Level-1  candidates. The true taus s are required to have pT > 8 GeV and |eta| < 2.4. The offline taus are offline reconstructed  objects with |eta|< 2.5. Both signal and background samples are produced with = 60
>
>
e fficiency (black triangles) is obtained from a multijet QCD sample and is defined as the fraction of Level-1 taus matched to an o ffline-tau that pass the HLT-FTK selection. The matching of the Level-1  tau with the true hadronic tau or with the o ffline-tau is satisfied if it is within ?dR < 0.2 from the Level-1  direction. In both the signal and background samples, an offl ine tau match is found for > 97% of the Level-1  candidates. The true taus s are required to have pT > 8 GeV and |eta| < 2.4. The o ffline taus are o ffline reconstructed  objects with |eta|< 2.5. Both signal and background samples are produced with = 60
 at sqrt(s) = 14 TeV. This plot is an update and a summary with respect to figures 39 and 42 of the FTK TDR [CERN-LHCC-2013-007] that now includes the use of IBL. The Level-1 seed has been updated to
Changed:
<
<
the expected 2015 trigger configuration and the background sample changed from WH->lnu->qq to the
>
>
the expected 2015 trigger configuration and the background sample changed from WH->lnu->qq to the
 multijet sample (with = 60) and the HLT-FTK selection has been updated.
Changed:
<
<

>
>

 png pdf
Changed:
<
<
>
>
 
Changed:
<
<

The plot shows the tau identification efficiency as a function of Level-1 tau candidate pT for taus from a signal sample of gluon fusion H->tau tau-> had ha events (blue triangles) and from a multijet background sample (black triangles) when a selection based on a multivariate discriminant that uses FTK tracking is applied at the HLT (FTK-BDT).

>
>
The plot shows the tau identification efficiency as a function of Level-1 tau candidate pT for taus from a signal sample of gluon fusion H->tau tau-> had ha events (blue triangles) and from a multijet background sample (black triangles) when a selection based on a multivariate discriminant that uses FTK tracking is applied at the HLT (FTK-BDT).
 The efficiency is defined as the fraction of Level-1 taus matched to a true hadronic tau decay and to an offline-tau identified with the offline loose Boosted Decision Tree (BDT) [ATLAS-CONF-2013-064] that pass the FTK-BDT selection at HLT for the signal and as the fraction of Level-1 taus matched to an offline-tau that pass the FTK-BDT selection for the multijet background. The FTK-BDT selection uses only variables based on FTK tracking. The Level-1 tau candidates are divided in 1-prong (also containing 0-prong) and multi-prong candidates based on the number of FTK associated in the signal cone. The variables that show the most separation power are the invariant mass of the tracks, and the sum of the pT of all tracks in the isolation ring divided by the sum of the pT of all the tracks in the signal region. The two BDTs are then combined to obtain an overall efficiency per Level-1 tau candidate for signal and background.
Changed:
<
<
This plot is an update and a summary with respect to Figures 39 and 42 of the FTK TDR [CERN-LHCC-2013-007] that now includes the use of IBL and a BDT tau selection based on FTK Tracks. The Level-1 seed has been updated to the expected 2015 trigger configuration and the background sample changed from WH->lnuqq to the multijet sample (with =60).
>
>
This plot is an update and a summary with respect to Figures 39 and 42 of the FTK TDR [CERN-LHCC-2013-007] that now includes the use of IBL and a BDT tau selection based on FTK Tracks. The Level-1 seed has been updated to the expected 2015 trigger configuration and the background sample changed from WH->lnuqq to the multijet sample (with =60).
 
Changed:
<
<

>
>

 png pdf
Changed:
<
<

>
>
  The plot shows the tau identification efficiency as a function of the offline-tau pT when applying the FTK selection (blue) and calorimeter clusters selection (red) at HLT. The efficiency is defined as the fraction of Level-1 tau matched to a true hadronic tau decay and to an offline tau identified with the offline loose Boosted Decision Tree (BDT) [ATLAS-CONF-2013-064].
Changed:
<
<
The FTK selection at HLT requires N_tracks (deltaR < 0.1) <= 3 and N_tracks (0.1< deltaR < 0.4) <= 2 while the calorimeter clusters selection requires clusters with E_T>25 GeV, f_core<0.59 and R_cal>0.079 where f_core is ratio of the transverse energy in a cone of radius 0.2 to the transverse energy in a cone of radius 0.4 around the tau direction and R_cal = (Sigma E_T * dR)/ (Sigma E_T). In both cases, the selections have be tuned to give the same background rejection factor of 2 per Level-1 tau candidate (with p_T > 12 GeV and calorimetric isolation of 4 GeV). This plot is an update and a summary with respect to figure 39 of the FTK TDR [CERN-LHCC-2013-007] that now includes the use of IBL.
>
>
The FTK selection at HLT requires N_tracks (deltaR < 0.1) <= 3 and N_tracks (0.1< deltaR < 0.4) <= 2 while the calorimeter clusters selection requires clusters with E_T>25 GeV, f_core0.079 where f_core is ratio of the transverse energy in a cone of radius 0.2 to the transverse energy in a cone of radius 0.4 around the tau direction and R_cal = (Sigma E_T * dR)/ (Sigma E_T). In both cases, the selections have be tuned to give the same background rejection factor of 2 per Level-1 tau candidate (with p_T > 12 GeV and calorimetric isolation of 4 GeV). This plot is an update and a summary with respect to figure 39 of the FTK TDR [CERN-LHCC-2013-007] that now includes the use of IBL.
 
Changed:
<
<

>
>

 png pdf
Changed:
<
<

>
>
 
Changed:
<
<
The plot shows the efficiency per event for a sample of boosted gluon fusion H->tautau->hadhad events, defined by requiring the Higgs pT > 60 GeV, versus the multijet QCD background efficiency for several HLT selections. The Level-1 selection used requires two Level-1 tau candidates with 12 and 20 GeV and a calorimetric isolation of 4 GeV separated in delta R <2.8 , as well as a Level-1 jet candidate with pT> 25 GeV. The red downwards pointing triangle shows the per event efficiency of the HLT selection which requires that the jet and at least one of the two tau to be consistent with the primary vertex (PV). The red circle shows the per event efficiency for applying the FTK selection at HLT (N_tracks (delta R < 0.1) <= 3 and N_tracks (0.1< delta R < 0.4) <= 2 ).
>
>
The plot shows the efficiency per event for a sample of boosted gluon fusion H->tautau->hadhad events, defined by requiring the Higgs pT > 60 GeV, versus the multijet QCD background efficiency for several HLT selections. The Level-1 selection used requires two Level-1 tau candidates with 12 and 20 GeV and a calorimetric isolation of 4 GeV separated in delta R as well as a Level-1 jet candidate with pT> 25 GeV. The red downwards pointing triangle shows the per event efficiency of the HLT selection which requires that the jet and at least one of the two tau to be consistent with the primary vertex (PV). The red circle shows the per event efficiency for applying the FTK selection at HLT (N_tracks (delta R < 0.1) <= 3 and N_tracks (0.1< delta R < 0.4) <= 2 ).
  The red upwards pointing triangle show the per event efficiency for applying the FTK selection at HLT and the primary vertex consistency requirement.
Changed:
<
<
The black star shows the efficiency of applying the calorimeter cluster selection (f_core < 0.59 and R_cal>0.079 where f_core is ratio of the transverse energy in a cone of radius 0.2 to the transverse energy in a cone of radius 0.4 around the tau direction and R_cal = ( Sigma E_T * dR )/ (Sigma E_T) ) and adding the requirement that both the Level-1 tau candidates have E_T > 32 GeV. The black triangle shows the efficiency for the same selection described above but with Level-1 tau candidates satisfying E_T >40 GeV for the first and E_T > 25 GeV for the second. The plot summarizes tau studies in the FTK TDR [CERN-LHCC-2013-007] that have been updated and now include the use of the IBL. The Level-1 seed has been updated to the one expected in the 2015 run and the background sample changed from WH-> lnuqq to the multijet sample (with =60).
>
>
The black star shows the efficiency of applying the calorimeter cluster selection (f_core < 0.59 and R_cal>0.079 where f_core is ratio of the transverse energy in a cone of radius 0.2 to the transverse energy in a cone of radius 0.4 around the tau direction and R_cal = ( Sigma E_T * dR )/ (Sigma E_T) ) and adding the requirement that both the Level-1 tau candidates have E_T > 32 GeV. The black triangle shows the efficiency for the same selection described above but with Level-1 tau candidates satisfying E_T >40 GeV for the first and E_T > 25 GeV for the second. The plot summarizes tau studies in the FTK TDR [CERN-LHCC-2013-007] that have been updated and now include the use of the IBL. The Level-1 seed has been updated to the one expected in the 2015 run and the background sample changed from WH-> lnuqq to the multijet sample (with =60).
 
Changed:
<
<

>
>

 png pdf
Changed:
<
<

>
>
  The transverse impact parameter is shown for tracks associated to light-flavor (black) and heavy-flavor (red) jets. The solid lines show the distribution for the offline tracks, whereas the points show the FTK tracks. The impact parameter is signed such that track displacements in the direction of the jet have positive values, while tracks with displacements opposite of the jet direction are negative. This plot is an update with respect to figure 19 of the FTK TDR [CERN-LHCC-2013-007] that now includes the use of IBL.
Changed:
<
<

>
>

 png pdf
Changed:
<
<

>
>
  The transverse impact parameter and its significance are shown for tracks associated to light-flavor (black) and heavy-flavor (red) jets. The solid lines show the distribution for the offline tracks, whereas the points show the re-fitted FTK tracks.
Line: 163 to 149
 The impact parameter is signed such that track displacements in the direction of the jet have positive values, while tracks with displacements opposite of the jet direction are negative. This plot is an update with respect to figure 19 of the FTK TDR [CERN-LHCC-2013-007] that now includes the use of IBL and the refit of FTK clusters associated to the FTK tracks using the offline algorithm. The clusters associated to the FTK tracks are fit with the global Chi^2 algorithm.
Changed:
<
<
A Chi^2 < 2 cut is applied to the FTK tracks after refit to increase track purity. The narrower d_0 significance core for FTK refitted tracks is a result of overestimated impact parameter uncertainties for the refitted FTK tracks.
>
>
A Chi^2 < 2 cut is applied to the FTK tracks after refit to increase track purity. The narrower d_0 significance core for FTK refitted tracks is a result of overestimated impact parameter uncertainties for the refitted FTK tracks.
 
Changed:
<
<

>
>

 png pdf
Changed:
<
<

>
>

 png pdf
Changed:
<
<

>
>

 png pdf
Changed:
<
<

>
>

 png pdf
Changed:
<
<

>
>
  In run 1, b-jet tagging in the HLT began with a calorimeter-based jet pre-selection that tightened the jet pT thresholds. With the FTK, track finding can be run with looser HLT jet thresholds without putting additional load on the HLT processors. The plot shows two such working points from a draft run-2 menu along with some examples of re-optimized working points in which the b-tagging is run with lower jet thresholds. Each of the working points shown includes a pre-selection requiring four L1 jets above 20 GeV. %The FTK enables this approach without adding additional load to the HLT processors.
Changed:
<
<
The output rates of the various trigger items are shown as a function of the event-level tth (h->bb) efficiency.
>
>
The output rates of the various trigger items are shown as a function of the event-level tth (h->bb) efficiency.
  All operating points assume the re-fitted FTK performance. The black points show b-jet items that will fit into the HLT constraints without FTK, red points show options with significantly larger input rates possible with FTK. The efficiencies are quoted with respect to the inclusive signal and include the L1 efficiency.
Line: 204 to 184
  The plot summarizes the impact of the FTK b-tagging described in the FTK TDR [CERN-LHCC-2013-007], updated to include the use of the IBL and the refit of FTK tracks.
<!-- Fast TracKer (FTK) updates to TDR for IBL (ATL-COM-DAQ-2014-014) -->
Changed:
<
<
>
>
 
Changed:
<
<

>
>

 png pdf
Changed:
<
<

>
>
  In run 1, b-jet tagging in the HLT began with a calorimeter-based jet pre-selection that tightened the jet \pt thresholds. With the FTK, track finding can be run with looser HLT jet thresholds without putting additional load on the HLT processors. The plot shows two such working points from a draft run-2 menu along with some examples of re-optimized working points in which the b-tagging is run with lower jet thresholds. Each of the working points shown includes a pre-selection requiring four L1 jets above 20 GeV.
Changed:
<
<
The output rates of the various trigger items are shown as a function of the event-level signal efficiency for an exotic 4b signature (G(m=300 GeV)->hh->4b).
>
>
The output rates of the various trigger items are shown as a function of the event-level signal efficiency for an exotic 4b signature (G(m=300 GeV)->hh->4b).
  All operating points assume the re-fitted FTK performance. The black points show proposed b-jet items that will fit into the HLT constraints without FTK, red points show options with significantly larger input rates possible with FTK. The efficiencies are quoted with respect to an offline requirement of four identified b-jets and include the L1 efficiency.
Line: 225 to 203
  For example, the ``2b55_4j55_Medium'' trigger requires at least two medium b-tagged jets above 55 GeV and four or more jets above 55 GeV. The plot summarizes the impact of the FTK b-tagging described in the FTK TDR [CERN-LHCC-2013-007], updated to include the use of the IBL and the refit of FTK tracks.
Deleted:
<
<
 
<!-- Fast TracKer (FTK) updates to TDR for IBL (ATL-COM-DAQ-2014-014) -->
Changed:
<
<
>
>
 
Changed:
<
<

>
>

 png pdf
Changed:
<
<

>
>
  Et distribution for offline b-tagged jets in simulated ttbar events.
Changed:
<
<
The offline jets, shown in yellow, are reconstructed using the anti-kt(R=0.4) algorithm and are required to have |eta| < 2.5 and satisfy the 80% working point of the IP2D b-tagging algorithm [ATLAS-CONF-2010-091].
>
>
The offline jets, shown in yellow, are reconstructed using the anti-kt(R=0.4) algorithm and are required to have |eta| < 2.5 and satisfy the 80% working point of the IP2D b-tagging algorithm [ATLAS-CONF-2010-091].
  The black points show the sub-set of offline jets matching a 20 GeV L1 jet (left) or an FTK track-jet (right).
Changed:
<
<
FTK track jets are reconstructed from FTK tracks [CERN-LHCC-2013-007] with |z0 x sin(theta)| < 2 mm using the anti-kt(R=0.4) algorithm.
>
>
FTK track jets are reconstructed from FTK tracks [CERN-LHCC-2013-007] with |z0 x sin(theta)| < 2 mm using the anti-kt(R=0.4) algorithm.
  The z0 is calculated with respect to the primary vertex found using the FTK tracks. The FTK track jets are required to consist of at least two tracks and have transverse momentum greater than 5 GeV. L1 jets are reconstructed from trigger towers using a sliding window algorithm.
Line: 251 to 225
  This can increase the trigger acceptance for b-jets at low transverse energies in events triggered at Level 1 by additional signatures besides the b-jets themselves. In addition, where the jet Et is low, the FTK tracks can help to distinguish jets from the primary interaction from additional low Et jets arising from pileup interactions.
Changed:
<
<

>
>

 eps pdf
Changed:
<
<

>
>

 eps pdf
Added:
>
>
 
Changed:
<
<
>
>
Pixel cluster size distribution for a tt̄ sample with pile-up 60 at 14 TeV. The clustering algorithm used is the grid clustering with the grid dimensions being 8 columns and 21 rows.
 
Added:
>
>
Figure 2: Comparison of the resolution of track parameter η for a single muon sample with no pile-up using the three different clustering algorithms. The ratio indicated by the blue markers is the ratio of the fully realistic implementation over the ideal, while the the red markers show the ratio of the partially realistic implementation over the ideal. The ideal clustering algorithm places no limits on the size of the cluster, while in the ideal centroid calculation the centroid is calculated as the ToT-weighted average of the cluster. On the realistic clustering implementation, the grid clustering is used, with a grid of 8 21 pixels, limiting the maximum cluster size, while in realistic centroid calculation the centroid is the center of a bounding box containing the cluster.
 
Added:
>
>
Comparison of the resolution of track parameter η for a tt̄ sample with pile-up 60 at √s = 14 TeV using the three different clustering algorithms. The ratio indicated by the blue markers is the ratio of the fully realistic implementation over the ideal, while the the red markers show the ratio of the partially realistic implementation over the ideal. The ideal clustering algorithm places no limits on the size of the cluster, while in the ideal centroid calculation the centroid is calculated as the ToT-weighted average of the cluster. On the real istic clustering implementation, the grid clustering is used, with a grid of 8 21 pixels, limiting the maximum cluster size, while in realistic centroid calculation the centroid is the center of a bounding box containing the cluster.
 
Changed:
<
<
>
>
Comparison of the χ 2 distribution for a single muon sample with no pile-up using the three different clustering algorithms. The ratio indicated by the blue markers is the ratio of the fully realistic implementation over the ideal, while the the red markers show the ratio of the partially realistic implementation over the ideal. The ideal clustering algorithm places no limits on the size of the cluster, while in the ideal centroid calculation the centroid is calculated as the ToT-weighted average of the cluster. On the realistic clustering implementation, the grid clustering is used, with a grid of 8 21 pixels, limiting the maximum cluster size, while in realistic centroid calculation the centroid is the center of a bounding box containing the cluster.
 
Added:
>
>

Comparison of the χ 2 distribution for a tt̄ sample with pile-up 60 at √s = 14 TeV using the three different clustering algorithms. The ratio indicated by the blue markers is the ratio of the fully realistic implementation over the ideal, while the the red markers show the ratio of the partially realistic implementation over the ideal. The ideal clustering algorithm places no limits on the size of the cluster, while in the ideal centroid calculation the centroid is calculated as the ToT-weighted average of the cluster. On the realistic clustering implementation, the grid clustering is used, with a grid of 8 21 pixels, limiting the maximum cluster size, while in realistic centroid calculation the centroid is the center of a bounding box containing the cluster.
 
<!-- ********************************************************* -->
<!-- Do NOT remove the remaining lines, but add requested info as appropriate-->

Revision 82016-05-30 - StamatiosGkaitatzis

Line: 1 to 1
 
META TOPICPARENT name="TriggerPublicResults"
AtlasPublicTopicHeader.png
Line: 325 to 325
 
META FILEATTACHMENT attachment="FTKTrkJetTurnOnWrtBtag.png" attr="" comment="" date="1408544204" name="FTKTrkJetTurnOnWrtBtag.png" path="FTKTrkJetTurnOnWrtBtag.png" size="19347" user="johnda" version="1"
META FILEATTACHMENT attachment="L1TurnOnWrtBtag.png" attr="" comment="" date="1408544252" name="L1TurnOnWrtBtag.png" path="L1TurnOnWrtBtag.png" size="19280" user="johnda" version="1"
META FILEATTACHMENT attachment="FTKTrkJetTurnOnWrtBtag.eps" attr="" comment="" date="1408550752" name="FTKTrkJetTurnOnWrtBtag.eps" path="FTKTrkJetTurnOnWrtBtag.eps" size="21574" user="johnda" version="1"
Added:
>
>
META FILEATTACHMENT attachment="8x10.png" attr="" comment="" date="1464603826" name="8x10.png" path="8x10.png" size="15589" user="sgkait" version="1"
META FILEATTACHMENT attachment="muons_chi2.png" attr="" comment="" date="1464603826" name="muons_chi2.png" path="muons_chi2.png" size="24816" user="sgkait" version="1"
META FILEATTACHMENT attachment="muons_eta.png" attr="" comment="" date="1464603826" name="muons_eta.png" path="muons_eta.png" size="25011" user="sgkait" version="1"
META FILEATTACHMENT attachment="ttbar_chi2.png" attr="" comment="" date="1464603826" name="ttbar_chi2.png" path="ttbar_chi2.png" size="22808" user="sgkait" version="1"
META FILEATTACHMENT attachment="ttbar_eta.png" attr="" comment="" date="1464603826" name="ttbar_eta.png" path="ttbar_eta.png" size="25632" user="sgkait" version="1"

Revision 72014-08-20 - JohnAlison

Line: 1 to 1
 
META TOPICPARENT name="TriggerPublicResults"
AtlasPublicTopicHeader.png
Line: 324 to 324
 
META FILEATTACHMENT attachment="FTKTrkJetTurnOnWrtBtag.pdf" attr="" comment="" date="1408544035" name="FTKTrkJetTurnOnWrtBtag.pdf" path="FTKTrkJetTurnOnWrtBtag.pdf" size="18507" user="johnda" version="1"
META FILEATTACHMENT attachment="FTKTrkJetTurnOnWrtBtag.png" attr="" comment="" date="1408544204" name="FTKTrkJetTurnOnWrtBtag.png" path="FTKTrkJetTurnOnWrtBtag.png" size="19347" user="johnda" version="1"
META FILEATTACHMENT attachment="L1TurnOnWrtBtag.png" attr="" comment="" date="1408544252" name="L1TurnOnWrtBtag.png" path="L1TurnOnWrtBtag.png" size="19280" user="johnda" version="1"
Added:
>
>
META FILEATTACHMENT attachment="FTKTrkJetTurnOnWrtBtag.eps" attr="" comment="" date="1408550752" name="FTKTrkJetTurnOnWrtBtag.eps" path="FTKTrkJetTurnOnWrtBtag.eps" size="21574" user="johnda" version="1"

Revision 62014-08-20 - JohnAlison

Line: 1 to 1
 
META TOPICPARENT name="TriggerPublicResults"
AtlasPublicTopicHeader.png
Line: 236 to 236
 
Added:
>
>

Et distribution for offline b-tagged jets in simulated ttbar events. The offline jets, shown in yellow, are reconstructed using the anti-kt(R=0.4) algorithm and are required to have |eta| < 2.5 and satisfy the 80% working point of the IP2D b-tagging algorithm [ATLAS-CONF-2010-091]. The black points show the sub-set of offline jets matching a 20 GeV L1 jet (left) or an FTK track-jet (right). FTK track jets are reconstructed from FTK tracks [CERN-LHCC-2013-007] with |z0 x sin(theta)| < 2 mm using the anti-kt(R=0.4) algorithm. The z0 is calculated with respect to the primary vertex found using the FTK tracks. The FTK track jets are required to consist of at least two tracks and have transverse momentum greater than 5 GeV. L1 jets are reconstructed from trigger towers using a sliding window algorithm. The bottom panels show the ratio of the matched jets to the full unbiased distribution. The high CPU consumption required by the tracking in the High Level Trigger means for b-tagging, the tracking must be seeded by jets found at L1 with a reasonably high (~20 GeV) Et threshold in order to reduce the rate to a level where the tracking can be performed. With the FTK, full scan b-tagging can be performed at the full Level 1 output rate, independently of jets found at L1. This can increase the trigger acceptance for b-jets at low transverse energies in events triggered at Level 1 by additional signatures besides the b-jets themselves. In addition, where the jet Et is low, the FTK tracks can help to distinguish jets from the primary interaction from additional low Et jets arising from pileup interactions.


eps pdf


eps pdf

 
Line: 248 to 278
 
<!-- For significant updates to the topic, consider adding your 'signature' (beneath this editing box) -->
Major updates:
Added:
>
>
-- JohnAlison - 20 Aug 2014
 -- LaurenTompkins - 13 May 2014

<!-- Person responsible for the page: 
Line: 260 to 291
 
Added:
>
>
 
META FILEATTACHMENT attachment="VertexNTrks_vs_VertexZerr_profile.pdf" attr="" comment="Primary vertex pdf" date="1401096780" name="VertexNTrks_vs_VertexZerr_profile.pdf" path="VertexNTrks_vs_VertexZerr_profile.pdf" size="15698" user="tompkins" version="1"
META FILEATTACHMENT attachment="VertexNTrks_vs_VertexZerr_profile.png" attr="" comment="Vertex png" date="1401097808" name="VertexNTrks_vs_VertexZerr_profile.png" path="VertexNTrks_vs_VertexZerr_profile.png" size="12671" user="tompkins" version="2"
META FILEATTACHMENT attachment="ROI_efficiency_sig_bkg.png" attr="" comment="" date="1401102468" name="ROI_efficiency_sig_bkg.png" path="ROI_efficiency_sig_bkg.png" size="10628" user="tompkins" version="1"
Line: 286 to 319
 
META FILEATTACHMENT attachment="ttHHLTRefitClean.pdf" attr="" comment="" date="1403863403" name="ttHHLTRefitClean.pdf" path="ttHHLTRefitClean.pdf" size="49097" user="tompkins" version="1"
META FILEATTACHMENT attachment="Xhh300RefitClean.png" attr="" comment="" date="1403863403" name="Xhh300RefitClean.png" path="Xhh300RefitClean.png" size="9167" user="tompkins" version="1"
META FILEATTACHMENT attachment="Xhh300RefitClean.pdf" attr="" comment="" date="1403863403" name="Xhh300RefitClean.pdf" path="Xhh300RefitClean.pdf" size="49011" user="tompkins" version="1"
Added:
>
>
META FILEATTACHMENT attachment="L1TurnOnWrtBtag.pdf" attr="" comment="" date="1408543967" name="L1TurnOnWrtBtag.pdf" path="L1TurnOnWrtBtag.pdf" size="18237" user="johnda" version="1"
META FILEATTACHMENT attachment="L1TurnOnWrtBtag.eps" attr="" comment="" date="1408544000" name="L1TurnOnWrtBtag.eps" path="L1TurnOnWrtBtag.eps" size="20694" user="johnda" version="1"
META FILEATTACHMENT attachment="FTKTrkJetTurnOnWrtBtag.pdf" attr="" comment="" date="1408544035" name="FTKTrkJetTurnOnWrtBtag.pdf" path="FTKTrkJetTurnOnWrtBtag.pdf" size="18507" user="johnda" version="1"
META FILEATTACHMENT attachment="FTKTrkJetTurnOnWrtBtag.png" attr="" comment="" date="1408544204" name="FTKTrkJetTurnOnWrtBtag.png" path="FTKTrkJetTurnOnWrtBtag.png" size="19347" user="johnda" version="1"
META FILEATTACHMENT attachment="L1TurnOnWrtBtag.png" attr="" comment="" date="1408544252" name="L1TurnOnWrtBtag.png" path="L1TurnOnWrtBtag.png" size="19280" user="johnda" version="1"

Revision 52014-06-27 - LaurenTompkins

Line: 1 to 1
 
META TOPICPARENT name="TriggerPublicResults"
AtlasPublicTopicHeader.png
Line: 186 to 186
 

Added:
>
>

In run 1, b-jet tagging in the HLT began with a calorimeter-based jet pre-selection that tightened the jet pT thresholds. With the FTK, track finding can be run with looser HLT jet thresholds without putting additional load on the HLT processors. The plot shows two such working points from a draft run-2 menu along with some examples of re-optimized working points in which the b-tagging is run with lower jet thresholds. Each of the working points shown includes a pre-selection requiring four L1 jets above 20 GeV. %The FTK enables this approach without adding additional load to the HLT processors. The output rates of the various trigger items are shown as a function of the event-level tth (h->bb) efficiency. All operating points assume the re-fitted FTK performance. The black points show b-jet items that will fit into the HLT constraints without FTK, red points show options with significantly larger input rates possible with FTK. The efficiencies are quoted with respect to the inclusive signal and include the L1 efficiency. The trigger names specify the jet multiplicities, pT thresholds and b-tagging operating points. For example, the ``2b55_4j55_Medium'' trigger requires at least two medium b-tagged jets above 55 GeV and four or more jets above 55 GeV. The plot summarizes the impact of the FTK b-tagging described in the FTK TDR [CERN-LHCC-2013-007], updated to include the use of the IBL and the refit of FTK tracks.

<!-- Fast TracKer (FTK) updates to TDR for IBL (ATL-COM-DAQ-2014-014) -->


png pdf

In run 1, b-jet tagging in the HLT began with a calorimeter-based jet pre-selection that tightened the jet \pt thresholds. With the FTK, track finding can be run with looser HLT jet thresholds without putting additional load on the HLT processors. The plot shows two such working points from a draft run-2 menu along with some examples of re-optimized working points in which the b-tagging is run with lower jet thresholds. Each of the working points shown includes a pre-selection requiring four L1 jets above 20 GeV. The output rates of the various trigger items are shown as a function of the event-level signal efficiency for an exotic 4b signature (G(m=300 GeV)->hh->4b). All operating points assume the re-fitted FTK performance. The black points show proposed b-jet items that will fit into the HLT constraints without FTK, red points show options with significantly larger input rates possible with FTK. The efficiencies are quoted with respect to an offline requirement of four identified b-jets and include the L1 efficiency. The trigger names specify the jet multiplicities, pT thresholds and b-tagging operating points. For example, the ``2b55_4j55_Medium'' trigger requires at least two medium b-tagged jets above 55 GeV and four or more jets above 55 GeV. The plot summarizes the impact of the FTK b-tagging described in the FTK TDR [CERN-LHCC-2013-007], updated to include the use of the IBL and the refit of FTK tracks.

<!-- Fast TracKer (FTK) updates to TDR for IBL (ATL-COM-DAQ-2014-014) -->


png pdf

 
Line: 232 to 282
 
META FILEATTACHMENT attachment="can_OffAll_b_60Refit_d0_signed_b.pdf" attr="" comment="" date="1401105191" name="can_OffAll_b_60Refit_d0_signed_b.pdf" path="can_OffAll_b_60Refit_d0_signed_b.pdf" size="62167" user="tompkins" version="1"
META FILEATTACHMENT attachment="can_OffAll_e_60Refit_d0_signed_e.pdf" attr="" comment="btagging" date="1401105160" name="can_OffAll_e_60Refit_d0_signed_e.pdf" path="can_OffAll_e_60Refit_d0_signed_e.pdf" size="62522" user="tompkins" version="1"
META FILEATTACHMENT attachment="can_OffAll_e_60Refit_d0Sig_signed_e.pdf" attr="" comment="btagging" date="1401105160" name="can_OffAll_e_60Refit_d0Sig_signed_e.pdf" path="can_OffAll_e_60Refit_d0Sig_signed_e.pdf" size="61383" user="tompkins" version="1"
Added:
>
>
META FILEATTACHMENT attachment="ttHHLTRefitClean.png" attr="" comment="" date="1403863403" name="ttHHLTRefitClean.png" path="ttHHLTRefitClean.png" size="9250" user="tompkins" version="1"
META FILEATTACHMENT attachment="ttHHLTRefitClean.pdf" attr="" comment="" date="1403863403" name="ttHHLTRefitClean.pdf" path="ttHHLTRefitClean.pdf" size="49097" user="tompkins" version="1"
META FILEATTACHMENT attachment="Xhh300RefitClean.png" attr="" comment="" date="1403863403" name="Xhh300RefitClean.png" path="Xhh300RefitClean.png" size="9167" user="tompkins" version="1"
META FILEATTACHMENT attachment="Xhh300RefitClean.pdf" attr="" comment="" date="1403863403" name="Xhh300RefitClean.pdf" path="Xhh300RefitClean.pdf" size="49011" user="tompkins" version="1"

Revision 42014-05-26 - LaurenTompkins

Line: 1 to 1
 
META TOPICPARENT name="TriggerPublicResults"
AtlasPublicTopicHeader.png
Line: 95 to 95
 
png pdf
Added:
>
>

The plot shows the tau identification efficiency as a function of Level-1 tau candidate pT for taus from a signal sample of gluon fusion H->tau tau-> had ha events (blue triangles) and from a multijet background sample (black triangles) when a selection based on a multivariate discriminant that uses FTK tracking is applied at the HLT (FTK-BDT). The efficiency is defined as the fraction of Level-1 taus matched to a true hadronic tau decay and to an offline-tau identified with the offline loose Boosted Decision Tree (BDT) [ATLAS-CONF-2013-064] that pass the FTK-BDT selection at HLT for the signal and as the fraction of Level-1 taus matched to an offline-tau that pass the FTK-BDT selection for the multijet background. The FTK-BDT selection uses only variables based on FTK tracking. The Level-1 tau candidates are divided in 1-prong (also containing 0-prong) and multi-prong candidates based on the number of FTK associated in the signal cone. The variables that show the most separation power are the invariant mass of the tracks, and the sum of the pT of all tracks in the isolation ring divided by the sum of the pT of all the tracks in the signal region. The two BDTs are then combined to obtain an overall efficiency per Level-1 tau candidate for signal and background. This plot is an update and a summary with respect to Figures 39 and 42 of the FTK TDR [CERN-LHCC-2013-007] that now includes the use of IBL and a BDT tau selection based on FTK Tracks. The Level-1 seed has been updated to the expected 2015 trigger configuration and the background sample changed from WH->lnuqq to the multijet sample (with =60).


png pdf

The plot shows the tau identification efficiency as a function of the offline-tau pT when applying the FTK selection (blue) and calorimeter clusters selection (red) at HLT. The efficiency is defined as the fraction of Level-1 tau matched to a true hadronic tau decay and to an offline tau identified with the offline loose Boosted Decision Tree (BDT) [ATLAS-CONF-2013-064]. The FTK selection at HLT requires N_tracks (deltaR < 0.1) <= 3 and N_tracks (0.1< deltaR < 0.4) <= 2 while the calorimeter clusters selection requires clusters with E_T>25 GeV, f_core<0.59 and R_cal>0.079 where f_core is ratio of the transverse energy in a cone of radius 0.2 to the transverse energy in a cone of radius 0.4 around the tau direction and R_cal = (Sigma E_T * dR)/ (Sigma E_T). In both cases, the selections have be tuned to give the same background rejection factor of 2 per Level-1 tau candidate (with p_T > 12 GeV and calorimetric isolation of 4 GeV). This plot is an update and a summary with respect to figure 39 of the FTK TDR [CERN-LHCC-2013-007] that now includes the use of IBL.


png pdf

The plot shows the efficiency per event for a sample of boosted gluon fusion H->tautau->hadhad events, defined by requiring the Higgs pT > 60 GeV, versus the multijet QCD background efficiency for several HLT selections. The Level-1 selection used requires two Level-1 tau candidates with 12 and 20 GeV and a calorimetric isolation of 4 GeV separated in delta R <2.8 , as well as a Level-1 jet candidate with pT> 25 GeV. The red downwards pointing triangle shows the per event efficiency of the HLT selection which requires that the jet and at least one of the two tau to be consistent with the primary vertex (PV). The red circle shows the per event efficiency for applying the FTK selection at HLT (N_tracks (delta R < 0.1) <= 3 and N_tracks (0.1< delta R < 0.4) <= 2 ). The red upwards pointing triangle show the per event efficiency for applying the FTK selection at HLT and the primary vertex consistency requirement. The black star shows the efficiency of applying the calorimeter cluster selection (f_core < 0.59 and R_cal>0.079 where f_core is ratio of the transverse energy in a cone of radius 0.2 to the transverse energy in a cone of radius 0.4 around the tau direction and R_cal = ( Sigma E_T * dR )/ (Sigma E_T) ) and adding the requirement that both the Level-1 tau candidates have E_T > 32 GeV. The black triangle shows the efficiency for the same selection described above but with Level-1 tau candidates satisfying E_T >40 GeV for the first and E_T > 25 GeV for the second. The plot summarizes tau studies in the FTK TDR [CERN-LHCC-2013-007] that have been updated and now include the use of the IBL. The Level-1 seed has been updated to the one expected in the 2015 run and the background sample changed from WH-> lnuqq to the multijet sample (with =60).

 
Added:
>
>


png pdf

The transverse impact parameter is shown for tracks associated to light-flavor (black) and heavy-flavor (red) jets. The solid lines show the distribution for the offline tracks, whereas the points show the FTK tracks. The impact parameter is signed such that track displacements in the direction of the jet have positive values, while tracks with displacements opposite of the jet direction are negative. This plot is an update with respect to figure 19 of the FTK TDR [CERN-LHCC-2013-007] that now includes the use of IBL.


png pdf

The transverse impact parameter and its significance are shown for tracks associated to light-flavor (black) and heavy-flavor (red) jets. The solid lines show the distribution for the offline tracks, whereas the points show the re-fitted FTK tracks. The first and third plots show the distributions in the barrel and the second and fourth plots show the distributions in the end-caps. The transverse impact parameter significance is defined as the transverse impact parameter divided by its associated uncertainty. The impact parameter is signed such that track displacements in the direction of the jet have positive values, while tracks with displacements opposite of the jet direction are negative. This plot is an update with respect to figure 19 of the FTK TDR [CERN-LHCC-2013-007] that now includes the use of IBL and the refit of FTK clusters associated to the FTK tracks using the offline algorithm. The clusters associated to the FTK tracks are fit with the global Chi^2 algorithm. A Chi^2 < 2 cut is applied to the FTK tracks after refit to increase track purity. The narrower d_0 significance core for FTK refitted tracks is a result of overestimated impact parameter uncertainties for the refitted FTK tracks.


png pdf


png pdf


png pdf


png pdf

 
Line: 122 to 212
 
META FILEATTACHMENT attachment="VertexNTrks_vs_VertexZerr_profile.pdf" attr="" comment="Primary vertex pdf" date="1401096780" name="VertexNTrks_vs_VertexZerr_profile.pdf" path="VertexNTrks_vs_VertexZerr_profile.pdf" size="15698" user="tompkins" version="1"
META FILEATTACHMENT attachment="VertexNTrks_vs_VertexZerr_profile.png" attr="" comment="Vertex png" date="1401097808" name="VertexNTrks_vs_VertexZerr_profile.png" path="VertexNTrks_vs_VertexZerr_profile.png" size="12671" user="tompkins" version="2"
Added:
>
>
META FILEATTACHMENT attachment="ROI_efficiency_sig_bkg.png" attr="" comment="" date="1401102468" name="ROI_efficiency_sig_bkg.png" path="ROI_efficiency_sig_bkg.png" size="10628" user="tompkins" version="1"
META FILEATTACHMENT attachment="ggHtthh_mu60_Ftk_CompJZ_numTrackIso.png" attr="" comment="" date="1401102468" name="ggHtthh_mu60_Ftk_CompJZ_numTrackIso.png" path="ggHtthh_mu60_Ftk_CompJZ_numTrackIso.png" size="9069" user="tompkins" version="1"
META FILEATTACHMENT attachment="ggHtthh_mu60_Ftk_CompJZ_numTrackCore.png" attr="" comment="" date="1401102468" name="ggHtthh_mu60_Ftk_CompJZ_numTrackCore.png" path="ggHtthh_mu60_Ftk_CompJZ_numTrackCore.png" size="8726" user="tompkins" version="1"
META FILEATTACHMENT attachment="ggHtthh_mu60_Ftk_CompJZ_numTrackCore.pdf" attr="" comment="tau plots" date="1401102928" name="ggHtthh_mu60_Ftk_CompJZ_numTrackCore.pdf" path="ggHtthh_mu60_Ftk_CompJZ_numTrackCore.pdf" size="50594" user="tompkins" version="1"
META FILEATTACHMENT attachment="ggHtthh_mu60_Ftk_CompJZ_numTrackIso.pdf" attr="" comment="tau plots" date="1401102928" name="ggHtthh_mu60_Ftk_CompJZ_numTrackIso.pdf" path="ggHtthh_mu60_Ftk_CompJZ_numTrackIso.pdf" size="50028" user="tompkins" version="1"
META FILEATTACHMENT attachment="ROI_efficiency_sig_bkg.pdf" attr="" comment="more tau plots" date="1401102967" name="ROI_efficiency_sig_bkg.pdf" path="ROI_efficiency_sig_bkg.pdf" size="58130" user="tompkins" version="1"
META FILEATTACHMENT attachment="Sig_L1_TAU12I_eff_BDT_tau_pt.png" attr="" comment="more tau plots" date="1401102967" name="Sig_L1_TAU12I_eff_BDT_tau_pt.png" path="Sig_L1_TAU12I_eff_BDT_tau_pt.png" size="10836" user="tompkins" version="1"
META FILEATTACHMENT attachment="Sig_L1_TAU12I_eff_BDT_tau_pt.pdf" attr="" comment="more tau plots" date="1401102967" name="Sig_L1_TAU12I_eff_BDT_tau_pt.pdf" path="Sig_L1_TAU12I_eff_BDT_tau_pt.pdf" size="61734" user="tompkins" version="1"
META FILEATTACHMENT attachment="eff_events_ggF.pdf" attr="" comment="tau sig eff plots" date="1401103017" name="eff_events_ggF.pdf" path="eff_events_ggF.pdf" size="52623" user="tompkins" version="1"
META FILEATTACHMENT attachment="eff_events_ggF.png" attr="" comment="tau sig eff plots" date="1401103017" name="eff_events_ggF.png" path="eff_events_ggF.png" size="11457" user="tompkins" version="1"
META FILEATTACHMENT attachment="eff_vs_pt_BDT.png" attr="" comment="tau eff plots" date="1401104235" name="eff_vs_pt_BDT.png" path="eff_vs_pt_BDT.png" size="11494" user="tompkins" version="1"
META FILEATTACHMENT attachment="eff_vs_pt_BDT.pdf" attr="" comment="tau eff plots" date="1401104235" name="eff_vs_pt_BDT.pdf" path="eff_vs_pt_BDT.pdf" size="15784" user="tompkins" version="1"
META FILEATTACHMENT attachment="can_OffAll_b_60_d0_signed_b.png" attr="" comment="btagging pngs" date="1401105039" name="can_OffAll_b_60_d0_signed_b.png" path="can_OffAll_b_60_d0_signed_b.png" size="12833" user="tompkins" version="1"
META FILEATTACHMENT attachment="can_OffAll_b_60Refit_d0_signed_b.png" attr="" comment="btagging pngs" date="1401105039" name="can_OffAll_b_60Refit_d0_signed_b.png" path="can_OffAll_b_60Refit_d0_signed_b.png" size="12947" user="tompkins" version="1"
META FILEATTACHMENT attachment="can_OffAll_e_60Refit_d0_signed_e.png" attr="" comment="btagging pngs" date="1401105039" name="can_OffAll_e_60Refit_d0_signed_e.png" path="can_OffAll_e_60Refit_d0_signed_e.png" size="28731" user="tompkins" version="1"
META FILEATTACHMENT attachment="can_OffAll_e_60Refit_d0Sig_signed_e.png" attr="" comment="btagging pngs" date="1401105039" name="can_OffAll_e_60Refit_d0Sig_signed_e.png" path="can_OffAll_e_60Refit_d0Sig_signed_e.png" size="30540" user="tompkins" version="1"
META FILEATTACHMENT attachment="can_OffAll_b_60Refit_d0Sig_signed_b.png" attr="" comment="btagging pngs" date="1401105039" name="can_OffAll_b_60Refit_d0Sig_signed_b.png" path="can_OffAll_b_60Refit_d0Sig_signed_b.png" size="30275" user="tompkins" version="1"
META FILEATTACHMENT attachment="can_OffAll_b_60Refit_d0_signed_b.pdf" attr="" comment="" date="1401105191" name="can_OffAll_b_60Refit_d0_signed_b.pdf" path="can_OffAll_b_60Refit_d0_signed_b.pdf" size="62167" user="tompkins" version="1"
META FILEATTACHMENT attachment="can_OffAll_e_60Refit_d0_signed_e.pdf" attr="" comment="btagging" date="1401105160" name="can_OffAll_e_60Refit_d0_signed_e.pdf" path="can_OffAll_e_60Refit_d0_signed_e.pdf" size="62522" user="tompkins" version="1"
META FILEATTACHMENT attachment="can_OffAll_e_60Refit_d0Sig_signed_e.pdf" attr="" comment="btagging" date="1401105160" name="can_OffAll_e_60Refit_d0Sig_signed_e.pdf" path="can_OffAll_e_60Refit_d0Sig_signed_e.pdf" size="61383" user="tompkins" version="1"

Revision 32014-05-26 - LaurenTompkins

Line: 1 to 1
 
META TOPICPARENT name="TriggerPublicResults"
AtlasPublicTopicHeader.png
Line: 19 to 19
 

Added:
>
>
The ATLAS HLT beam spot finding and primary vertex reconstruction algorithm adapted for FTK tracks are used to find all primary vertices in the event. The resolution along the beam axis (z) of the FTK primary vertices is dependent on the number of tracks associated with the vertex. The plot shows the z resolution as a function of the number of FTK tracks per primary vertex for all primary vertices in the event. For a 20-track vertex the z-resolution is  40m. The sample used is tt MC with IBL for 14 TeV pp collisions with an average of 60 overlapping pp interaction. This plot is an update of figure 28 of the FTK TDR [CERN-LHCC-2013-007] which showed a z-resolution of  70m for a 20-track vertex.
 
Changed:
<
<
Fast TracKer (FTK) updates to TDR for IBL (ATL-COM-DAQ-2014-014)
>
>
<!-- Fast TracKer (FTK) updates to TDR for IBL (ATL-COM-DAQ-2014-014) -->
 
Changed:
<
<

png pdf
>
>

png pdf
 

Changed:
<
<
Placeholder
>
>
Track multiplicities of  candidates computed with FTK tracks for a signal cone with dR < 0.1 (top) and for an isolation ring with 0.1 < dR < 0.4 (bottom). A signal sample of  from gluon fusion H -> tautau -> hadhad events is shown in blue, and a multijet QCD background sample is shown in red. Both signal and background samples are produced with = 60 at sqrt(s) = 14 TeV. The Level-1 trigger used is TAU12I, which requires a  candidate with less than 4 GeV of calorimetric isolation energy and a pT threshold of 12 GeV. The track multiplicities in the signal cone and in the isolation ring are defined as follows: the leading track within dR < 0.2 from the Level-1  direction is determined; the track multiplicity in the signal cone (N_SC) is obtained by counting all tracks within dR_SC < 0.1 from the leading track direction; the track multiplicity in the isolation ring (N_IR) is obtained by counting all tracks at a distance 0.1 <dR_IR < 0.4 from the leading tracks direction; if no leading track is found, the Level-1  direction is used as the reference direction to define the track multiplicity in the isolation ring. The tracks considered to calculate the multiplicities N_SC and N_IR are required to fulfill the following criteria: pT > 1 GeV; |d0| < 2 mm; |z0|<150 mm; chi^2/N_dof < 4; the di ffrence between the z_0 of the track and z_0 of the leading track in the cone < 2 mm. For the signal, only Level-1 taus matching within dR < 0.1 to a truth tau have been considered. As expected, the N_IR distribution is much broader for the multijet QCD background than for the signal. This plot is an update and a summary with respect to figures 35 and 37 of the FTK TDR [CERN-LHCC-2013-007] that now includes the use of IBL. The Level-1 seed has been updated to the expected 2015 trigger configuration and the background sample changed from WH -> lnu qq to the multijet sample (with = 60). The signal cone and isolation ring definitions and the track selection have also been optimized to find the best background rejection at signal eciency larger than 90%.
 
Changed:
<
<

png pdf
>
>

png pdf


png pdf

 
Added:
>
>
 
Added:
>
>
The plot shows the  identification eciency measured in a signal sample of gluon fusion H ->tautau-> hadhad (red triangles, blue circles) and a multijet background sample (black triangles) for a cut-based FTK HLT selection. The HLT-FTK selection is defined as: N_tracks(dR < 0.1) < = 3 and N_tracks(0.1 <d R < 0.4) <=  2. The signal eciency with respect to truth (red triangles) is defined as the fraction of Level-1 taus matched to a true hadronic tau decay and to an offline-tau that pass the HLT-FTK selection; the efficiency with respect to the offline selection (blue circles) is defined as the fraction of Level-1 taus matched to a true hadronic tau decay and to an offline-tau identified with the offline loose Boosted Decision Tree (BDT) [ATLAS-CONF-2013-064] that pass the HLT-FTK selection. The background efficiency (black triangles) is obtained from a multijet QCD sample and is defined as the fraction of Level-1 taus matched to an offline-tau that pass the HLT-FTK selection. The matching of the Level-1  tau with the true hadronic tau or with the offline-tau is satisfied if it is within dR < 0.2 from the Level-1  direction. In both the signal and background samples, an offline tau match is found for > 97% of the Level-1  candidates. The true taus s are required to have pT > 8 GeV and |eta| < 2.4. The offline taus are offline reconstructed  objects with |eta|< 2.5. Both signal and background samples are produced with = 60 at sqrt(s) = 14 TeV. This plot is an update and a summary with respect to figures 39 and 42 of the FTK TDR [CERN-LHCC-2013-007] that now includes the use of IBL. The Level-1 seed has been updated to the expected 2015 trigger configuration and the background sample changed from WH->lnu->qq to the multijet sample (with = 60) and the HLT-FTK selection has been updated.


png pdf
 
Line: 62 to 118
 
<!-- Once this page has been reviewed, please add the name and the date e.g. StephenHaywood - 31 Oct 2006 -->

\ No newline at end of file

Added:
>
>

META FILEATTACHMENT attachment="VertexNTrks_vs_VertexZerr_profile.pdf" attr="" comment="Primary vertex pdf" date="1401096780" name="VertexNTrks_vs_VertexZerr_profile.pdf" path="VertexNTrks_vs_VertexZerr_profile.pdf" size="15698" user="tompkins" version="1"
META FILEATTACHMENT attachment="VertexNTrks_vs_VertexZerr_profile.png" attr="" comment="Vertex png" date="1401097808" name="VertexNTrks_vs_VertexZerr_profile.png" path="VertexNTrks_vs_VertexZerr_profile.png" size="12671" user="tompkins" version="2"

Revision 22014-05-19 - AlbertoAnnovi

Line: 1 to 1
 
META TOPICPARENT name="TriggerPublicResults"
Deleted:
<
<
 AtlasPublicTopicHeader.png

FTKPublicResults

Line: 21 to 20
 
Changed:
<
<
Placeholder
>
>
Fast TracKer (FTK) updates to TDR for IBL (ATL-COM-DAQ-2014-014)
 

Revision 12014-05-13 - LaurenTompkins

Line: 1 to 1
Added:
>
>
META TOPICPARENT name="TriggerPublicResults"

AtlasPublicTopicHeader.png

FTKPublicResults

<!-- this line is optional -->

Introduction

This page collects public results for the performance of the FTK system. The technical design report can be found here. Figures from the TDR are collected on this page.

2014 Performance Plots

Placeholder


png pdf

Placeholder


png pdf

<!-- ********************************************************* -->
<!-- Do NOT remove the remaining lines, but add requested info as appropriate-->
<!-- ********************************************************* -->


<!-- For significant updates to the topic, consider adding your 'signature' (beneath this editing box) -->
Major updates:
-- LaurenTompkins - 13 May 2014

<!-- Person responsible for the page: 
Either leave as is - the creator's name will be inserted; 
Or replace the complete REVINFO tag (including percentages symbols) with a name in the form TwikiUsersName -->
Responsible: LaurenTompkins
Subject: public
<!-- Once this page has been reviewed, please add the name and the date e.g. StephenHaywood - 31 Oct 2006 -->
 
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