AtlasPublicTopicHeader.png

Approved trigger cosmic-ray, single-beam, system, and timing plots

Introduction

The L1 trigger and HLT commissioning and performance plots below are approved to be shown by ATLAS speakers at conferences and similar events.

Contact the Trigger coordinator or the TDMT in case of questions and/or suggestions.

L1 Trigger

L1 Muon Barrel (RPC)

This plot is only for Trigger Sector 39. It shows the mean value of the distribution of track Theta passing by a given PAD+CM-eta (y-axis), versus the ordinal number that indentifies the PAD and its CM-eta (from PAD=0, CM=0 : bin 0; to PAD=6, CM=3, bin 13). No CM-phi are considered, because at the moment the trigger is configured differently for them; and because two CM-phi in the same PAD are at the same $\theta$ angle wrt the beam axis. The plot clearly provides an example of the different behaviour of the L1_MU6 and L1_MU10 thresholds from the L1_MU0 threshold: the former do grow approx. linearly with the angle Theta of the PAD+CM-eta, in order to have the track always pointing to the I.P., whereas the latter is essentially flat, with a slight structure from the shaft sculpting. Plots obtained on full statistics from run 131227, looking at the CosmicMuons stream. Theta_Mean.jpg Contact: Giuseppe Salamanna

L1 Muon End Caps (TGC)

  • TGC_LVL1 : trigger timing distribution with single-beam is shown. The unit of X-axis is Bunch-Crossing, it means 25nsec.
  • There are three types of trigger issued by TGC, and they are exclusive.
    • TGC_HALO uses hits from 2 doublet stations. To have acceptance for beam halo which runs in parallel to beam line, two layers on pivot planes in eta direction is used, on the other hand , coincidence of 3 out of 4 layers is applied in phi direction.
    • TGC_MU0 , in addition to TGC_HALO, required 2 out of 3 coincidence in the 1st triplet station. (within full open road)
    • TGC_MU6 , in addition to MU0, requiring the position of 2/3 coincidence be inside the narrower road
  • There are two sharp peaks in the plot. The single beam is going from C to A-side during this period. The difference of time can be under stood as Time-of-flight.
  • The spread of the timing peak is about 1BC, it means the timing alignment is perfectly done at this level. ( Rem : delay parameters have been set with assuming particles are coming from IP, so the direction for C-side is opposite to this assumption. It looks this is the reason why the red peak is spread into 2 bins.)
  • After looking this plot, we shifted global timing by -5BC, it means TGC is set as ready for collision
tgc-timing-1beam.jpg Contact: Masaya Ishino

L1 Central Trigger (CTP)

Timing distribution of Level 1 triggers from September 10, the first day of single-beam data. Events were triggered with the BPTX, providing a stable time reference (at BC 0) with respect to the LHC. One should note both the large overlap between triggers (since the beam quality was poor, we observed a large number of calorimeter and muon triggers) and the broad timing distribution of the different trigger sources. Additionally, one can see the 'two-peak' structure in the TGC from the two endcaps, explained in detail in another plot above. 10sep.gif Contact: Daniel Sherman
Timing distribution of Level 1 triggers from September 12, the third day of single-beam data. Events were triggered here with the MBTS at BC 0. Of note in this plot is the excellent timing of the BPTX and MBTS, and also the relatively small coincidence of the minimum bias trigger with calorimeter and muon triggers. The latter point implies that the beam quality had improved significantly in the first 48 hours of beam time. The timing of the RPC had not been tuned at all prior to this run. 12sep.gif Contact: Daniel Sherman
Level-1 trigger rates. Data were collected during RUN 87863, triggering on BPTX from beam 2. The plot shows the trigger rate for the BPTX, MBTS single counter, LCID. The rate is averaged over 10 seconds, and it peaks every 40 seconds, the beam injection interval at that time. l1rates.gif Contact: Andrea Messina
CTP Bunch-Crossing (BC) distribution of the RPC low-pt trigger, from any trigger sector, with respect to the TRT trigger before (run 125636) and after (run 137651) a single time alignment calibration iteration. The residual spread is mainly due to the fact that a coarse (minimum 1 BC level) correction was applied when putting the RPC in time witj the TRT (actually: delay set to +1 BC on purpose) comp.new.jpg Contact: Michela Biglietti, Giuseppe Salamanna
CTP Bunch-Crossing (BC) distribution of the RPC low-pt trigger, with respect to the TRT trigger after (run 137651) a single time alignment calibration iteration, in units of BC, in an RPC Sector vs Tower map. This is equivalent to the previous plot, but is obtained on a subsample of events where only 1 CTP RPC entry and 1 RPC trigger sector+tower were recorded, in order to be able to associate CTP and space information. run137651.jpg Contact: Michela Biglietti, Giuseppe Salamanna
CTP Bunch-Crossing (BC) distribution of the RPC low-pt trigger, with respect to the RPC trigger sector 39 taken as reference, after (run 131537) a single time alignment calibration iteration, in units of BC, in an RPC Sector vs Tower map. This is equivalent to the previous plot, but is obtained using only RPC information on a run where RPC gave L1 Accept. wrtRPC.jpg Contact: Michela Biglietti, Giuseppe Salamanna
Eta of the position of the Trigger CM hit (x-axis) vs the Eta of the position of the closest MuCTPi ROI recorded. The closest MuCTPi ROI is the ROI closest in Eta and Phi to the CM hit considered. Both CM-eta and CM-phi are plotted here. When the hit is not matched with a track, a few CM hits display in the plot that are uncorrelated with an actual ROI in that event, being therefore not real triggers (no coincidence satisfied). These disappear when asking for a track match. TrackMatchEffect_Eta_off.gif Contact: Giuseppe Salamanna

L1 Minimum Bias (MBTS)

Timing distribution for 6 of the 32 MBTS panels. Data were collected in run 87863, triggering on BPTX from a single beam. The horizontal axis is the same as the TGC plot above, showing the number of bunch crossings delayed with respect to the trigger. With a small amount of single beam data, the timing distribution for each scintillator panel was adjusted to align the MBTS with the BPTX, thereby setting up proper timing for collision data, mbts-87863-mod.gif Contact: Daniel Sherman
Comparison of scope traces of analogue MBTS signals out of the TileCal electronics, for a vertical cosmic muon (top) and the collimator splashes (bottom). A roughly vertical cosmic muon yields a signal of about 700 mV amplitude, whereas the collimator splashes resulted in many many charged particles crossing the scintillators saturating the TileCal readout electronics (at -2 V).

Note: MBTS stands for Minimum Bias Trigger Scintillators. They are 2x16 scintillator paddles, installed on both sides of the interaction point. See the ATLAS week talks for more details.

ScopeTraceMbts.jpg Contact: David Berge

L1 Beam Pickups (BPTX)

Oscilloscope traces of discriminated beam pick-up (BPTX) signal (C1, yellow) and minimum bias trigger scintillator (MBTS) analogue signals (C2, C3, C4) during an injection of 1 bunch (beam 2) without RF capture. The bunch manages to circulate a few times. After 7 turns its intensity falls below the threshold of the BPTX discriminator. The first few turns gives only small activity in the MBTS. After 3 or 4 turns all MBTS show saturated signals for 5 to 6 turns. bptx_and_mbts_7turns.jpg Contact: Thilo Pauly
Bunch intensity measured by the beam pick-up monitoring system during a coast of more than 20 minutes of beam 2 on Friday 12 Sep 2008 1:11 am. The relative precision determined from the scatter of data points is 10 percent. The absolute intensity value is not calibrated yet and corresponds roughly to unit of 1e10 protons. BPTX_bunchintensity.png Contact: Thilo Pauly
Oscilloscope traces with persistency set to infinity of: beam pickup (BPTX) signal (C3 blue) of beam 2, discriminated BPTX signal (C4, green), bunch clock of beam 2 (C1 yellow), reference bunch clock (C2 red). The traces were taken during 20 minutes of beam 2 on Friday 12 Sep 2008 1:11 am.

The phase between BPTX signal and bunch clock 2 stayed constant within +/- 100 ps (40 ps RMS).

The reference clock, which was used by ATLAS at the time, was not in sync with the beam.

bptx_long_coast.jpg Contact: Thilo Pauly

L1 Calorimeter Trigger (L1Calo)

L1Calo calorimeter energy correlation plot. This shows the energy measured in trigger towers (usually 0.1x0.1 in eta/phi) by the Level-1 calorimeter trigger (x-axis) compared to the energy measured in the full readout for the calorimeters (y-axis) - in this case the Liquid Argon electromagnetic layers. A good correlation is seen, and this is done with nominal calibrations. When full energy calibration is applied, the spread will decrease. A sharp cut-off is seen in the trigger tower energy at the trigger threshold of 5 GeV used for much of the 2008 cosmic running. l1calo_correlation.JPG
[ps] [tiff]
Contact: Steve Hillier
L1Calo cosmic spectrum. Here we see the energy spectrum of trigger tower energies as seen in the Level-1 Calorimeter trigger towers for a typical cosmic run. Though the majority of cosmic muons only deposit a small ammount of energy in the calorimeters, there is a large tail of higher energies, mainly due to showering and large showers, rather than individual muons. These are very useful for debugging the trigger. The peak at the top end of the spectrum is an artefact of saturation in the digital logic for the setting used at the time - all energies above about 125 GeV are recorded (and triggered) as saturated towers. l1calo_spectrum.JPG
[ps] [tiff]
Contact: Steve Hillier
L1Calo cosmic event. A typical cosmic event triggered by the Level-1 calorimeter trigger. The trigger thresholds typically involved for such an event with significant deposits in the Tile Calorimeter are 1HA5 and 1J5 - ie one 'tau-like' cluster above 5 GeV or one 'jet-like' cluster above 5 GeV. l1calo_cosmic.JPG
[ps] [tiff]
Contact: Steve Hillier
L1Calo splash event. One of the famous collimator splash events, as seen in the Level-1 Calorimeter trigger. This is shown as a 2-D eta/phi plot, with eta along the x-axis, and phi up the y-axis, and the colours are proportional to the transverse energy deposited in each trigger tower. The well-known eight-fold phi structure can be seen, but many other features are also possible. The difference in absolute scale between the A and C side is attributed to the fact that timing of the C-side was actually one bunch-crossing away from ideal, and this was corrected as a result of these observations. l1calo_splash.JPG Contact: Steve Hillier
The Figure shows a quasi-online produced L1Calo tower timing distribution from a first night's splash event (triggered by MBTS); the beam is coming from the right. The Figure shows the eta-phi timing distribution of all EM towers; in z the timing offset in nanoseconds with respect to the timing of the L1_EM14 trigger towers located at -0.4 < eta < (inner ring) is plotted. The observed time differences seen in this plot are mainly due time-of-flight, as in this figure no ToF correction is done yet. These data will be used to derive a first set of L1Calo timing corrections. [Remark: red strip is due to the overlap region not being commissioned yet ...] [pdf] [png]
Contact: Steve Hillier
This Figure shows as above the eta-phi L1Calo tower timing distribution from a first night's splash event, now corrected for ToF using a simplified geometry (see also above); reference is again he L1_EM14 trigger towers located at -0.4 < eta < (inner ring). The derived timing offsets/delays will serve as input for first L1Calo timing corrections constants. The plot shows that the accuracy of the relative L1Calo EM timing at startup (i.e already for the first splash events) was for most towers correct at the few ns level. [Remark: red strip is due to the overlap region not being commissioned yet ...] [pdf] [png]
Contact: Steve Hillier
Reconstructed trigger tower signal using PHOS4 scan. Using fixed-energy calorimeter calibration pulses and varying the nanosecond PHOS4 delay in the PPM, an analogue signal shape can be reconstructed. This is a Liquid Argon pulse. The signal is fit using a Gaussian(rising-edge)/Landau(falling-edge) hybrid fit function. See CDS Record for more details. l1calo_reconstructedSignalWithFit.png
[png]
Contact: Taylor Childers
Digitized trigger tower output from PreProcessor Module (PPM) . Using fixed-energy calorimeter calibration pulses an analogue signal is digitized at the LHC bunch crossing frequency of 40MHz, which yields a sample every 25ns. This is a Liquid Argon pulse. The signal is fit using a Gaussian(rising-edge)/Landau(falling-edge) hybrid fit function and can be used to extract more detailed information about the pulse shape on the nanosecond level. See CDS Record for more details. l1calo_digitizedSignalWithFit.png
[png]
Contact: Taylor Childers
Eta/Phi map of the electromagnetic calorimeter for a single splash event (event number 2166, run number 140370) from November 2009. The signal peak time (in nanoseconds) is shown on the z-axis as determined from fitting digitized pulses with Gaussian/Landau fit function. Beam-1 was the source of this event, which moves in the -Eta direction. See CDS Record for more details. h_emDelaySumNs_splash.png
[png]
Contact: Taylor Childers
Eta projection of the Eta/Phi map of the electromagnetic calorimeter for a single splash event (event number 2166, run number 140370) from November 2009. The signal peak time (in nanoseconds) is shown on the z-axis as determined from fitting digitized pulses with Gaussian/Landau fit function. Beam-1 was the source of this event, which moves in the -Eta direction. See CDS Record for more details. h_emDelaySumNs_splash_px.png
[png]
Contact: Taylor Childers
Eta/Phi map of the hadronic calorimeter for a single splash event (event number 2666, run number 140370) from November 2009. The signal peak time (in nanoseconds) is shown on the z-axis as determined from fitting digitized pulses with Gaussian/Landau fit function. Beam-2 was the source of this event, which moves in the +Eta direction. See CDS Record for more details. h_hadDelaySumNs_splash.png
[png]
Contact: Taylor Childers
Eta projection of the Eta/Phi map of the hadronic calorimeter for a single splash event (event number 2666, run number 140370) from November 2009. The signal peak time (in nanoseconds) is shown on the z-axis as determined from fitting digitized pulses with Gaussian/Landau fit function. Beam-2 was the source of this event, which moves in the +Eta direction. See CDS Record for more details. h_hadDelaySumNs_splash_px.png
[png]
Contact: Taylor Childers
Time of flight from collision vertex to the mid-point (between outer and inner layer) of the electromagnetic calorimeter layer. Symmetric in Phi. See CDS Record for more details. emTof_physics.png
[png]
Contact: Taylor Childers
Time of flight from collision vertex to the mid-point (between outer and inner edge) of the hadronic calorimeter layer. Symmetric in Phi. See CDS Record for more details. hadTof_physics.png
[png]
Contact: Taylor Childers
Time of flight from beam collimator to the mid-point (between outer and inner edge) of the electromagnetic calorimeter layer. Symmetric in Phi. See CDS Record for more details. emTof_splash.png
[png]
Contact: Taylor Childers
Time of flight from beam collimator to the mid-point (between outer and inner edge) of the hadronic calorimeter layer. Symmetric in Phi. See CDS Record for more details. hadTof_splash.png
[png]
Contact: Taylor Childers
Time of flight from collision vertex to mid-point (between outer and inner edge) of the electromagnetic calorimeter minus the time of flight from the collimator to the same mid-point. This time of flight correction was applied to the splash events in order to dereive the l1calo analogue signal timing delays expected for physics collisions. Symmetric in Phi. See CDS Record for more details. emTof_physics_splash.png
[png]
Contact: Taylor Childers
Time of flight from collision vertex to mid-point (between outer and inner edge) of the hadronic calorimeter minus the time of flight from the collimator to the same mid-point. This time of flight correction was applied to the splash events in order to dereive the l1calo analogue signal timing delays expected for physics collisions. Symmetric in Phi. See CDS Record for more details. hadTof_physics_splash.png
[png]
Contact: Taylor Childers
Eta/Phi map of the electromagnetic calorimeter for a single splash event (event number 2166, run number 140370) from November 2009. The signal peak time (in nanoseconds) is shown on the z-axis as determined from fitting digitized pulses with Gaussian/Landau fit function. The peak times have been corrected for time of flight in order to present the timing as expected for beam collisions. Beam-1 was the source of this event, which moves in the -Eta direction. See CDS Record for more details. h_emDelaySumNs_new.png
[png]
Contact: Taylor Childers
Eta projection of the Eta/Phi map of the electromagnetic calorimeter for a single splash event (event number 2166, run number 140370) from November 2009. The signal peak time (in nanoseconds) is shown on the z-axis as determined from fitting digitized pulses with Gaussian/Landau fit function. The peak times have been corrected for time of flight in order to present the timing as expected for beam collisions. Beam-1 was the source of this event, which moves in the -Eta direction. See CDS Record for more details. h_emDelaySumNs_new_px.png
[png]
Contact: Taylor Childers
Eta/Phi map of the hadronic calorimeter for a single splash event (event number 2666, run number 140370) from November 2009. The signal peak time (in nanoseconds) is shown on the z-axis as determined from fitting digitized pulses with Gaussian/Landau fit function. The peak times have been corrected for time of flight in order to present the timing as expected for beam collisions. Beam-1 was the source of this event, which moves in the -Eta direction. See CDS Record for more details. h_hadDelaySumNs_new.png
[png]
Contact: Taylor Childers
Eta projection of the Eta/Phi map of the hadronic calorimeter for a single splash event (event number 2666, run number 140370) from November 2009. The signal peak time (in nanoseconds) is shown on the z-axis as determined from fitting digitized pulses with Gaussian/Landau fit function. The peak times have been corrected for time of flight in order to present the timing as expected for beam collisions. Beam-1 was the source of this event, which moves in the -Eta direction. See CDS Record for more details. h_hadDelaySumNs_new_px.png
[png]
Contact: Taylor Childers
Peak time (from L1Calo channel 0x041f0700) as extracted using the Gaussian/Landau fit function for each splash event from November 2009 (Run 140370). Used to show that a minority of channels show different peak times depending on the beam used for the splash, however, the variation is still within the tolerance of +/-5ns. See CDS Record for more details. peakpos_0x041f0700.png
[png]
Contact: Taylor Childers
Peak time (from L1Calo channel 0x00100302) as extracted using the Gaussian/Landau fit function for each splash event from November 2009 (Run 140370). Used to show that a majority of channels show the same peak times independent of which beam is used for the splash. See CDS Record for more details. peakpos_0x00100302.png
[png]
Contact: Taylor Childers
Eta/Phi map of the electromagnetic calorimeter using all splash events (run number 140370) from November 2009. The mean signal peak time (in nanoseconds) is shown on the z-axis as determined from fitting the digitized pulses from each splash event with a Gaussian/Landau fit function. The peak times have been corrected for time of flight in order to present the timing as expected for beam collisions. See CDS Record for more details. h_emSummary_timing.png
[png]
Contact: Taylor Childers
Eta/Phi map of the hadronic calorimeter using all splash events (run number 140370) from November 2009. The mean signal peak time (in nanoseconds) is shown on the z-axis as determined from fitting the digitized pulses from each splash event with a Gaussian/Landau fit function. The peak times have been corrected for time of flight in order to present the timing as expected for beam collisions. See CDS Record for more details. h_hadSummary_timing.png
[png]
Contact: Taylor Childers
Eta/Phi map of the electromagnetic calorimeter using all splash events (run number 140370) from November 2009. The mean timing offset used by the l1calo PreProcessor hardware (in nanoseconds) is shown on the z-axis as determined from fitting the digitized pulses from each splash event with a Gaussian/Landau fit function. The delays have been corrected for splash time of flight in order to present the timing as expected for beam collisions. See CDS Record for more details. h_emFullDelay.png
[png]
Contact: Taylor Childers
Eta/Phi map of the hadronic calorimeter using all splash events (run number 140370) from November 2009. The mean timing offset used by the l1calo PreProcessor hardware (in nanoseconds) is shown on the z-axis as determined from fitting the digitized pulses from each splash event with a Gaussian/Landau fit function. The delays have been corrected for splash time of flight in order to present the timing as expected for beam collisions. See CDS Record for more details. h_hadFullDelay.png
[png]
Contact: Taylor Childers

Egamma Slice

The figure shows the shower shape R_eta used for electron and photon selections calculated at Level-2 and Event Filter. It is calculated by the ratio of the energy deposit in 3x7 cells (corresponding to 0.075 x 0.175 in Delta eta x Delta phi) over 7 x 7 cells in the second EM sampling. Only clusters are shown if the cluster could be matched to an offline cluster with ET>5 GeV. Note, the value of R_eta can have values above one due to the electronic shaping function used in LAr. They are set-up in such a way that noise contributions will fluctuate around zero instead of producing on offset, thus cell energies can obtain negative values. This might result that the total energy deposit in Delta eta x Delta phi = 3 x 7x cells is bigger than the one in 7 x 7 cells in case of small signals. The plot was done using run 90272. It shows nicely the form of the R_eta variable obtained in cosmic data taking and conveys the message the HLT e/gamma trigger is technically functioning. This figure was produced using the ESDs from reprocessing 602. The trigger content is the one from the actual online running. The same figure in eps format: run90272_rcore1d.eps run90272_rcore1d.gif Contact: Monika Wielers
The figure shows the shower shape R_eta used for electron and photon selections calculated at Level-2 and Event Filter in a scatter plot. The colour code give the number of clusters found in each bin. Only clusters are shown if the cluster could be matched to an offline cluster with ET>5 GeV. The same information as in the previous figure is displayed. In a conference the previous figure should be shown in preference to this one, however, this figure may be useful in case of questions but will require careful explanation. This figure was produced using the ESDs from reprocessing 602. The trigger content is the one from the actual online running. The same figure in eps format: run90272_rcoreoefl2.eps run90272_rcoreoefl2.gif Contact: Monika Wielers
Another shower shape used for electron/jet separation is the search for substructures within one cluster in the first EM sampling which has a very fine-grained granularity in eta. The shower is studied in a window Delta eta x Delta phi = 0.125 x 0.2 and the first E1(max) and second highest maximum E2(max) are searched for. The figure shows the distribution energy in the strip with maximal energy at Level-2 and Event Filter. The clusters come from run 90272 and only clusters are shown if the cluster could be matched to an offline cluster with ET>5 GeV. This plot conveys the message the HLT e/gamma trigger is technically functioning. This figure was produced using the ESDs from reprocessing 602. The trigger content is the one from the actual online running. The same figure in eps format: run90272_emax1d.eps run90272_emax1d.gif Contact: Monika Wielers

Muon Slice

Distribution of the α angle in the barrel ( α = angle between the MDT Middle fit slope in the r-z plane and the direction pointing to the interaction vertex) obtained by LVL2 μFast, shown for all the fit segments performed in the Middle station (black line) and for those Middle fit segments confirmed to be a muon track by the presence of another fit segment either in the outermost station or in the innermost station (red line). The plot comes from run 92226, taken with solenoid field on and toroid field off (straight tracks in the Muon Spectrometer). The purpose of this comparison is to show the performance of the μFast pattern recognition, even if the algorithm is thought to work on muons pointing to the interaction point while the events considered here (cosmic rays) don't have this feature.

The same figure in eps format: run_92226_Mufast_barrel_Alpha_2seg.eps

run_92226_Mufast_barrel_Alpha_2seg.gif Contact: Alessandro Di Mattia
Barrel track Sagitta reconstructed by LVL2 μFast employing tracks that have at least two MDT fit segments. In the case the track has only two fit segments the Sagitta is reconstructed with the assumption that the track points to the nominal Interaction Vertex (i.e. the origin of the ATLAS coordinate system). The plot comes from run 92226, taken with solenoid field on and toroid field off (straight tracks in the Muon Spectrometer). The Sagitta peaks at zero and the flat structure under the peak is due to tracks having only two MDT fit segments, being these tracks non pointing to the nominal Interaction Vertex.

The same figure in eps format: run_92226_Mufast_barrel_Sagitta_2seg.eps

run_92226_Mufast_barrel_Sagitta_2seg.gif Contact: Alessandro Di Mattia
Distribution of z0 (z0 = distance in the r-z plane between the intersection of the track direction with the beam line and the origin of the ATLAS coordinate system) computed by LVL2 μFast employing tracks that have at least two MDT fit segments. The plot comes from run 92226, taken with solenoid field on and toroid field off (straight tracks in the Muon Spectrometer). The z0 peaks at zero and the poor resolution point out that most of the tracks does not point to the nominal Interaction Vertex (i.e. the origin of the ATLAS coordinate system).

The same figure in eps format: run_92226_Mufast_barrel_IP_2seg.eps

run_92226_Mufast_barrel_IP_2seg.gif Contact: Alessandro Di Mattia
Distribution of the α angle in the barrel ( α = angle between the MDT Middle fit slope in the r-z plane and the direction pointing to the interaction vertex) obtained by LVL2 μFast, shown for all the fit segments performed in the Middle station (black line) and for those Middle fit segments confirmed to be a muon track by the presence of two other fit segments in both the outermost station and the innermost station (red line). The plot comes from run 92226, taken with solenoid field on and toroid field off (straight tracks in the Muon Spectrometer). Owing to the more stringent constraints to point to the interaction vertex imposed to μFast, the number of selected cosmics events is drastically reduced, but the performance of the algorithm is strongly improved in terms of sagitta and transverse momentum reconstruction.

The same figure in eps format: run_92226_Mufast_barrel_Alpha_3seg.eps

run_92226_Mufast_barrel_Alpha_3seg.gif Contact: Alessandro Di Mattia
Barrel track Sagitta reconstructed by LVL2 μFast employing tracks that have three MDT fit segments. The plot comes from run 92226, taken with solenoid field on and toroid field off (straight tracks in the Muon Spectrometer). The Sagitta peaks at zero. The resolution of the peak sets the intrinsic limit of the muon momentum resolution achieved by μFast. In the present study the alignment corrections of the precision chambers are not taken into account and the resolution of Sagitta of straight tracks .

The same figure in eps format: run_92226_Mufast_barrel_Sagitta_3seg.eps

run_92226_Mufast_barrel_Sagitta_3seg.gif Contact: Alessandro Di Mattia
Distribution of z0 (z0 = distance in the r-z plane between the intersection of the track direction with the beam line and the origin of the ATLAS coordinate system) computed by LVL2 μFast employing tracks that three MDT fit segments. The plot comes from run 92226, taken with solenoid field on and toroid field off (straight tracks in the Muon Spectrometer). The z0 is gaussian distributed around zero and the resolution of 60 cm correspond to the tolerance of the Vertex pointing allowed by the finite size of the Muon RoI. This plot shows that the tracks fully reconstructed by the μFast pattern recognition point to the nominal Intercation Vertex (i.e. the origin of the ATLAS coordinate system).

The same figure in eps format: run_92226_Mufast_barrel_IP_3seg.eps

run_92226_Mufast_barrel_IP_3seg.gif Contact: Alessandro Di Mattia
Performance for MDT cluster finding of L2 muFast: x-axis shows the distance of the precision chamber clusters (MDT segment hits) from the trigger data (TGC hits) and the y-axis shows the number of TGC hits found in the RoI. It is expected to have less than 20 TGC hits in the Muon RoI, but still an higher number is found because of the chamber noise and because of the incident angle of the cosmic muons, which may fire more than 1 readout strip/wires. The position of the MDT cluster (w.r.t. the trigger) is not well defined for event with a number of TGC hits greater than 20, but the pattern recognition is able to fit them with no big loss of efficiency. Fit inefficiencies are also happening because of the limited size of the Muon Road (red dots near the boundaries) or because of the unphysical conversion of MDT time into space that forces to reject some of the selected MDT hits entering the fit. The total efficiency for selecting MDT cluster in the Middle endcap station is 93% and the clusters yielding bad fit is ~10% of the fitted clusters.

The same figure in eps format: run_90272_Mufast_endcap_middle_TGC-MDT_corr.eps

run_90272_Mufast_endcap_middle_TGC-MDT_corr.gif Contact: Alessandro Di Mattia
Distribution of the drift space conversion of MDT hit entering into the fit. The peak outside the boundary of the MDT tube (1.5 cm) and the little spot at zero are due to unphysical MDT time to space conversions and spoil the fit efficiency by about 2\% of the reconstructed LVL1 RoIs. The origin of the unphysical conversion of the MDT drift time is the bad definition of the t0 (for some of the MDT tubes) because of to the limited resolution on the event time, that for cosmic it is given by the muon trigger chamber and not by the beam clock.

The same figure in eps format: run_90272_Mufast_endcap_middle_MDT_drift_space.eps

run_90272_Mufast_endcap_middle_MDT_drift_space.gif Contact: Alessandro Di Mattia
Distribution of the MDT endcap cluster fit inefficiencies in the x-y ATLAS coordinates. The inefficiencies correspond to 4.7% of the total reconstructed LVL1 RoIs. The big hot spot is due to a missing MDT chamber int he readout (EMS514) and the little hot spot is due t a noisy MDT chamber.

The same figure in eps format: run_90272_Mufast_endcap_middle_missing_MDT.eps

run_90272_Mufast_endcap_middle_missing_MDT.gif Contact: Alessandro Di Mattia
Distribution of the difference of the two α angle measurements (α = angle between the fit slope in the r-z plane and the direction pointing to the interaction vertex) one performed with MDT hits one performed with TGC hits. The dotted line is made using (for the MDT α measurement) only the MDT hits of the cluster in the Middle station, while the solid one is made using both the hits of Middle and Outer Station. The performance of the match is much better in the second case, because the big lever arm between Middle and Outer Station removes the inaccuracy due to the bad MDT calibration. The drop between the dotted line and the solid line is due to the orientation of the cosmic muon tracks that typically point into a region not covered by the Outer Station of the Muon Spectrometer. The purpose of this plot is to show that the performance of the match are similar to those obtained from the Monte Carlo studies.

The same figure in eps format: run_90272_Mufast_endcap_Alpha_TGC-MDT_match.eps

run_90272_Mufast_endcap_Alpha_TGC-MDT_match.gif Contact: Alessandro Di Mattia
Here the isolation variable based on the Inner Detector (ID) is shown, obtained with the muon Level 2 muIso algorithm. The variable is defined as: Iso = pT(μ)/ΣpT(ΔR<0.2), where pT(μ) is the transverse momentum of the track measured in the ID matched with the muon and ΣpT(ΔR<0.2) is the sum of the transverse momenta of all ID tracks contained in a cone centered around the muon track with half-width ΔR=0.2. This plot is made with muons from run 91860. In this run both the solenoid and toroids magnetic fields where on. Since cosmic muons have to produce isolated tracks, the most probable value for Iso is 1. Few events gather around Iso~0.5, this happens when the ID tracking algorithm reconstruct two tracks out of one with very similar parameters.

The same figure in eps format: IsoTrk_cosmics.ps

IsoTrk_cosmics.gif Contact: Camilla Maiani
Energy deposition of muons in the Tile Calorimeter, as obtained from the LVL2 muTile algorithm, for the run 91060 (no magnetic field) with the request of energy threshold in Tile Calorimeter cells of 300 MeV. The typically expected value of about 2.5 GeV for the deposited energy can be observed, compatibly with studies performed on simulated cosmics data.

The same figure in eps format: muTile1.eps

muTile1.gif Contact: Aranzazu Ruiz Martinez
Azimuthal angle phi distribution in the Tile Calorimeter obtained with the LVL2 muTile algorithm, for the run 91060 (no magnetic field). The distribution shows the typical up-down shape, as to be expected for cosmic muons passing through the calorimeter.

The same figure in eps format: muTile2.eps

muTile2.gif Contact: Aranzazu Ruiz Martinez
The plot shows the cosmic muons identified at Level-2 trigger by TileMuId in combination with TrigIDSCAN (plot extracted from the HLT monitoring histograms in run 91900 where the solenoid and toroid magnetic fields were switched on).

The plot shows the difference between the muon ϕ coordinate provided by TileMuId (ϕTile) and the ϕ coordinate of the associated track found in the Inner Detector (ϕID) as a function of the muon pT measured in the Inner Detector.

Two branches are observed corresponding to muons with different charge. Difference between Tile and ID is larger in the low-pT region as expected.

The same figure in eps format: run91900_absPtTrkPre_vs_DelPhiTrk.eps

run91900_absPtTrkPre_vs_DelPhiTrk.gif Contact: Aranzazu Ruiz Martinez
The plot shows the cosmic muons identified at Level-2 trigger by TileMuId in combination with TrigIDSCAN (plot extracted from the HLT monitoring histograms in run 91900 where the solenoid and toroid magnetic fields were switched on).

Difference between the muon ϕ coordinate provided by TileMuId (ϕTile) and the ϕ coordinate of the associated track found in the Inner Detector after having been extrapolated to the TileCal Radius (ϕTR) using the following parametrization:
ϕTR±) = ϕID±) -/+ 0.000123 -/+ 0.507/pT±)
as a function of the muon pT measured in the Inner Detector.

The dispersion of ~0.1 rad, which is the TileCal granularity, confirms that the extrapolated ID track points to the TileCal module where the muon was found.

The same figure in eps format: run91900_absPtTrkPre_vs_DelPhiTrkTR.eps

run91900_absPtTrkPre_vs_DelPhiTrkTR.gif Contact: Aranzazu Ruiz Martinez
Difference in pseudorapidity (eta) between muon tracks obtained in the Muon Spectrometer with the TrigMuonEF package used in the Event Filter, and the corresponding muon tracks obtained by Moore algorithm in the offline reconstruction. Run 90272 was considered, with magnetic field on. The resolution is then obtained from the fit to a Gauss function and is observed to be about 0.007. Tails are due to slightly different configurations in online and offline. The same figure in eps format: muonEF1.eps muonEF1.gif Contact: Michela Biglietti
Difference in azimuthal angle (phi) between muon tracks obtained in the Muon Spectrometer with the TrigMuonEF package used in the Event Filter, and the corresponding muon tracks obtained by Moore algorithm in the offline reconstruction. Run 90272 was considered, with magnetic field on. The resolution is then obtained from the fit to a Gauss function and is observed to be about 17 mrad. Tails are due to slightly different configurations in online and offline. The same figure in eps format: muonEF2.eps muonEF2.gif Contact: Michela Biglietti

HLT Tracking

The following three figures (starting with this one) show L2 event reconstruction efficiency for 2008 cosmic data, separately for the three Inner Detector tracking algorithms that were running at L2. L2 efficiency is defined with respect to an event with an offline track and was measured for the RPC L1 stream since cosmic algorithms at L2 were only used to trigger events from this stream. The offline track is required to have at least three silicon space points (SP, number of pixel hits plus the number of SCT hits divided by two) in the upper and three in the lower part of the silicon barrel. Either of the two track arms can be independently reconstructed at L2 by silicon algorithms. If there is more than one such track in an event, the track with most pixel hits is used as a reference (most SCT hits if there are no pixel hits). We require |d0| < 200 mm for plots other than d0 dependency.
The track is also required to be within Transition Radiation Tracker (TRT) read-out time window. This is required due to large RPC trigger jitter. TRT detector is reading out three bunch crossings (BC). TRT is operating on a principle of a drift chamber, where time of arrival of the signal varies over the range of about 50ns, depending on the track to wire distance within the TRT detector element (straw). Therefore, optimal time window for TRT detector is even considerably smaller than 75ns (three BC). Outside the optimal range, hits have either poor tracking accuracy or are lost completely. This has clear impact on the track reconstruction efficiency as can be seen in the figure. For plots other than this one we therefore require -10ns < TRT EP < 25ns.
L2 reconstruction efficiency as a function of TRT EP. Different symbols indicate different L2 algorithms as shown in the legend. TRT L2 efficiency falls off sharply at the edge of TRT read-out time window. Events with invalid EP (mostly events that have no TRT hits on track) are not shown in this plot. With |d0| < 200mm requirement.
The same figure in eps format: L2eff.CombinedInDetTracks_CTB.ep.goldenSi_200.eps
L2eff.CombinedInDetTracks_CTB.ep.goldenSi_200.png Contact: Sasa Fratina
L2 reconstruction efficiency as a function of track impact parameter d0. Different symbols indicate different L2 algorithms as shown in the legend. With -10ns < TRT EP < 25ns requirement.
The same figure in eps format: L2eff.CombinedInDetTracks_CTB.d0.goldenSi_3.eps
L2eff.CombinedInDetTracks_CTB.d0.goldenSi_3.png Contact: Sasa Fratina
L2 reconstruction efficiency as a function of track transverse momenta pT. pT for cosmic tracks is defined in the same way as for collisions: pT = | sin(theta) * p |, where theta is the angle between the track trajectory and the beam axis. Different symbols indicate different L2 algorithms as shown in the legend. Track selection -10ns < TRT EP < 25ns and |d0| < 200mm is used. The low efficiency for IDScan at the lowest-PT bins is expected (and intentional): The spacepoint shifter used before the pattern recognition works for more-or-less straight tracks in the inner detector.
The same figure in eps format: L2eff.CombinedInDetTracks_CTB.pt.goldenSi_203.eps
L2eff.CombinedInDetTracks_CTB.pt.goldenSi_203.png Contact: Sasa Fratina
An example of the Tier-0 Monitoring for IDScan. The histogram is the IDScan phi_0 distribution for tracks from the IDCosmic stream where phi_0 is the track tangent angle at the track perigee, the point of closest approach to the origin. This clearly shows the top-to-bottom nature of the events with the two trigger tracks reconstructed approximately at +pi/2 and -pi/2.

Figure as better quality eps file

pres.gif Contact: Mark Sutton
The distribution of the IDScan track impact parameter with respect to the beamline position for events from the IDCosmic stream from the Tier-0 monitoring, clearly showing the acceptance of the SCT and Pixel detectors used for the pattern recognition.

Figure as better quality eps file

idscan-a0.gif Contact: Mark Sutton
The distribution of IDScan track z0 for events from the IDCosmic stream from the Tier-0 monitoring, clearly showing the acceptance of the SCT and Pixel detectors used for the pattern recognition.

Figure as better quality eps file

idscan-z0.gif Contact: Mark Sutton
The distribution of SiTrack track z0 for events from the IDCosmic stream from the Tier-0 monitoring, clearly showing the acceptance of the SCT and Pixel detectors used for the pattern recognition, and a large spike due to the presence of fake tracks due to a noisy module which illustrates the role of the monitoring in correcting routine problems of this nature which might otherwise affect data quality.

Figure as better quality eps file

sitrack-z0.gif Contact: Mark Sutton
a cosmic event showing the two L2 tracks which can be seen clearly from the close up of the pixel detector in the top right. This event was taken from run 901272.

Figure as better quality pdf file

event90127_307141.gif Contact: Mark Sutton
The following three plots show the per track efficiency to reconstruct Event Filter tracks with respect to offline tracks for run 91862 (solenoid on). Loose, medium and tight cuts are applied to the offline tracks.

Loose: >=8 barrel silicon hits OR >=30 barrel TRT hits, pT > 1 GeV, d0 < 500 mm, -10ns < TRT Event Phase < 40ns.

Medium: >=10 barrel silicon hits, >=20 barrel TRT hits, pT > 1 GeV, d0 < 250mm, -5ns < TRT Event Phase < 30ns.

Tight: >=4 barrel pixel hits, >=12 barrel SCT hits, >=50 barrel TRT hits, pT > 1 GeV, d0 < 40mm, -5ns < TRT Event Phase < 30ns.

Silicon hits is defined as 2*NPixelHits + NSCTHits. Events are from the IDCosmic stream, which is triggered by the muon chamber at L1, and found to have an inner detector track at L2. The dashed line shows the overall efficiency. This is 83.0% for loose tracks, based on around 18k tracks.

Figure as better quality eps file

EffLoose91862.jpg Contact: Jenna Lane
For medium tracks, the overall efficiency is 99.7% based on around 6k tracks.

Figure as better quality eps file

EffMed91862.jpg Contact: Jenna Lane
For tight tracks, the overall efficiency is 100% based on around 450 tracks.

Figure as better quality eps file

EffTight91862.jpg Contact: Jenna Lane
The following four plots show the per track efficiency to reconstruct Event Filter tracks with respect to offline tracks for run 92048 (solenoid off). Loose, medium and tight cuts are applied to the offline tracks.

Loose: >=8 barrel silicon hits OR >=30 barrel TRT hits, pT > 1 GeV, d0 < 500 mm, -10ns < TRT Event Phase < 40ns.

Medium: >=10 barrel silicon hits, >=20 barrel TRT hits, pT > 1 GeV, d0 < 250mm, -5ns < TRT Event Phase < 30ns.

Tight: >=4 barrel pixel hits, >=12 barrel SCT hits, >=50 barrel TRT hits, pT > 1 GeV, d0 < 40mm, -5ns < TRT Event Phase < 30ns.

Silicon hits is defined as 2*NPixelHits + NSCTHits. Events are from the IDCosmic stream, which is triggered by the muon chamber at L1, and found to have an inner detector track at L2. The dashed line shows the overall efficiency. This is 81.6% for loose tracks, based on around 18k tracks.

Figure as better quality eps file

EffLoose92048.jpg Contact: Jenna Lane
For medium tracks, the overall efficiency is 99.8% based on around 6k tracks.

Figure as better quality eps file

EffMed92048.jpg Contact: Jenna Lane
For tight tracks, the overall efficiency is 100% based on around 450 tracks.

Figure as better quality eps file

EffTight92048.jpg Contact: Jenna Lane
The loose offline track requirement allows TRT only tracks. At the time of the data reprocessing, the Event Filter was not running any TRT-only tracking. Here, the hit requirement on the offline tracks is modified to be >=8 Si hits to remove the TRT only tracks. For loose Si tracks, the overall efficiency is 98.0% based on around 10k tracks.

Figure as better quality eps file

EffLooseSil92048.jpg Contact: Jenna Lane
The following four plots show the track parameters of Event Filter cosmic tracks from 100k events of run 121419 (2009 data taking). The tracks shown are only from the inside-out tracking, selected by requiring >= 1 silicon hit on the EF track. TRT-only tracks are not included. Sharp peaks due to noisy modules are seen, in particular in the d0 and z0 distributions. The small number of events with positive phi arise when the EF fits a cosmic as two separate tracks. Right, d0 distribution

Figure as better quality eps file

SiEFd0.jpg Contact: Jenna Lane
Right, z0 distribution

Figure as better quality eps file

SiEFz0.jpg Contact: Jenna Lane
Right, eta distribution

Figure as better quality eps file

SiEFEta.jpg Contact: Jenna Lane
Right, phi distribution

Figure as better quality eps file

SiEFPhi.jpg Contact: Jenna Lane
The following 2 pictures show VP1 event displays for a cosmic events from run 121416. Shown are the pixel (turquoise), SCT (blue) and TRT (purple) detectors. The SCT hits are shown as short bars, in orange if they are associated with the track, yellow otherwise. The TRT hits are shown as small dots - orange if associated with the track, white otherwise. The circular surface is to display the TRT barrel hits, since the TRT barrel doesn't measure the z co-ordinate. The TRT endcap hits are displayed on the cylindrical surface, since the TRT endcap doesn't measure the radius from the beampipe.

Here, the track pT is measured by the EF as 7.4 GeV.

png file

vp1_3dcocktail_run121416_evt2330_final.png Contact: Jenna Lane
VP1 Event display for a cosmic event from run 121416. Track pT measured by the EF as 0.5 GeV.

png file

vp1_3dcocktail_run121416_evt2338_final.png Contact: Jenna Lane
The following three plots show the per track efficiency to reconstruct Event Filter tracks with respect to offline tracks for run 121416 (solenoid on). Only tracks from the inside-out tracking were included. (InDet Tracks) These were preselected by requiring EF and offline tracks to have >= 1 silicon hit Loose, medium and tight cuts were then applied to the offline tracks.

Loose: >=8 barrel silicon hits OR >=30 barrel TRT hits, pT > 1 GeV, d0 < 500 mm, -10ns < TRT Event Phase < 40ns.

Medium: >=10 barrel silicon hits, >=20 barrel TRT hits, pT > 1 GeV, d0 < 250mm, -5ns < TRT Event Phase < 30ns.

Tight: >=4 barrel pixel hits, >=12 barrel SCT hits, >=50 barrel TRT hits, pT > 1 GeV, d0 < 40mm, -5ns < TRT Event Phase < 30ns.

Silicon hits is defined as 2*NPixelHits + NSCTHits. Events are from the IDCosmic stream, which were triggered by either the TRTFastOR trigger at L1 or by an inner detector track at L2. For loose tracks, 94.8% efficiency

eps file

Eff121416LooseSi.eps Contact: Jenna Lane
For medium tracks, 100% efficiency

eps file

Eff121416MediumSi.eps Contact: Jenna Lane
For tight tracks, 100% efficiency

eps file

Eff121416TightSi.eps Contact: Jenna Lane
The following three plots show the per track efficiency to reconstruct Event Filter tracks with respect to offline tracks for run 122189 (solenoid on). Only tracks from the inside-out tracking were included. (InDet Tracks) These were preselected by requiring EF and offline tracks to have >= 1 silicon hit Loose, medium and tight cuts were then applied to the offline tracks.

Loose: >=8 barrel silicon hits OR >=30 barrel TRT hits, pT > 1 GeV, d0 < 500 mm, -10ns < TRT Event Phase < 40ns.

Medium: >=10 barrel silicon hits, >=20 barrel TRT hits, pT > 1 GeV, d0 < 250mm, -5ns < TRT Event Phase < 30ns.

Tight: >=4 barrel pixel hits, >=12 barrel SCT hits, >=50 barrel TRT hits, pT > 1 GeV, d0 < 40mm, -5ns < TRT Event Phase < 30ns.

Silicon hits is defined as 2*NPixelHits + NSCTHits. Events are from the IDCosmic stream, which were triggered by either the TRTFastOR trigger at L1 or by an inner detector track at L2. For loose tracks, 94.9% efficiency

eps file

Eff122189LooseSi.eps Contact: Jenna Lane
For medium tracks, 99.9% efficiency

eps file

Eff122189MediumSi.eps Contact: Jenna Lane
For tight tracks, 100% efficiency

eps file

Eff122189TightSi.eps Contact: Jenna Lane

The following three plots show the performance of data preparation and tracking (SiTrack) running on a CPU compared to a GPU. Data preparation (bytestream decoding and clustering) were fully-ported to the GPU and all steps of SiTrack (except for track duplicate merging/removal) were ported to the GPU. Primary vertex reconstruction in SiTrack was not performed.

The first plot shows the performance comparison for data preparation (bytestream decoding and clustering). The test was run on high-luminosity ttbar MC.

eps file

hlt_gpu_data_prep_full.png Contact: Jacob Howard

The second plot shows the performance comparison for tracking (SiTrack). The test was run on high-luminosity ttbar MC.

eps file

hlt_gpu_tracking_full.png Contact: Jacob Howard

The third plot shows the throughput of the full chain of data preparation and tracking in the tau slice on high-luminosity ttbar MC as a function of the number of Athena trigger processes.

eps file

hlt_gpu_tau_roi_processing_rate.png Contact: Jacob Howard

Tau Slice

ATLAS event display for run 90272, event 2895570, triggered by tauNoCut trigger signature, in L1Calo stream. RoIs triggered under such signature have at least 5 GeV energy deposition at L1. The RoI triggered in this event has also a track reconstructed at HLT step, pointing close to nominal interaction region. The HLT calorimeter deposit as well as the track reconstructed are both shown in the event display. Run 90272 is from September 2008, and the event display software used is VP1, using ESD from HLT reprocessing of BS data at Tier0. tau_90272_2895570.jpg Contact: Olya Igonkina
ATLAS event display for run 90272, event 4524774, triggered by tauNoCut trigger signature, in L1Calo stream. RoIs triggered under such signature have at least 5 GeV energy deposition at L1. The RoI triggered in this event has also a track reconstructed at HLT step, pointing close to nominal interaction region. The HLT calorimeter deposit as well as the track reconstructed are both shown in the event display. Run 90272 is from September 2008, and the event display software used is VP1, using ESD from HLT reprocessing of BS data at Tier0. tau_90272_4524774.jpg Contact: Olya Igonkina
ATLAS DQ monitoring for the tau slice for run 92226, taken in October 2008. The reference plots shown in blue are taken for a good run (92054), while the red/green plots show data with unusual/usual distribution. The shifter tracks unusual transverse hadronic energy distribution at L2 for tau candidates. This was identified as a problem in configuration of calibration trigger items (trk9i_calib) which did not ignored laser pulses for calibration of hadronic calorimeter. This was identified on-lined and fixed within short period of time. tau_DQ_92226.jpg Contact: Olya Igonkina
The tau trigger performance is checked with respect to the offline reconstruction. The plots show the pT difference as a function of EF tau (top) and the energy correlation between trigger and offline reconstructions (bottom). No eta dependence was found. The difference is within the expected difference between trigger and offline reconstruction at the cell level comparison. The EF show a reasonable performance with respect to the offline reconstruction. pubplot_tautrigger_difftauptvseta.gif Contact: Soshi Tsuno
The tau trigger performance is checked with respect to the offline reconstruction. The plots show the pT difference as a function of EF tau (top) and the energy correlation between trigger and offline reconstructions (bottom). The difference is within the expected difference between trigger and offline reconstruction at the cell level comparison. The EF show a reasonable performance with respect to the offline reconstruction. pubplot_tautrigger_difftauptvspt.gif Contact: Soshi Tsuno
The tau trigger reconstruction consists of the clusters in the EM and hadronic calorimeters, and the tracks associated in the tau object. This gives us an unique oppotunity to get handle the MIP cluster in the tau. By asking the extrapolated track on the surface of the calorimeter to be matched with the cluster with 20cmx20cm rectangular region, the MIP cluster is identified. Figure presents the energy distributions of the MIP cluster in the EF tau. There are three peaks at 1, 3 and 10GeV in the MIP cluster energy distribution. The 10GeV peak is that the MIP cluster itself fires the trigger with threshold above 5GeV. The rest of them are less energetic cluster but the large cluster exists in neighbor of the MIP cluster, then sum of cluster energy in the tau object exceeds the trigger threshold. Note that the number of clusters associated in the tau object in ∆R≤0.4 is not always one. pubplot_tautrigger_muoefclusterenergy.gif Contact: Soshi Tsuno

HLT Calo

This plot shows the the LVL2 egamma eta/phi hit map for a cosmic run (90246). The signature L1_EM3 was causing the hot spot over there even thought it was prescaled of 2000. The plots are normalized to the bin in eta=0.475. This bin is mostly caused by L1_EM7 hits. ALWAYS when these plots are to be shown, the following to comments should appear : "Most of these problems are addressed directly in hardware during shutdown. These are, anyway, just a handful of channels in 200 thousands (<1/‰)" and this "Bad L1 Trigger Towers are shown here. For cosmic runs, the L1 hardware works out of its operating range (too low Et range). This causes the appearing of such hot towers. It is again, nothing that compromises physics of the ATLAS detector". Run90246.001.jpg Contact: Denis Damazio
This plot shows the the LVL2 egamma eta/phi hit map for a cosmic run (90247). The hot trigger tower shown in the previous run/plot is not there anymore as the noise tower was masked. The signature L1_EM3 is not anymore prescaled. The plots are normalized to the bin in eta=0.475. This bin is mostly caused by L1_EM7 hits. Other hot towers appear in L1_EM3 (before they would be prescaled out!). Two hot cells appear, however, around eta=0.475. These are detector hot cells as we can see in the next plot. ALWAYS when these plots are to be shown, the following to comments should appear : "Most of these problems are addressed directly in hardware during shutdown. These are, anyway, just a handful of channels in 200 thousands (<1/‰)" and this "Bad L1 Trigger Towers are shown here. For cosmic runs, the L1 hardware works out of its operating range (too low Et range). This causes the appearing of such hot towers. It is again, nothing that compromises physics of the ATLAS detector". Run90247.001.001.jpg Contact: Denis Damazio
This plot correlates the HLT L2 egamma eta/phi hit map with the online detector monitoring plot. The detector monitoring plot is only made by detector partition. In this case, we can see clearly the two hot spots also in the detector online monitoring. ALWAYS when these plots are to be shown, the following to comments should appear : "Most of these problems are addressed directly in hardware during shutdown. These are, anyway, just a handful of channels in 200 thousands (<1/‰)" and this "Bad L1 Trigger Towers are shown here. For cosmic runs, the L1 hardware works out of its operating range (too low Et range). This causes the appearing of such hot towers. It is again, nothing that compromises physics of the ATLAS detector". Run90247HLTLAr.001.jpg Contact: Denis Damazio
The L2 egamma algorithm transverse EM energy for two different L1 thresholds. As one can clearly see, the L1 threshold helps to eliminate a lot of detector noise in the L2. By switching from L1_EM3 to L1_EM7, we decrease the amount of events a lot and avoid the low energy tail. We also prove that data can reach the L2 algorithms coming from the LAr detector. L2EMEnergy.001.jpg Contact: Denis Damazio
The L2 egamma algorithm transverse Hadronic energy. This shows that the L2 machines can receive data from the ATLAS hadronic calorimeters. L2HADEnergy.001.jpg Contact: Denis Damazio
L2 egamma time to run the L2 feature extraction algorithms. The average time is well within the 40 ms L2 time budget. A few events appear with high processing times. These are the first event for some of the machines. That happens because part of the conditions loading happen during the first event. ALWAYS mention that this is being addressed by the High Level trigger people AND that thanks to the amount of buffering provided by the data acquisition system, this is not a problem. L2EMTime.001.jpg Contact: Denis Damazio
L2 jet processing time. A few events appear with high processing times. These are the first event for some of the machines. That happens because part of the conditions loading happen during the first event. ALWAYS mention that this is being addressed by the High Level trigger people AND that thanks to the amount of buffering provided by the data acquisition system, this is not a problem. Also, interesting to comment that the RoI for jets is 2.5x2.5 bigger than the EM one, justifying the slower processing times (average of 3ms for egamma and 8.5ms for jets). JetTime.001.jpg Contact: Denis Damazio

This plot shows the the LVL2 egamma eta/phi hit map for a cosmic run (90247). Here a zoom is taken around the region where two hot cells can be seen around eta=0.475. These are detector hot cells as the size of the blur is not an RoI like size (this would indicate a L1 only issue). ALWAYS when these plots are to be shown, the following to comments should appear : "Most of these problems are addressed directly in hardware during shutdown. These are, anyway, just a handful of channels in 200 thousands (<1/‰)". As it can be seen, any cluster close to these hot cells will have a position bias towards them. This imply in the need for an HLT mask.

Run90247_NoHLTMask.gif Contact: Denis Damazio
This plot shows the the LVL2 egamma eta/phi hit map for the cosmic run (90247). Here a zoom is taken around the region where two hot cells could be detected previously (around eta=0.475). These cells were masked on the HLT side but they are still hot in feeding the L1 trigger. As a consequence, an egamma RoI sized blur appear. ALWAYS when these plots are to be shown, the following to comments should appear : "Most of these problems are addressed directly in hardware during shutdown. These are, anyway, just a handful of channels in 200 thousands (<1/‰)". Since those cells are not anymore hot, there are no cluster position bias, and the fake clusters caused by the L1 firing are uniformly distributed in the whole area. This imply that an HLT mask is important to our algorithms, as well as a L1 mask. Run90247_HLTMask.gif Contact: Denis Damazio
Snapshot of the HLT details tab of the HLT Calo expert OHP monitoring. In sequence : Tau L2 algo total (EM+Had) calibrated energy; Tau L2 algo errors (most of them are related to failing to find a hot enough seed - normal for cosmics); Jet L2 algo EM energy with respect to eta; Jet L2 algo had energy with respect to eta; E/gamma L2 algo EM total energy; E/gamma L2 algo Had total energy; E/gamma L2 algo algorithm errors; E/gamma L2 algo data unpacking errors. Using the stored quality bits, we could see that this came from a faulty readout board. Plots being installed as part of the HLT Expert OHP monitoring. Run 114700. OHP1.gif Contact: Denis Damazio
Snapshot of the time performance tab of the HLT Calo expert OHP monitoring. E/gamma L2 algo processing time; L2 Jet algo processing time; The Total time (in this case dominated by the quick random triggers rejection - the larger time is related to Full Scan algorithms being run at the L2); and the T2CaloEgamma versus eta; Plots from run 114700. The most important part of the information there are the average values : 3.69, 7.28, 4.87, 15.34 (this one, again, dominated by the quick remove of random events) and 3.94 (in the Y-axis). It is recommended to put these numbers on top of the plots. re-OHP.gif Contact: Denis Damazio
T2CaloEgamma_eGamma time in the real system. See that the total processing time per RoI averages below 4 ms. The time in the crack regions is a bit higher, as more data has to be unpack and analyzed. Most of the time is spent in data fetching (the algorithm run outside the P1 runs in less than 1ms). time_vs_eta.gif Contact: Denis Damazio
3D plot of an event seen by T2CaloTau. The cells were exported to an ntuple and displayed with some special root macros. We could also check the energy of some of the cells. Very interesting as there is EM and hadronic energy in close by positions. 3D.jpg Contact: Denis Damazio
Total time per event for all the Level 2 trigger algorithms as calculated by the High-Level Trigger resources monitoring system. The optimization performed here is the grouping of a sequence of calls for each ATLAS calorimeter layer into a single one corresponding to the full Region of Interest used by the algorithm. Since the ATLAS data flow system is equipped with large buffers, the event in the tail on this plot do not cause any dead-time in the Trigger. The total average Level 2 time is targeted at 40ms for the final system. CostMonitorPlot.gif Contact: Denis Damazio
Data retrieval and total processing time for different Level 2 trigger algorithms before and after optimization of the data retrieval scheme from detector buffers. The different global processing times for each algorithm depend on caching effects and Region of Interest sizes. Both data taking periods had at most a peak luminosity of 2.8e30cm-2s-1. TimePlotApprovedTable.jpg Contact: Denis Damazio

Links


Responsible: Trigger coordinator
Last reviewed by: Never reviewed

Topic attachments
I Attachment History Action Size Date Who Comment
GIFgif 10sep.gif r1 manage 14.7 K 2009-03-25 - 13:37 DanielSherman  
GIFgif 12sep.gif r1 manage 12.5 K 2009-03-25 - 13:38 DanielSherman  
JPEGjpg 3D.jpg r1 manage 370.4 K 2009-06-09 - 16:27 DenisDamazio  
PNGpng BPTX_bunchintensity.png r1 manage 7.8 K 2008-12-05 - 10:50 ThiloPauly  
PDFpdf Corrected.pdf r1 manage 71.9 K 2009-12-16 - 21:56 ThorstenWengler  
PNGpng Corrected.png r1 manage 228.0 K 2009-12-16 - 21:56 ThorstenWengler  
Unknown file formateps Eff121416LooseSi.eps r1 manage 11.3 K 2009-09-25 - 16:26 JennaLane  
Unknown file formateps Eff121416MediumSi.eps r1 manage 10.1 K 2009-09-25 - 16:26 JennaLane  
Unknown file formateps Eff121416TightSi.eps r1 manage 10.9 K 2009-09-25 - 16:26 JennaLane  
Unknown file formateps Eff122189LooseSi.eps r1 manage 11.2 K 2009-09-25 - 16:26 JennaLane  
Unknown file formateps Eff122189MediumSi.eps r1 manage 11.6 K 2009-09-25 - 16:27 JennaLane  
Unknown file formateps Eff122189TightSi.eps r1 manage 10.9 K 2009-09-25 - 16:27 JennaLane  
Unknown file formateps Eff92048LooseNoTRT.eps r1 manage 13.9 K 2009-06-09 - 11:49 JennaLane  
Unknown file formateps EffLoose91862.eps r1 manage 16.9 K 2009-06-09 - 11:39 JennaLane  
JPEGjpg EffLoose91862.jpg r1 manage 21.7 K 2009-06-09 - 10:53 JennaLane  
Unknown file formateps EffLoose92048.eps r1 manage 17.0 K 2009-06-09 - 11:44 JennaLane  
JPEGjpg EffLoose92048.jpg r1 manage 21.2 K 2009-06-09 - 11:08 JennaLane  
JPEGjpg EffLooseSil92048.jpg r1 manage 21.8 K 2009-06-09 - 11:09 JennaLane  
Unknown file formateps EffMed91862.eps r1 manage 13.6 K 2009-06-09 - 11:42 JennaLane  
JPEGjpg EffMed91862.jpg r1 manage 22.1 K 2009-06-09 - 10:55 JennaLane  
Unknown file formateps EffMed92048.eps r1 manage 13.6 K 2009-06-09 - 11:45 JennaLane  
JPEGjpg EffMed92048.jpg r1 manage 24.2 K 2009-06-09 - 11:09 JennaLane  
Unknown file formateps EffTight91862.eps r1 manage 9.8 K 2009-06-09 - 11:42 JennaLane  
JPEGjpg EffTight91862.jpg r1 manage 19.5 K 2009-06-09 - 10:55 JennaLane  
Unknown file formateps EffTight92048.eps r1 manage 9.8 K 2009-06-09 - 11:45 JennaLane  
JPEGjpg EffTight92048.jpg r1 manage 20.3 K 2009-06-09 - 11:09 JennaLane  
GIFgif IsoTrk_cosmics.gif r1 manage 16.2 K 2009-06-05 - 12:13 CamillaMaiani Muons isolation distribution for the LVL2 trigger ID-based muIso algorithm with cosmic-ray muons
Postscriptps IsoTrk_cosmics.ps r1 manage 8.3 K 2009-06-05 - 12:15 CamillaMaiani Muons isolation distribution for the LVL2 trigger ID-based muIso algorithm with cosmic-ray muons (ps format)
Unknown file formateps L2TotalTime.eps r1 manage 7.2 K 2011-01-17 - 15:20 ImmaRiu L2 total time in eps
GIFgif L2TotalTime.gif r1 manage 8.0 K 2011-01-17 - 15:19 ImmaRiu L2 total time in gif
Unknown file formateps L2eff.CombinedInDetTracks_CTB.d0.goldenSi_3.eps r1 manage 20.9 K 2009-03-23 - 18:56 SasaFratina L2 eff in cosmic data as a function of offline track impact parameter d0
PNGpng L2eff.CombinedInDetTracks_CTB.d0.goldenSi_3.png r1 manage 19.5 K 2009-03-23 - 18:18 SasaFratina L2 eff in cosmic data as a function of offline track impact parameter d0
Unknown file formateps L2eff.CombinedInDetTracks_CTB.ep.goldenSi_200.eps r1 manage 20.2 K 2009-03-23 - 18:55 SasaFratina L2 eff in cosmic data as a function of TRT event phase (time of cosmic track)
PNGpng L2eff.CombinedInDetTracks_CTB.ep.goldenSi_200.png r1 manage 20.2 K 2009-03-23 - 18:13 SasaFratina L2 eff in cosmic data as a function of TRT event phase (time of cosmic track)
Unknown file formateps L2eff.CombinedInDetTracks_CTB.pt.goldenSi_203.eps r1 manage 11.8 K 2009-03-23 - 18:56 SasaFratina L2 eff in 2008 cosmic data as a function of offline track pT
PNGpng L2eff.CombinedInDetTracks_CTB.pt.goldenSi_203.png r1 manage 15.8 K 2009-03-23 - 18:19 SasaFratina L2 eff in 2008 cosmic data as a function of offline track pT
GIFgif OHP1.gif r1 manage 50.1 K 2009-06-09 - 16:01 DenisDamazio  
PNGtiff OHP1.tiff r1 manage 122.4 K 2009-06-09 - 15:55 DenisDamazio  
GIFgif Run90247_HLTMask.gif r1 manage 18.7 K 2009-06-09 - 15:42 DenisDamazio  
GIFgif Run90247_NoHLTMask.gif r1 manage 18.3 K 2009-06-09 - 15:43 DenisDamazio  
JPEGjpg ScopeTraceMbts.jpg r1 manage 218.5 K 2009-01-07 - 13:04 DavidBerge Scope trace of MBTS analogue signal of a cosmic muon and a splash event
Unknown file formateps SiEFEta.eps r1 manage 10.2 K 2009-09-25 - 15:00 JennaLane  
JPEGjpg SiEFEta.jpg r1 manage 21.0 K 2009-09-25 - 15:01 JennaLane  
Unknown file formateps SiEFPhi.eps r1 manage 9.7 K 2009-09-25 - 15:03 JennaLane  
JPEGjpg SiEFPhi.jpg r1 manage 21.2 K 2009-09-25 - 15:04 JennaLane  
Unknown file formateps SiEFd0.eps r1 manage 8.6 K 2009-09-25 - 15:00 JennaLane  
JPEGjpg SiEFd0.jpg r1 manage 21.4 K 2009-09-25 - 15:00 JennaLane  
Unknown file formateps SiEFz0.eps r1 manage 10.2 K 2009-09-25 - 15:04 JennaLane  
JPEGjpg SiEFz0.jpg r1 manage 23.8 K 2009-09-25 - 15:05 JennaLane  
JPEGjpg Theta_Mean.jpg r1 manage 47.2 K 2009-11-09 - 13:55 GiuseppeSalamanna  
GIFgif TrackMatchEffect_Eta_off.gif r1 manage 16.7 K 2009-11-07 - 01:23 GiuseppeSalamanna  
PDFpdf Uncorrected.pdf r1 manage 0.3 K 2009-12-16 - 21:57 ThorstenWengler  
PNGpng Uncorrected.png r1 manage 53.0 K 2009-12-16 - 21:57 ThorstenWengler  
Unknown file formateps bc-distr.sl_vs_pad.eps r1 manage 16.1 K 2009-11-07 - 01:20 GiuseppeSalamanna  
JPEGjpg bc-distr.sl_vs_pad.jpg r1 manage 99.8 K 2009-11-09 - 13:52 GiuseppeSalamanna  
JPEGjpg bptx_and_mbts_7turns.jpg r1 manage 429.7 K 2008-12-05 - 10:50 ThiloPauly  
JPEGjpg bptx_long_coast.jpg r1 manage 164.6 K 2008-12-05 - 10:51 ThiloPauly  
Unknown file formateps comp.new.eps r1 manage 9.5 K 2009-11-11 - 15:39 MichelaBiglietti  
JPEGjpg comp.new.jpg r1 manage 20.4 K 2009-11-11 - 15:38 MichelaBiglietti  
PNGpng emTof_physics.png r1 manage 5.0 K 2010-05-10 - 05:19 TaylorChilders l1calo ToF vertex 2 detector (EM)
PNGpng emTof_physics_splash.png r1 manage 5.3 K 2010-05-10 - 05:54 TaylorChilders l1calo ToF total correction (EM)
PNGpng emTof_splash.png r1 manage 4.9 K 2010-05-10 - 05:53 TaylorChilders l1calo ToF collimator 2 detector (EM)
GIFgif event90127_307141.gif r2 r1 manage 125.3 K 2009-04-10 - 12:39 MarkSutton L2 Tracking event display
PDFpdf event90127_307141.pdf r1 manage 129.1 K 2009-03-29 - 17:42 MarkSutton  
PNGpng h_emDelaySumNs_new.png r1 manage 11.8 K 2010-05-10 - 05:56 TaylorChilders l1calo correct peak time for 2009 splash event (EM)
PNGpng h_emDelaySumNs_new_px.png r1 manage 6.8 K 2010-05-10 - 05:58 TaylorChilders l1calo eta projection of corrected peak time for 2009 splash event (EM)
PNGpng h_emDelaySumNs_splash.png r1 manage 10.1 K 2010-05-10 - 05:16 TaylorChilders l1calo peak time for 2009 splash event (EM)
PNGpng h_emDelaySumNs_splash_px.png r1 manage 6.9 K 2010-05-10 - 05:17 TaylorChilders l1calo eta projection of peak time for 2009 splash event (EM)
PNGpng h_emFullDelay.png r1 manage 8.2 K 2010-05-10 - 06:02 TaylorChilders l1calo mean fullDelayData derived from 2009 splash events (EM)
PNGpng h_emSummary_timing.png r1 manage 11.8 K 2010-05-10 - 06:01 TaylorChilders l1calo mean peak time for all 2009 splashes (EM)
PNGpng h_hadDelaySumNs_new.png r1 manage 11.1 K 2010-05-10 - 05:57 TaylorChilders l1calo corrected peak time for 2009 splash event (HAD)
PNGpng h_hadDelaySumNs_new_px.png r1 manage 6.9 K 2010-05-10 - 05:57 TaylorChilders l1calo eta projection of corrected peak time for 2009 splash event (HAD)
PNGpng h_hadDelaySumNs_splash.png r1 manage 10.0 K 2010-05-10 - 05:17 TaylorChilders l1calo peak time for 2009 splash event (HAD)
PNGpng h_hadDelaySumNs_splash_px.png r1 manage 6.9 K 2010-05-10 - 05:18 TaylorChilders l1calo eta projection of peak time for 2009 splash event (HAD)
PNGpng h_hadFullDelay.png r1 manage 9.3 K 2010-05-10 - 06:03 TaylorChilders l1calo mean fullDelayData derived from 2009 splash events (HAD)
PNGpng h_hadSummary_timing.png r1 manage 10.8 K 2010-05-10 - 06:01 TaylorChilders l1calo mean peak time for all 2009 splashes (HAD)
PNGpng hadTof_physics.png r1 manage 5.6 K 2010-05-10 - 05:20 TaylorChilders l1calo ToF vertex 2 detector (HAD)
PNGpng hadTof_physics_splash.png r3 r2 r1 manage 5.4 K 2010-05-10 - 06:32 TaylorChilders l1calo ToF total correction (HAD)
PNGpng hadTof_splash.png r2 r1 manage 5.2 K 2010-05-10 - 06:05 TaylorChilders l1calo ToF collimator 2 detector (HAD)
Unknown file formateps hlt_gpu_data_prep_full.eps r1 manage 17.2 K 2012-05-15 - 11:35 JacobHoward  
PNGpng hlt_gpu_data_prep_full.png r1 manage 141.0 K 2012-05-15 - 11:33 JacobHoward  
Unknown file formateps hlt_gpu_tau_roi_processing_rate.eps r1 manage 8.3 K 2012-05-15 - 11:33 JacobHoward  
PNGpng hlt_gpu_tau_roi_processing_rate.png r1 manage 101.6 K 2012-05-15 - 11:33 JacobHoward  
Unknown file formateps hlt_gpu_tracking_full.eps r1 manage 12.4 K 2012-05-15 - 11:33 JacobHoward  
PNGpng hlt_gpu_tracking_full.png r1 manage 102.7 K 2012-05-15 - 11:33 JacobHoward  
Unknown file formateps idscan-a0.eps r1 manage 1502.9 K 2009-03-30 - 17:26 MarkSutton IDScan d0 distribution for IDCosmic stream from Tier-0 monitoring
GIFgif idscan-a0.gif r1 manage 7.6 K 2009-04-10 - 11:52 MarkSutton IDCosmic Tier-0 monitoring d0 distribution for IDScan
Unknown file formateps idscan-z0.eps r1 manage 1502.9 K 2009-03-30 - 17:27 MarkSutton IDScan z distribution from IDCosmic stream from Tier-0 monitoring
GIFgif idscan-z0.gif r1 manage 8.7 K 2009-04-10 - 11:52 MarkSutton IDCosmic Tier-0 monitoring z0 distribution for IDScan
JPEGjpg l1calo_correlation.JPG r1 manage 45.0 K 2008-11-18 - 16:22 SteveHillier L1Calo calorimeter energy correlation plot
Postscriptps l1calo_correlation.ps r1 manage 2530.8 K 2010-03-22 - 16:35 SteveHillier L1Calo ET correlation plot (PS version)
PNGtiff l1calo_correlation.tiff r1 manage 138.1 K 2010-03-22 - 16:35 SteveHillier L1Calo ET correlation plot (TIFF version)
JPEGjpg l1calo_cosmic.JPG r1 manage 87.9 K 2008-11-18 - 16:32 SteveHillier L1Calo cosmic event
Postscriptps l1calo_cosmic.ps r1 manage 4253.1 K 2010-03-22 - 16:37 SteveHillier L1Calo cosmic event (PS version)
PNGtiff l1calo_cosmic.tiff r1 manage 1345.3 K 2010-03-22 - 16:37 SteveHillier L1Calo cosmic event (TIFF version)
PNGpng l1calo_digitizedSignalWithFit.png r1 manage 6.5 K 2010-05-10 - 05:08 TaylorChilders l1calo digitized signal(LAr)
PNGpng l1calo_reconstructedSignalWithFit.png r1 manage 7.7 K 2010-05-10 - 05:15 TaylorChilders l1calo reconstructed phos4 signal (LAr)
JPEGjpg l1calo_spectrum.JPG r1 manage 35.7 K 2008-11-18 - 16:27 SteveHillier L1Calo cosmic spectrum
Postscriptps l1calo_spectrum.ps r1 manage 1719.9 K 2010-03-22 - 16:36 SteveHillier L1Calo cosmic hadronic spectrum (PS version)
PNGtiff l1calo_spectrum.tiff r1 manage 83.3 K 2010-03-22 - 16:36 SteveHillier L1Calo cosmic hadronic spectrum (TIFF version)
JPEGjpg l1calo_splash.JPG r1 manage 281.7 K 2008-11-19 - 10:13 SteveHillier L1Calo splash event
GIFgif l1rates.gif r1 manage 8.3 K 2008-11-27 - 17:39 AndreaMessina level-1 trigger rates
GIFgif mbts-87863-mod.gif r1 manage 15.9 K 2009-03-25 - 13:37 DanielSherman  
Unknown file formateps muTile1.eps r1 manage 12.9 K 2009-03-20 - 01:16 AndreaVentura  
GIFgif muTile1.gif r1 manage 15.6 K 2009-03-20 - 01:17 AndreaVentura  
Unknown file formateps muTile2.eps r1 manage 19.6 K 2009-03-20 - 01:17 AndreaVentura  
GIFgif muTile2.gif r1 manage 18.3 K 2009-03-20 - 01:17 AndreaVentura  
Unknown file formateps muonEF1.eps r1 manage 11.1 K 2009-03-20 - 01:15 AndreaVentura  
GIFgif muonEF1.gif r1 manage 12.6 K 2009-03-20 - 01:15 AndreaVentura  
Unknown file formateps muonEF2.eps r1 manage 10.7 K 2009-03-20 - 01:16 AndreaVentura  
GIFgif muonEF2.gif r1 manage 12.9 K 2009-03-20 - 01:16 AndreaVentura  
PNGpng peakpos_0x00100302.png r1 manage 8.4 K 2010-05-10 - 06:00 TaylorChilders l1calo peak time vs. event number for 2009 splash events (uniform)
PNGpng peakpos_0x041f0700.png r1 manage 7.7 K 2010-05-10 - 05:59 TaylorChilders l1calo peak time vs. event number for 2009 splash events (non-uniform)
Unknown file formateps pres.eps r1 manage 184.5 K 2009-03-29 - 17:49 MarkSutton Tier-0 monitoring idscan phi display (IDCosmic slice
GIFgif pres.gif r1 manage 64.4 K 2009-04-10 - 11:51 MarkSutton IDCosmic Tier-0 monitoring phi distribution from IDScan
GIFgif re-OHP.gif r1 manage 37.4 K 2009-06-09 - 16:02 DenisDamazio  
Unknown file formateps run137651.eps r1 manage 26.0 K 2009-11-11 - 15:03 MichelaBiglietti  
JPEGjpg run137651.jpg r1 manage 212.7 K 2009-11-11 - 15:08 MichelaBiglietti  
Unknown file formateps run91900_absPtTrkPre_vs_DelPhiTrk.eps r1 manage 10.5 K 2009-06-05 - 13:58 ArantxaRuizMartinez <nop>TileMuId combined with TrigIDSCAN (before parametrization) for run 91900 in eps format
GIFgif run91900_absPtTrkPre_vs_DelPhiTrk.gif r1 manage 7.4 K 2009-06-05 - 13:59 ArantxaRuizMartinez <nop>TileMuId combined with TrigIDSCAN (before parametrization) for run 91900 in gif format
Unknown file formateps run91900_absPtTrkPre_vs_DelPhiTrkTR.eps r2 r1 manage 10.9 K 2009-06-05 - 15:44 ArantxaRuizMartinez <nop>TileMuId combined with TrigIDSCAN (after parametrization) for run 91900 in eps format
GIFgif run91900_absPtTrkPre_vs_DelPhiTrkTR.gif r1 manage 7.7 K 2009-06-05 - 14:03 ArantxaRuizMartinez <nop>TileMuId combined with TrigIDSCAN (after parametrization) for run 91900 in gif format
Unknown file formateps run_90272_Mufast_endcap_Alpha_TGC-MDT_match.eps r1 manage 12.0 K 2009-03-31 - 20:42 AlessandroDiMattia Match between Alpha computed with MDT and Alpha computed with TGC
GIFgif run_90272_Mufast_endcap_Alpha_TGC-MDT_match.gif r1 manage 6.1 K 2009-03-31 - 20:44 AlessandroDiMattia Match between Alpha computed with MDT and Alpha computed with TGC
Unknown file formateps run_90272_Mufast_endcap_middle_MDT_drift_space.eps r1 manage 11.3 K 2009-03-31 - 17:57 AlessandroDiMattia Converted MDT drift space of the Middle fit segment hits selected by L2 muFast
GIFgif run_90272_Mufast_endcap_middle_MDT_drift_space.gif r1 manage 4.9 K 2009-03-31 - 17:58 AlessandroDiMattia Converted MDT drift space of the Middle fit segment hits selected by L2 muFast
Unknown file formateps run_90272_Mufast_endcap_middle_TGC-MDT_corr.eps r1 manage 279.7 K 2009-03-31 - 17:54 AlessandroDiMattia Correlation between MDT and TGC hit clusters seen by L2 muFast
GIFgif run_90272_Mufast_endcap_middle_TGC-MDT_corr.gif r1 manage 18.1 K 2009-03-31 - 17:55 AlessandroDiMattia Correlation between MDT and TGC hit clusters seen by L2 muFast
Unknown file formateps run_90272_Mufast_endcap_middle_missing_MDT.eps r1 manage 22.2 K 2009-03-31 - 18:00 AlessandroDiMattia Distribution on x-y ATLAS coordinate of the L2 muFast cluster finding inefficiencies
GIFgif run_90272_Mufast_endcap_middle_missing_MDT.gif r1 manage 5.5 K 2009-03-31 - 18:01 AlessandroDiMattia Distribution on x-y ATLAS coordinate of the L2 muFast cluster finding inefficiencies
Unknown file formateps run_92226_Mufast_barrel_Alpha_2seg.eps r1 manage 11.4 K 2009-03-31 - 11:59 AlessandroDiMattia Alpha angle in the Muon barrel by L2 muFast, obtained requiring two MDT segments
GIFgif run_92226_Mufast_barrel_Alpha_2seg.gif r1 manage 11.3 K 2009-03-31 - 12:00 AlessandroDiMattia Alpha angle from L2 muFast in the barrel, obtained requiring two MDT segments
Unknown file formateps run_92226_Mufast_barrel_Alpha_3seg.eps r1 manage 11.3 K 2009-03-31 - 12:00 AlessandroDiMattia Alpha angle from L2 muFast in the barrel, obtained requiring three MDT segments
GIFgif run_92226_Mufast_barrel_Alpha_3seg.gif r1 manage 10.7 K 2009-03-31 - 12:02 AlessandroDiMattia Alpha angle from L2 muFast in the barrel, obtained requiring three MDT segments
Unknown file formateps run_92226_Mufast_barrel_IP_2seg.eps r1 manage 10.8 K 2009-03-31 - 15:18 AlessandroDiMattia Z0 of barrel tracks from L2 muFast computed using tracks with at least two MDT fit segments reconstructed
GIFgif run_92226_Mufast_barrel_IP_2seg.gif r1 manage 3.2 K 2009-03-31 - 15:19 AlessandroDiMattia Z0 of barrel tracks from L2 muFast computed using tracks with at least two MDT fit segments reconstructed
Unknown file formateps run_92226_Mufast_barrel_IP_3seg.eps r1 manage 11.9 K 2009-03-31 - 15:20 AlessandroDiMattia Z0 of barrel tracks from L2 muFast computed using tracks with three MDT fit segments reconstructed
GIFgif run_92226_Mufast_barrel_IP_3seg.gif r1 manage 3.3 K 2009-03-31 - 15:21 AlessandroDiMattia Z0 of barrel tracks from L2 muFast computed using tracks with three MDT fit segments reconstructed
Unknown file formateps run_92226_Mufast_barrel_Sagitta_2seg.eps r1 manage 12.2 K 2009-03-31 - 15:03 AlessandroDiMattia Barrel track Sagitta from L2 muFast computed using tracks with at least two MDT fit segments reconstructed
GIFgif run_92226_Mufast_barrel_Sagitta_2seg.gif r1 manage 3.6 K 2009-03-31 - 15:14 AlessandroDiMattia Barrel track Sagitta from L2 muFast computed using tracks with at least two MDT fit segments reconstructed
Unknown file formateps run_92226_Mufast_barrel_Sagitta_3seg.eps r1 manage 11.4 K 2009-03-31 - 15:15 AlessandroDiMattia Barrel track Sagitta from L2 muFast computed using tracks with three MDT fit segments reconstructed
GIFgif run_92226_Mufast_barrel_Sagitta_3seg.gif r1 manage 3.0 K 2009-03-31 - 15:16 AlessandroDiMattia Barrel track Sagitta from L2 muFast computed using tracks with three MDT fit segments reconstructed
Unknown file formateps sitrack-z0.eps r1 manage 1502.9 K 2009-03-30 - 17:28 MarkSutton SiTrack z distribution from IDCosmic stream from Tier-0 monitoring
GIFgif sitrack-z0.gif r1 manage 8.3 K 2009-04-10 - 11:53 MarkSutton IDCosmic Tier-0 monitoring z0 distribution for SiTrack
JPEGjpg tau_90272_2895570.jpg r1 manage 234.7 K 2009-03-25 - 22:10 StefaniaXella  
JPEGjpg tau_90272_4524774.jpg r1 manage 274.6 K 2009-03-25 - 22:34 StefaniaXella  
JPEGjpg tau_DQ_92226.jpg r1 manage 117.5 K 2009-03-26 - 00:29 StefaniaXella  
JPEGjpg tgc-timing-1beam.jpg r3 r2 r1 manage 217.7 K 2009-01-23 - 15:39 MasayaIshino  
GIFgif time_vs_eta.gif r1 manage 16.2 K 2009-06-09 - 16:07 DenisDamazio  
PNGpng vp1_3dcocktail_run121416_evt2330_final.png r1 manage 25.8 K 2009-09-25 - 15:23 JennaLane  
PNGpng vp1_3dcocktail_run121416_evt2338_final.png r1 manage 28.4 K 2009-09-25 - 15:23 JennaLane  
JPEGjpg wrtRPC.jpg r1 manage 69.7 K 2009-11-11 - 15:09 MichelaBiglietti  
Unknown file formateps wrtRpc.eps r1 manage 20.6 K 2009-11-11 - 15:02 MichelaBiglietti  
Edit | Attach | Watch | Print version | History: r64 < r63 < r62 < r61 < r60 | Backlinks | Raw View | WYSIWYG | More topic actions
Topic revision: r64 - 2018-01-24 - JoergStelzer
 
    • Cern Search Icon Cern Search
    • TWiki Search Icon TWiki Search
    • Google Search Icon Google Search

    Atlas All webs login

This site is powered by the TWiki collaboration platform Powered by PerlCopyright & 2008-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