AtlasPublicTopicHeader.png

Level-1 Calorimeter Trigger Public Results

Introduction

Approved plots that can be shown by ATLAS speakers at conferences and similar events. Please do not add figures on your own. Contact the responsible project leader in case of questions and/or suggestions. Follow the guidelines on the trigger public results page. [ For L1Calo members: See also a discussion on the plot-approval procedure at the L1Calo Weekly meeting (9 July 2018): link to PDF. ]

Performance studies of the ATLAS L1Calorimeter trigger upgrade for run 3 (July 2, 2018)

Per-jet efficiency computed from a HH→bb(bb) Monte Carlo simulation comparing the performance of the Run 2 trigger system with the proposed system after the Phase-1 upgrade, described in detail in ATLAS-TDR-023. The efficiency is shown for Run 2 L1 jets (black) and jFEX jets (blue). The jFEX algorithm is with a new optimisation that uses a circular 0.9x0.9 sliding window with a 0.3x0.3 seed and a search window for the local maximum of 0.5x0.5. The offline Anti-kt reconstruction algorithm (red) runs on jTowers with a radius parameter of R=0.4 and is shown for reference, it is not planned to run in the hardware. The efficiency for run 2 jets is shown as an illustration of what is possible in the current hardware. For both the jFEX algorithm and the offline Anti-kt reference, a noise threshold of 2 GeV is applied to all jTowers to suppress noise from electronics and pileup. The thresholds of the three methods have been tuned to have the same rate. The efficiency is computed with respect to the calibrated offline jets with |η| < 2.5 and $p_T$ > 30 GeV. ATL-COM-DAQ-2018-019 .png
png pdf eps
Per-jet efficiency for jets with nearby jets computed from a HH→bb(bb) Monte Carlo simulation comparing the performance of the Run 2 trigger system with the proposed system after the Phase-1 upgrade, described in detail in ATLAS-TDR-023. The efficiency is shown for Run 2 L1 jets (black) and jFEX jets (blue). The jFEX algorithm is with a new optimisation that uses a circular 0.9x0.9 sliding window with a 0.3x0.3 seed and a search window for the local maximum of 0.5x0.5. The offline Anti-kt reconstruction algorithm (red) runs on jTowers with a radius parameter of R=0.4 and is shown for reference, it is not planned to run in the hardware. The efficiency for run 2 jets is shown as an illustration of what is possible in the current hardware. For both the jFEX algorithm and the offline Anti-kt reference, a noise threshold of 2 GeV is applied to all jTowers to suppress noise from electronics and pileup. The thresholds of the three methods have been tuned to have the same rate. The efficiency is computed with respect to the calibrated offline jets with |η| < 2.5 and $p_T$ > 30 GeV, where at least 1 jet above 30 GeV is required to be within ΔR=0.6 of the probe jet. ATL-COM-DAQ-2018-019 .png
png pdf eps

Efficiency computed from a Z→ee Monte Carlo simulation comparing the performance of the existing electron trigger with the proposed trigger that will be implemented during the Phase-1 upgrade, described in detail ATLAS-TDR-023. Details of the electron isolation and ET calculation are also described in ATLAS-TDR-023. The isolation thresholds were tuned to give the lowest rate while maintaining 95% efficiency for electrons with truth 30 GeV < $E_T$ < 50 GeV. For clusters with $E_T$ > 60 GeV, the isolation requirement was removed for better comparison, as this is also done in the current electron trigger. The threshold of 21 GeV (blue) has been chosen such that the trigger has about the same rate as the Run 2 trigger L1_EM24VHI (black) ATL-COM-DAQ-2017-033. The threshold of 28 GeV (red) results in about half that rate. ATL-COM-DAQ-2018-019 .png
png pdf eps
Efficiency of the new missing transverse energy (MET) algorithm proposed for the Run 3 jFEX ATLAS-TDR-023, shown for a simulated sample of ZH→ννbb events measured with respect to the truth MET. The MET in the jFEX is computed from the vector sum of all towers with ET above an η-dependent threshold. The threshold ranges from 0-5 GeV and is designed to suppress noise arising from electronics and pileup. The MET threshold (abbreviated XE) was tuned to 57 GeV to give approximately the same rate as L1_XE50 in Run 2 data. The efficiency of the jFEX MET is compared to L1_XE50 as measured in a selection of Z→μμ events, where the Z boson serves as proxy for the MET, as muons are not included in the calculation of MET in the trigger. This efficiency plot is taken directly from MissingEtTriggerPublicResults. ATL-COM-DAQ-2018-019 .png
png pdf eps

L1Calo Performance plots 2018 (Run 2)

L1Topo Hardware-Simulation Mismatches: Mismatch rates between L1Topo hardware and simulation. First row shows for each trigger chain the ratio between number of events selected by the simulation but not by the hardware and the total number of events accepted by the simulation. Second row shows the ratio of number of events selected by the hardware but not by the simulation and the total number of events accepted by hardware. Masses and energies are expressed in GeV and angles in radians. Sub-indexes “i, j” denote lists of trigger objects, “1” means leading in terms of transverse momentum. ATL-COM-DAQ-2018-170 .png
png pdf eps
L1Topo Hardware-Simulation Mismatches: Mismatch rates between L1Topo hardware and simulation. First row shows for each trigger chain the ratio between number of events selected by the simulation but not by the hardware and the total number of events accepted by the simulation. Second row shows the ratio of number of events selected by the hardware but not by the simulation and the total number of events accepted by hardware. Masses and energies are expressed in GeV and angles in radians. Sub-indexes “i, j” denote lists of trigger objects; bx+1 refers to the bunch crossing immediately after the event. Super-indexes “C, F” for jets denote central (|η|<2.5) and full range (|η|<4.9), respectively. ATL-COM-DAQ-2018-170 .png
png pdf eps

L1Calo Performance plots 2017 (Run 2)

Average Pedestal Shift (8b4e): The plots show the average deviation of the digitised Level-1 Calorimeter Trigger input signals from the expected flat baseline as function of the bunch crossing (BC) number for a selected part of the LHC orbit. The pedestal baseline is the signal height in absence of energy depositions in a given trigger tower. One FADC count corresponds to a transverse energy deposit of approximately 250 MeV. Shown is the mean pedestal shift taking into account all towers of the LAr Electromagnetic Calorimeter Barrel A partition (EMB-A) [left] and of the LAr Forward Calorimeter 1 A partition (FCAL1-A) [right] for lumi blocks 78 and 540 of ATLAS run 340368, corresponding to average mu values of 58.1 and 38.1, respectively. The corresponding LHC fill is 6370 in 8b4e bunch filling scheme. Only read out FADC values corresponding to filled LHC bunches are taken into account. ATL-COM-DAQ-2018-004 .png
png pdf
.png
png pdf
Average Pedestal Shift (8b4e): The plots show the average deviation of the digitised Level-1 Calorimeter Trigger input signals from the expected flat baseline as function of the bunch crossing (BC) number for a selected part of the LHC orbit. The pedestal baseline is the signal height in absence of energy depositions in a given trigger tower. One FADC count corresponds to a transverse energy deposit of approximately 250 MeV. Shown is the mean pedestal shift taking into account all towers of the LAr Electromagnetic Calorimeter Barrel A partition (EMB-A) [left] and of the LAr Forward Calorimeter 1 A partition (FCAL1-A) [right] for lumi blocks 78 and 540 of ATLAS run 340368, corresponding to average mu values of 58.1 and 38.1, respectively. The corresponding LHC fill is 6370 in 8b4e bunch filling scheme. The full readout window of 5 FADC counts centred around the triggered bunch crossing is taken into account. Filled bunches are indicated by grey background colour. ATL-COM-DAQ-2018-004 .png
png pdf
.png
png pdf
Average Pedestal Correction (8b4e): The plots show the pedestal correction as function of the bunch crossing (BC) number for a selected part of the LHC orbit. It is continuously calculated and applied by the firmware of the new Multichip Modules in the PreProcessor electronics of the Level-1 Calorimeter Trigger (L1Calo) in order to correct online the ET calculation result of each trigger tower for pile-up induced baseline shifts. To enhance the signal over noise ratio, L1Calo uses a finite impulse response filter operated on five consecutive values of the digitised input signal. The pedestal correction in units of FIR Counts (i.e. weighted FADC counts) is the difference between an average of each trigger tower's digital filter output over 65536 LHC orbits (approximately 6s) and a corresponding target value determined by the filter output in absence of any energy deposition. Shown is the mean correction for all towers of the LAr Electromagnetic Calorimeter Barrel A partition (EMB-A) [left] and of the LAr Forward Calorimeter 1 A partition (FCAL1-A) [right] for lumi blocks 78 and 540 of ATLAS run 340368, corresponding to average mu values of 58.1 and 38.1, respectively. The corresponding LHC fill is 6370 in 8b4e bunch filling scheme. A readout value of the pedestal correction is available only for filled bunches. ATL-COM-DAQ-2018-004 .png
png pdf
.png
png pdf
Pedestal Correction: The plot shows the Pedestal Correction as calculated by the firmware of the new Multichip Module (nMCM), a component on the PreProcessor of the Level-1 Calorimeter Trigger (L1Calo), for a selected part of the LHC orbit. The pedestal correction is computed for each bunch crossing, and is plotted in units of weighted ADC counts. The average pedestal correction is calculated over 65536 LHC orbits, which corresponds to a duration of approximately 6 seconds. Shown is the correction for the LAr calorimeter Electromagnetic Barrel A partition (EMB-A).
This plot is taken from the L1Calo offline monitoring that uses a dedicated data stream (express stream). The data was taken by ATLAS in run 327342 with =33.8. The corresponding LHC fill is 5849. ATL-COM-DAQ-2017-064
.png
png pdf
Average Pedestal Shift: The plot shows the average deviation from the expected flat baseline of the digitized L1Calo input signals as a function of the Bunch Crossing (BC) Number for a selected part of the LHC orbit. The baseline is the signal height in the absence of energy depositions in a given trigger tower. For this plot only input signals from the LAr calorimeter Electromagnetic Barrel A partition (EMB-A) are taken into account. The average is constructed over all trigger towers without significant energy depositions and over all considered events in the given ATLAS run. One ADC count corresponds to a transverse energy deposition of approximately 0.25 GeV. This plot is taken from the L1Calo offline monitoring that uses a dedicated data stream (express stream). The data was taken by ATLAS in run 327342 with =33.8. The corresponding LHC fill is 5849. ATL-COM-DAQ-2017-064 .png
png pdf

L1Calo Performance plots 2016 (Run 2)

Comparison of the L1Topo decision from hardware and from simulation for several L1Topo trigger items. For this plot, 258k events have been analysed. Empty bins correspond to: < 3.8x10−4 [%]. Simulated decisions are either from the ”non-bitwise” implementation or from the ”bitwise-correct” one. The fraction of events for which both simulated outputs disagree with the hardware output is indicated in blue. The fraction of events for which only the ”bitwise-correct” (”non-bitwise”) simulation differs from the hardware output is indicated in red (green). The bitwise-correct implementation can significantly improve the accuracy of the simulation. Only the L1Topo items that were used in active trigger in 2016 run are shown. Persistent mismatches (blue/red areas) are mostly due to small rounding errors in the invariant mass calculation. ATL-COM-DAQ-2017-008 ATL-COM-DAQ-2017-008.png
png
Left: Fraction of events for which the L1Topo ΔηΔϕ algorithm produced a different outcome in firmware and in simulation. The allowed ranges of Δη and Δϕ are indicated, as well as the pT requirements used to select the input object used to compute these quantities. A small fraction of differences is currently expected because the firmware quantities are implemented as integers, while the ones in simulation are floating point values. ATL-COM-DAQ-2016-143

Right: Fraction of events for which the L1Topo H_{T} algorithm produced a different outcome in firmware and in simulation. The minimum required H_{T} is indicated, as well as the requirements applied to the jets used to compute H_{T}. A small fraction of differences is currently expected because the firmware quantities are implemented as integers, while the ones in simulation are floating point values. ATL-COM-DAQ-2016-143
.png
png eps
.png
png eps

L1Calo Performance plots 2015 (Run 2)

Performance Plots approved for Autumn Conferences: ATL-COM-DAQ-2015-150 (Sep 21, 2015)

Left: The trigger rate for the missing ET trigger with a threshold at 35 GeV per bunch is plotted as function of the inst. Lumi per bunch. The rates are shown for different settings with and w/o pedestal correction applied. The pedestal correction minimise pile-up effects and linearises the trigger rate.

Right: The trigger rate for the missing ET trigger with a threshold at 50 GeV per bunch is plotted as function of the inst. Lumi per bunch. The rates are shown for different settings with and w/o pedestal correction applied. The pedestal correction minimise pile-up effects and linearises the trigger rate.
.png
png pdf eps
.png
png pdf eps
Left: The figure shows the trigger rates per bunch for various em triggers in 25 and 50ns operation as function of the inst. Lumi per bunch. A linear behaviour for all items is observed as well as a good agreement for the different bunch spacing schemes. EM12 and EM15 are triggers with thresholds at 12 and 15 GeV respectively. EM20VHI has additional requirements on isolation (electromagnetic and hadronic) applied.

Right: The trigger rate for the missing ET trigger with a threshold at 35 GeV per bunch is plotted as function of the inst. Lumi per bunch. The rates are shown for different settings with and w/o pedestal correction applied. The pedestal correction minimise pile-up effects and linearises the trigger rate.
.png
png pdf eps
.png
png pdf eps
Left: The figure shows the rate per bunch of the missing ET trigger with a threshold of 35 GeV (XE35) as function of the bunch position within a bunch train. Due to the interplay of in-time and out-of-time pile-up which leads to a higher level of the pedestal an increased rate at the beginning of the bunch train is observed.

Right: The figure shows the rate per bunch of the missing ET trigger with a threshold of 35 GeV (XE35) as function of the position within a bunch train. The interplay of in-time and out-of-time pile-up leads to an increased level of the pedestal at the beginning of the bunch train. A pedestal correction algorithm implemented in firmware compensates for this effect and results in stable rates over the full bunch train.
.png
png
.png
png
The figure shows the rate per bunch of the missing ET trigger with a threshold of 35 GeV (XE35) as function of the position within a bunch train. The interplay of in-time and out-of-time pile-up leads to an increased level of the pedestal at the beginning of the bunch train. A pedestal correction algorithm implemented in firmware compensates for this effect and results in stable rates over the full bunch train.

.png
png

Left: The Figure shows the normalised coefficients of the Finite Impulse Response Filter (FIR) for the electromagnetic layer. The coefficients are shown for a matched filter which is given by the signal pulse shape assuming white noise and no correlations between the five input ADC slices. The x-axis indicates the different η-bins for which the filters are shown. The y-axis indicates the five coefficients per η-bin and the z-axis shows the normalised filter value.

Right: The Figure shows the normalised coefficients of the Finite Impulse Response Filter (FIR) for the electromagnetic layer. The coefficients are shown for an autocorrelation filter for 25ns bunch spacing. The filters are given by the signal pulse shape. They take correlations between different ADC input slices from out of time pile-up into account. The x-axis indicates the different η-bins for which the filters are shown. The y-axis indicates the five coefficients per η-bin and the z-axis shows the normalised filter value.
.png
png pdf eps
.png
png pdf eps
Left: The Figure shows the normalised coefficients of the Finite Impulse Response Filter (FIR) for the hadronic layer. The coefficients are shown for a matched filter which is given by the signal pulse shape assuming white noise and no correlations between the five input ADC slices. The x-axis indicates the different η-bins for which the filters are shown. The y-axis indicates the five coefficients per η-bin and the z-axis shows the normalised filter value.

Right: The Figure shows the normalised coefficients of the Finite Impulse Response Filter (FIR) for the hadronic layer. The coefficients are shown for an autocorrelation filter for 25ns bunch spacing. The filters are given by the signal pulse shape. They take correlations between different ADC input slices from out of time pile-up into account. The x-axis indicates the different η-bins for which the filters are shown. The y-axis indicates the five coefficients per η-bin and the z-axis shows the normalised filter value.
.png
png pdf eps
.png
png pdf eps
Left: The figure shows the efficiency that a calorimeter pulse is identified in the correct bunch crossing as function of its offline energy by the Trigger logic. The performance of a matched filter is compared to an autocorrelation filter for the electromagnetic barrel (EMB). Since the level of out of time pile-up is rather low, the filters are very similar to each other and consequently the performance is close.

Right: The figure shows the efficiency that a calorimeter pulse is identified in the correct bunch crossing as function of its offline energy by the Trigger logic. The performance of a matched filter is compared to an autocorrelation filter for the inner wheel of the electromagnetic endcap. Since the level of out of time pile-up is significant, the filters are different and consequently the performance is significantly better for autocorrelation filters.
.png
png pdf eps
.png
png pdf eps
The figure shows the efficiency that a calorimeter pulse is identified in the correct bunch crossing as function of its offline energy by the Trigger logic. The performance of a matched filter is compared to an autocorrelation filter for the forward calorimeter (FCAL). Since the level of out of time pile-up is significant, the filters are different and consequently the performance is significantly better for autocorrelation filters.

.png
png pdf eps

Monitoring Plots approved for the ATLAS report to LHCC (Jun 3, 2015)

Left: The figure shows the distribution of the transverse energy for em candidates identified within the cluster processor system of the Level-1 Calorimeter Trigger. The information is read out from the new Common Merger Module (CMX). The data were recorded during initial pp collisions in 2015 with protons colliding at centre of mass energy of √s=13TeV.

Right: The figure shows the distribution of the transverse energy for em candidates identified within the cluster processor system of the Level-1 Calorimeter Trigger which are transmitted to the Level-1 Topological Trigger. The information is read out from the new Common Merger Module (CMX). The data were recorded during initial pp collisions in 2015 with protons colliding at centre of mass energy of √s= 13TeV.
.png
png pdf eps
.png
png pdf eps

Monitoring Plots Update (Sep 21, 2015)

Left: The figure shows the distribution of the transverse energy for em candidates identified within the cluster processor system of the Level-1 Calorimeter Trigger. The information is read out from the new Common Merger Module (CMX). The data were recorded during initial pp collisions in 2015 with protons colliding at centre of mass energy of √s=13TeV.

Right: The figure shows the distribution of the transverse energy for em candidates identified within the cluster processor system of the Level-1 Calorimeter Trigger which are transmitted to the Level-1 Topological Trigger. The information is read out from the new Common Merger Module (CMX). The data were recorded during initial pp collisions in 2015 with protons colliding at centre of mass energy of √s= 13TeV.
.png
png pdf eps
.png
png pdf eps

Phase-0 Upgrade Simulation Figures

Level-1 Missing ET Trigger Rates from high luminosity simulation: ATL-COM-DAQ-2013-150 (Nov 27, 2013)

Left: The estimated Level-1 trigger rate as a function of the missing ET (MET) threshold from 14 TeV minimum bias Monte Carlo for a <μ> = 54 and a 25 ns bunch spacing. Shown are the operation scenarios with 2011 and 2012 noise cuts using matched FIR filters and two options for Run 2 with noise cuts optimised for a trigger tower occupancy of 0.5% using autocorrelation FIR filters with and without a pedestal correction (p. c.) which are possible with the upgraded Level-1 calorimeter trigger system.

Right: The estimated Level-1 trigger rate as a function of the missing ET (MET) threshold from 14 TeV minimum bias Monte Carlo for a <μ> = 81 and a 25 ns bunch spacing. Shown are the operation scenarios with 2011 and 2012 noise cuts using matched FIR filters and two options for Run 2 with noise cuts optimised for a trigger tower occupancy of 1.0% using autocorrelation FIR filters with and without a pedestal correction (p. c.) which are possible with the upgraded Level-1 calorimeter trigger system.
.png
png eps
.png
png eps

L1Calo Performance plots 2011-2013 (Run 1)

Performance of the ATLAS Level-1 Trigger: ATL-COM-DAQ-2013-016 (May 01, 2013)

Left: L1Calo trigger tower timing in ns as a function of η and φ for the electromagnetic (EM) calorimeter layer. The timing is derived by fitting the trigger tower ADC distributions using either a Gauss-Landau or Landau-Landau function, after all timing corrections were applied in hardware. Precision of this method of timing determination is estimated to be around 1 ns, also lowest step available to tune timing in L1Calo hardware (in PHOS4 chip) is 1ns. This plot shows the results using collision data from May 2012. In ideal case of perfectly timed system all Trigger Towers would give entries at zero. The plot shows that timing is within the target of +- 3ns for all Trigger Towers.

Right: The same for the hadronic (HAD) calorimeter layer.

.png
png eps
.png
png eps
Left: L1Calo trigger tower timing in ns as a function of η for the electromagnetic (EM) calorimeter layer. The timing is derived by fitting the trigger tower ADC distributions using either a Gauss-Landau or Landau-Landau function, after all timing corrections were applied in hardware. Precision of this method of timing determination is estimated to be around 1 ns, also lowest step available to tune timing in L1Calo hardware (in PHOS4 chip) is 1ns. This plot shows the results using collision data from May 2012. In ideal case of perfectly timed system all Trigger Towers would give entries at zero. The plot shows that timing is within the target of +- 3ns.

Right: The same for the hadronic (HAD) calorimeter layer.

.png
png eps

.png
png eps

Left: L1Calo timing as a function of time since start of the run for the electromagnetic (EM) calorimeter layer. The timing is an average and rms of the individual trigger tower timings which are derived using a simplified fitting method based on the ADC peak position. This plot shows results obtained offline using collision data from run 191426 (22 october 2011) compared with beam phase as measured by the Central Trigger. It is shown that during a run, timing is stable to better than 1ns level.

Right: The same for the hadronic (HAD) calorimeter layer.

.png
png eps

.png
png eps

Left: The figure above concerns the trigger known within ATLAS as L1_EM18VHI, where ‘H’ denotes that a hadronic veto of 1GeV has been applied, ‘V’ denotes that the threshold energy is variable in η and ‘I’ denotes the use of electromagnetic isolation. This plot shows the efficiency turn on curve of this trigger after various levels of electromagnetic isolation have been applied.

The ET denoted on the above figure relates to offline reconstructed electron ET.

A subset of data identified as Z→ee candidates by standard offline reconstruction was selected from around 1 fb-1 taken around the end of November and early December, 2012. The average number of interactions per bunch crossing in this data ranged from 10 to 40.

The efficiency is defined with respect to electrons from these Z candidates satisfying additional selection criteria, among others:

- have |η|< 2.5
- are required to satisfy tight offline electron identification
- are in active area of calorimeter
- the invariant mass of the tag and probe must satisfy 80 < m < 100 GeV
- are matched to L1 trigger EM object
- are matched to High Level Trigger electron object
- the tag electron must have an isolated track

The error bars on the plots are statistical in nature.

Right: The same for the trigger known within ATLAS as L1_EM25HI

.png
png eps

.png
png eps

Left: The figure above concerns the trigger known within ATLAS as L1_EM18VHI, where ‘H’ denotes that a hadronic veto of 1GeV has been applied, ‘V’ denotes that the threshold energy is variable in η and ‘I’ denotes the use of electromagnetic isolation. This plot shows the efficiency at turn on plateau as a function of pile-up after various levels of electromagnetic isolation have been applied.

A subset of data identified as Z→ee candidates by standard offline reconstruction was selected from around 1 fb-1 taken around the end of November and early December, 2012. The average number of interactions per bunch crossing in this data ranged from 10 to 40.

The electron selection criteria are the same as those used for Figure 7.

The error bars on the plots are statistical in nature.



Right: The same for the trigger known within ATLAS as L1_EM25HI.

.png
png eps

.png
png eps

The figure above investigates the triggers which, in ATLAS trigger nomenclature are notated as L1_16H, L1_EM18VH and L1_25H. Within this, the `H' in the name of these triggers denotes that they have already had a hadronic veto of ≤ 1 GeV applied and the letter `V' denotes that the threshold energy is variable in η.

This plot shows the effectiveness of a veto isolation cut on the rates of the level 1 calorimeter triggers L1_EM16H, L1_EM18VH and L1_EM25H. The x-axis shows the relative rate reduction achieved by applying the extra isolation requirements and the y-axis is the relative reduction in rate. The labels denote isolation value was used for the corresponding trigger. Efficiency values are calculated using integrals between 30 and 100 GeV

A subset of data identified as Z→ee candidates by standard offline reconstruction was selected from around 1 fb-1 taken around the end of November and early December, 2012. The average number of interactions per bunch crossing in this data ranged from 10 to 40. The cut on the energy of the probe electrons is set at 30 GeV when calculating the efficiencies for this plot.

The electron selection criteria are the same as those used for Figure 7.

The error bars are not included in this plot as they are viewed to be negligible.

.png
png eps

This plot shows the relative effectiveness of a fractional isolation cut on the rates of the level 1 calorimeter trigger L1_EM16 which is an electron trigger with a threshold of 16 GeV. The electromagnetic isolation considered here represents the total energy found in a ring of em trigger towers surrounding the area which caused the trigger.

The three data series plotted are the trigger with an isolation veto as possible in the current firmware, the trigger with a fractional isolation where the isolation allowed is a fraction of the level 1 electron energy and the trigger with both the fractional isolation and a hadronic veto of ≤ 1 GeV.

The x-axis shows the relative rate achieved by applying the extra isolation requirements and the y-axis is the relative efficiency. The labels denote which fraction (F) or isolation (I) was used for the corresponding trigger. Efficiency values are calculated using integrals between 25 and 100 GeV.

The electron selection criteria are the same as those used for Figure 7.

The statistical errors for the efficiencies are not shown as they are small compared to the points and systematic errors have not been considered at this point.

.png
png eps

Left: This plot shows L1Calo receiver gains applied to signals in electromagnetic layer, as used at the end of 2012/13 data taking period.

Receiver gains are where L1Calo energy calibration is applied, ensuring correct energy scale on trigger tower level.

The gains are not uniform, because cables, carrying analog input signals from ATLAS front-end to L1Calo have different length and attenuation. Another source of non-uniformities are differences in electronics response, corrections for dead or noisy calorimeter cells and corrections for reduced high voltage.

Right: The same for L1Calo receiver gains applied to signals in hadronic LAr calorimeter.

.png
png eps

.png
png eps

This plot shows L1Calo receiver gains applied to signals coming from Tile calorimeter, as used at the end of 2012/13 data taking period.

Receiver gains are where L1Calo energy calibration is applied, ensuring correct energy scale on trigger tower level.

The gains are not uniform, because cables, carrying analog input signals from ATLAS front-end to L1Calo have different length and attenuation. Another source of non-uniformities are differences in electronics response and corrections for reduced response in drawers in emergency mode.

.png
png eps

This plot shows relative change in L1Calo receiver gains, used by L1Calo to compensate for reduction of high voltage in Liquid Argon Presampler. The change happened on 28/9/2012 when HV was reduced to 1200 V. New receiver gains were calculated with offline script based on HV corrections for individual LAr cells and EM shower profile determined from analysis of collision data. Gains were updated for most of EM barrel, although for some areas the update was not necessary, as these were on reduced HV already.

.png
png eps

Left: Fractional difference between L1Calo transverse energy and offline transverse energy as a function of the offline transverse energy. The L1Calo energy is calculated using two different methods; the energy based on the ADC peak sample and the energy based on the result of the look-up-table (LUT). This plot shows the distributions for the Liquid Argon electromagnetic barrel (EMB, -1.5< η < 1.5) calorimeter using 2012 collision data, recorded on Oct. 21st. EMB-A and EMB-C represent different sides of the barrel, in terms of the pseudorapidity (A: η>0, C:η<0). The errors on the y-axis represent statistical errors, while the errors on the x-axis show the bin width. For most calorimeter partitions statistical errors are negligible.

Right: The same quantity for the Tile hadronic calorimeter (TILE, -1.5 < η < 1.5) using 2012 collision data, recorded on Oct. 21st. TILE-A and TILE-C represent different sides of the barrel, in terms of the pseudorapidity (A: η>0, C:η<0).

.png
png eps

.png
png eps

Left: Fractional difference between L1Calo transverse energy and offline transverse energy as a function of the offline transverse energy. The L1Calo energy is calculated using the energy based on the ADC peak sample. This plot shows the distributions for all electromagnetic calorimeter partitions using 2012 collision data, recorded on Oct. 21st. The partition names represent different parts of the detector in terms of the pseudorapidity (EMB/EMEC2/EMEC1/FCAL1: |η|< 1.5 /<1.8/<3.2/<4.9). The first bin for the FCAL1 (ET < 7 GeV) is subject to large pile-up effects and is therefore not shown. The errors on the y-axis represent statistical errors, while the errors on the x-axis represent the bin width. For most calorimeter partitions statistical errors are negligible.

Right: The same quantity for all hadronic calorimeter partitions. The partition names represent different parts of the detector in terms of the pseudorapidity (TILE/HEC/FCAL23: |η| < 1.5/<3.2/<4.9). There was not enough data at high ET for the very forward regions (FCAL23), which is why those bins are empty.

.png
png eps

.png
png eps

Left: Ratio between offline transverse energy and L1Calo transverse energy as a function of η. The L1Calo energy is calculated using the energy based on the ADC peak sample. This plot shows the distribution for electromagnetic calorimeter layer using 2012 collision data, recorded on Oct. 21st. The errors on the y-axis represent statistical errors, while the errors on the x-axis represent the bin width. For most calorimeter partitions statistical errors are negligible.

Righ: The same quantity for hadronic calorimeter layer.

.png
png eps

.png
png eps

L1Calo Trigger rates 2011-2012

Performance of the ATLAS Level-1 Trigger: ATL-COM-DAQ-2012-033 (May 02, 2012)

Level-1 Trigger cross-sections (rate/luminosity) for a selection of L1Calo-based trigger items. The left side of the figure corresponds to measurements from two 7TeV runs with 2011 nominal per-bunch luminosities, and colliding bunches delivered in bunch trains with 50ns spacing. The right side of the figure corresponds to a special high-luminosity 7TeV run with no bunch trains. The middle of the figure corresponds to an 8TeV run with 2012 nominal per-bunch luminosities and 50ns bunch trains. The falls in rate for XE50 and FJ75 triggers between 2011 and 2012 runs are due to trigger noise-cut increases in the forward regions of L1Calo. All other rate changes (increases) are due to the increased centre-of-mass energy. EM16 (EM30) is an electron-photon trigger with a threshold at 16 (30) GeV.

EM16VH is an electron-photon trigger with an hadronic layer energy veto and varied thresholds across the calorimeter, with typically 16 GeV thresholds. TAU15 is an hadronically-decaying tau trigger with threshold at 15 GeV. XE50 is a trigger for missing ET above 50 GeV at the EM scale. XE50_BGRP7 is an XE50 trigger with a veto on the first 3 bunches of a bunch train. J75 is a trigger for a central jet (|η|<3.2) with ET above 75 GeV. FJ75 is a trigger for a jet in the forward region (|η|>3.2) with ET above 75 GeV. 4J10 is a trigger for four central jets with ET above 10 GeV.

.png
png eps
png (without fixed-rate lines) eps (without fixed-rate lines)

L1Calo Forward Noise Cut Studies 2011/2012

Performance of the ATLAS Level-1 Trigger: ATL-COM-DAQ-2012-033 (May 02, 2012)

Left: Distribution of L1Calo Preprocessor ADC counts for four different regions of the EM FCAL calorimeter. The four bins represent divisions in |η| of the trigger towers, nominally: 3.1-3.2 (Bin 1), 3.2-3.5 (Bin 2), 3.5-4.2 (Bin 3), 4.2-4.9 (Bin 4). Zero-bias events from a single run were used for these distributions.

Right: Standard deviation (from RMS of distribution) of the L1Calo Preprocessor ADC distributions of four regions of the EM FCAL calorimeter, measured over a range of luminosities that have been quantified in terms of the interactions per bunch crossing. The four bins represent divisions in |η| of the trigger towers, nominally: 3.1-3.2 (Bin 1), 3.2-3.5 (Bin 2), 3.5-4.2 (Bin 3), 4.2-4.9 (Bin 4). Zero-bias events from a single run were used for these distributions.
.png
png eps
.png
png eps
Left: Distribution of L1Calo Preprocessor ADC counts for two different regions of the Hadronic FCAL2 calorimeter. The two bins represent divisions in |η| of the trigger towers, nominally: 3.1-3.5 (Bin 1), 3.5-4.9 (Bin 2). Zero-bias events from a single run were used for these distributions.

Right: Standard deviations (from RMS of distribution) of the L1Calo Preprocessor ADC distributions of two regions of the Hadronic FCAL2 calorimeter, measured over a range of luminosities that have been quantified in terms of the interactions per bunch crossing. The two bins represent divisions in |η| of the trigger towers, nominally: 3.1-3.5 (Bin 1), 3.5-4.9 (Bin 2). Zero-bias events from a single run were used for these distributions.
.png
png eps
.png
png eps
Left: Distribution of L1Calo Preprocessor ADC counts for two different regions of the Hadronic FCAL3 calorimeter. The two bins represent divisions in |η| of the trigger towers, nominally: 3.1-3.5 (Bin 1), 3.5-4.9 (Bin 2). Zero-bias events from a single run were used for these distributions.

Right: Standard deviations (from RMS of distribution) of the L1Calo Preprocessor ADC distributions of two regions of the Hadronic FCAL3 calorimeter, measured over a range of luminosities that have been quantified in terms of the interactions per bunch crossing. The two bins represent divisions in |η| of the trigger towers, nominally: 3.1-3.5 (Bin 1), 3.5-4.9 (Bin 2). Zero-bias events from a single run were used for these distributions.
.png
png eps
.png
png eps
Left: Distribution of L1Calo Preprocessor ADC counts for four different regions of the EM EndCap Inner Wheel calorimeter. The four bins represent divisions in |η| of the trigger towers, nominally: 2.5-2.7 (Bin 1), 2.7-2.9 (Bin 2), 2.9-3.1 (Bin 3), 3.1-3.2 (Bin 4). Zero-bias events from a single run were used for these distributions.

Right: Standard deviations (from RMS of distribution) of the L1Calo Preprocessor ADC distributions of four regions of the EM EndCap Inner Wheel calorimeter, measured over a range of luminosities that have been quantified in terms of the interactions per bunch crossing. The four bins represent divisions in |η| of the trigger towers, nominally: 2.5-2.7 (Bin 1), 2.7-2.9 (Bin 2), 2.9-3.1 (Bin 3), 3.1-3.2(Bin 4). Zero-bias events from a single run were used for these distributions.
.png
png eps
.png
png eps
L1_XE50 (Missing ET Trigger) efficiency as a function of the offline topological cluster-based missing ET, for a sample of candidate W->e nu events (single electron with ET above 25 GeV, passing tight identification and other quality requirements, with the candidate W transverse mass greater than 40 GeV). Four different choices of trigger tower noise cuts were simulated offline, one with Forward Calorimeter (FCAL) noise cuts optimized to conditions with an average of 15 interactions per crossing, one with FCAL noise cuts optimized to 20 average interactions per crossing, one with both FCAL and Electromagnetic EndCap Inner Wheel (EMEC-IW) noise cuts optimized for 20 average interactions per crossing, and one with FCAL and EMEC-IW noise cuts optimized to 25 interactions per crossing.

Data was taken from a single 2012 run, which had a peak luminosity of 23.1 average collisions per filled bunch crossing.

.png
png eps

Predicted Level-1 Missing Energy rates with pile-up noise suppression: ATL-COM-DAQ-2011-152 (December 6, 2011)

FCAL/EMEC inner noise cuts and XE trigger
Level-1 Missing Et (MET) rates as a function of threshold for several pile-up noise cut scenarios. The rates are estimated by applying noise cuts to ZeroBias events in run 191426 at a luminosity around 3.2x1033 and mu of 15. The 2011 configuration corresponds to noise cuts of approximately 1 GeV in all trigger towers. The loose forward noise cut applies cuts of 6.5, 5.5 and 2.5 GeV in the first FCAL layer and 4.5 in the second layer at |η| > 3.5. The tighter noise cuts raise these by 1 GeV, and also raise the noise cuts in all other towers beyond |η| = 2.5 by 0.5 GeV. The final case removes FCAL entirely from the Missing Et calculation. At this luminosity, the bulk of the fake MET rate reduction is achieved with the loose cuts.
.png
png eps

L1Calo Calibration Figures 2011

Calibration and Performance of the ATLAS Level-1 Calorimeter Trigger: ATL-COM-DAQ-2011-037 (June 1, 2011)

Timing monitoring 2010/11
Mean L1Calo timing as function of date for the electromagnetic (EM) and hadronic (Had) calorimeter partitions. The mean timing is an average of the individual trigger tower timings which are derived using a simplified fitting method based on the ADC peak position. The vertical lines indicate adjustments in the global CTP clock phase which synchronize the clock to the LHC radio-frequency system.
.png
png eps
.png
png eps
Timing status March 2011
L1Calo trigger tower timing in ns as function of eta and phi for the electromagnetic (EM) and hadronic (HAD) calorimeter layer. The timing is derived by fitting the trigger tower ADC distributions using either a Gauss-Landau or Landau-Landau function. This plot shows the results using collision data from the initial 2011 running period. White bins have no measurement due to lack of statistics.
.png
png eps
.png
png eps
Timing status April 2011
L1Calo trigger tower timing in ns as function of eta and phi for the electromagnetic (EM) and hadronic (HAD) calorimeter layer. The timing is derived by fitting the trigger tower ADC distributions using either a Gauss-Landau or Landau-Landau function. This plot shows the results using collision data after applying corrections to the L1Calo timing delays derived from figure 3 or 5, respectively. White bins have no measurement due to lack of statistics.
.png
png eps
.png
png eps
Energy correlation (Beginning of 2011)
L1Calo trigger tower transverse energy versus offline transverse energy. The offline transverse energy is derived by summing the individual calorimeter cells associated to a tower. These plots show the results for the electromagnetic (EM) and hadronic (HAD) calorimeter using 2011 collisions data.
.png
png eps
.png
png eps
Energy resolution (2010)
Fractional difference between L1Calo transverse energy and offline transverse energy as a function of the offline transverse energy. The L1Calo energy is calculated using two different methods; the energy based on the ADC peak sample and the energy based on the result of the look-up-table (LUT). These plots show the distributions for the electromagnetic barrel (EMB) and the Tile hadronic calorimeter using 2010 collision data.
.png
png eps
.png
png eps
Energy resolution (Early 2011)
Fractional difference between L1Calo transverse energy and offline transverse energy as a function of the offline transverse energy. The L1Calo energy is calculated using two different methods; the energy based on the ADC peak sample and the energy based on the result of the look-up-table (LUT). These plots show the distributions for the electromagnetic barrel (EMB) and the Tile hadronic calorimeter using 2011 collision data which include improvements in the LUT calculation.
.png
png eps
.png
png eps
Correlation of FIR output and ADC peak sample
The output of the finite-impulse-response (FIR) filter before drop bit truncation as a function of the peak ADC sample for an example trigger tower from the electromagnetic (EM) layer. A linear fit is applied to distribution for peak ADC values above 50, well above the pedestal value of about 32 counts. The fitted gradient is used to derive look-up-table (LUT) slopes which determine the energy calibration. The plot shows the results from the analysis of 2010 collision data.
.png
png eps
LUT calibration (2010)
The fitted gradients as a function of eta and phi for the electromagnetic (EM) and hadronic (Had.) layer. The results are derived from linear fits to the distributions of the finite-impulse-response (FIR) filter output as a function of the peak ADC sample as shown in figure 13. This plot shows the result from the analysis of 2010 collision data.
.png
png eps
.png
png eps
Normalised pulse shape (2010)
The pedestal subtracted and normalized ADC pulse shape for an example L1Calo trigger tower as derived from the analysis of 2010 collision data.
.png
png eps
FIR calibration (2010)
The sum (S_1+S_3) as a function of eta and phi for the electromagnetic (EM) and hadronic (Had.) calorimeter layer. The value S i is the normalized pulse height of the i-th ADC sample as illustrated in figure 16. This plot shows the result from the analysis of 2010 collision data.
.png
png eps
.png
png eps

L1Calo Calibration Figures 2010

ATLAS Level-1 Calorimeter Trigger: Timing Calibration with 2009 LHC Beam Splashes: ATL-DAQ-PUB-2010-001 (April 30, 2010)

Figure 1: Figure 1(a) is a standard pulse as it is read out of the L1Calo system and Figure 1(b) is a reconstructed pulse with nanosecond time resolution which is derived from special pulser runs as described in the text. Both signals are fit with the hybrid Landau/Gaussian fit function described by Equation 1. The signals were taken from a Liquid Argon calibration run. ATL-DAQ-PUB-2010-001-fig_01a.png
png eps
ATL-DAQ-PUB-2010-001-fig_01b.png
png eps
Figure 2: This is an eta-phi plot of the peak time location with ns precision plotted on the z-axis. The peak times (t0) are measured by fitting each trigger tower signal with a Landau/Gaussian hybrid function. The timing reference was taken as 175 ns from Figure 1(a). The electromagnetic layer is shown in 2(a) with beam-1 approaching in the −h direction using event number 2166. The hadronic layer is shown in 2(b) with beam-2 approaching in the +h direction using event number 2666. Both events are taken from Run 140370. ATL-DAQ-PUB-2010-001-fig_02a.png
png eps
ATL-DAQ-PUB-2010-001-fig_02b.png
png eps
Figure 3: An eta-projection of the peak time location distribution in Figure 2 is shown. The electromagnetic layer is shown in 3(a) with beam-1 approaching in the −eta direction using event number 2166. The hadronic layer is shown in 3(b) with beam-2 approaching in the +eta direction using event number 2666. Both events are taken from Run 140370. ATL-DAQ-PUB-2010-001-fig_03a.png
png eps
ATL-DAQ-PUB-2010-001-fig_03b.png
png eps
Figure 5: The approximate time of flight from collision vertex to detector layer as a function of eta. The electromagnetic layer is shown in 5(a) and the hadronic layer in 5(b). ATL-DAQ-PUB-2010-001-fig_05a.png
png eps
ATL-DAQ-PUB-2010-001-fig_05b.png
png eps
Figure 6: The time of flight from collimator to detector layer as a function of eta is shown using eta = 0 as a reference. The time of flight from the interaction point to the detector, shown in Figure 5, is subtracted to get the total time of flight correction seen in Figure 7. The electromagnetic layer is shown in 6(a). The hadronic layer is shown in 6(b). The beam-1 (−eta) trajectory is used here with reflection across the eta = 0 axis representing the beam-2 trajectory. ATL-DAQ-PUB-2010-001-fig_06a.png
png eps
ATL-DAQ-PUB-2010-001-fig_06b.png
png eps
Figure 7: This is the total time of flight correction as a function of eta. The electromagnetic layer is shown in 7(a). The hadronic layer is shown in 7(b). The beam-1 (−eta) trajectory is used here with reflection across the eta = 0 axis representing the beam-2 trajectory. ATL-DAQ-PUB-2010-001-fig_07a.png
png eps
ATL-DAQ-PUB-2010-001-fig_07b.png
png eps
Figure 8: The corrected peak time location in nanoseconds for both calorimeter layers. The electromagnetic layer is shown in 8(a) with beam-1 (−eta trajectory) using event number 2166. The hadronic layer is shown in 8(b) with beam-2 (+eta trajectory) using event number 2666. Both events taken from Run 140370. ATL-DAQ-PUB-2010-001-fig_08a.png
png eps
ATL-DAQ-PUB-2010-001-fig_08b.png
png eps
Figure 9: The mean of the eta bins in Figure 8. The distributions would be flat for perfect timing, however, partition dependent offsets must be corrected. The electromagnetic layer is shown in 9(a) with beam 1 approaching in the −eta direction using event number 2166. The hadronic layer is shown in 9(b) with beam 2 approaching in the +eta direction using event number 2666. Both events taken from Run 140370. ATL-DAQ-PUB-2010-001-fig_09a.png
png eps
ATL-DAQ-PUB-2010-001-fig_09b.png
png eps
Figure 10: The peak position (t0), determined using Equation 1, as a function of the ATLAS event number. Figure 10(a) shows a non-uniform response to beam-1 and beam-2 events (PPM channel located in hadronic end cap), which was seen in a small number of channels. Figure 10(b) shows a typical TT with the expected uniform response to beam-1 and beam-2 splash events (PPM channel located in electromagnetic barrel). ATL-DAQ-PUB-2010-001-fig_10a.png
png eps
ATL-DAQ-PUB-2010-001-fig_10b.png
png eps
Figure 11: The mean correction to peak time location in nanoseconds for both calorimeter layers. The electromagnetic layer is shown in 11(a). The hadronic layer is shown in 11(b). Data taken from splash events in Run 140370. ATL-DAQ-PUB-2010-001-fig_11a.png
png eps
ATL-DAQ-PUB-2010-001-fig_11b.png
png eps
Figure 12: The final corrected timing delays for each TT in nanoseconds for both calorimeter layers. The electromagnetic layer is shown in 12(a). The hadronic layer is shown in 12(b). ATL-DAQ-PUB-2010-001-fig_12a.png
png eps
ATL-DAQ-PUB-2010-001-fig_12b.png
png eps

L1Calo calibration figures not assigned to a CDS note

Energy ramp for one particular Trigger Tower from the Tile system
Five different energies have been pulsed using the Tile charge injection system. The transverse energy measured in the Tile calorimeter is plotted vs. the energy measured by L1Calo. A linear fit is overlayed with the slope of the line corresponding to the calibration constant derived by this method.

png eps
Energy ramp for one particular Trigger Tower from the LAr system
Six different energies have been pulsed using the LAr pulser system. The transverse energy measured in the LAr calorimeter is plotted vs. the energy measured by L1Calo. A linear fit is overlayed with the slope of the line corresponding to the calibration constant derived by this method.

png eps
Tile energy correlation plot
Energy correlation plot from 7 TeV data where the transverse energy measured in the Tile Calorimeter is shown vs. the transverse energy measured by L1Calo. The transverse energy of all cells which correspond to a Trigger Tower is summed up and compared to the corresponding L1 Trigger Tower. The plot shows a very good correlation with only a very few outliers.

png eps
LAr energy correlation plot
Energy correlation plot from 7 TeV data where the transverse energy measured in the LAr Calorimeter is shown vs. the transverse energy measured by L1Calo. The transverse energy of all cells which correspond to a Trigger Tower is summed up and compared to the corresponding L1 Trigger Tower. The plot shows a very good correlation.

png eps
Correlation between peak ADC input and LUT output
L1Calo digitises trigger tower signals with a scale of 250 MeV per ADC. The digital pulses are passed through a filter to improve energy resolution, noise rejection and bunch crossing identification. The filter output is then passed into a look-up table (LUT) which performs pedestal subtraction, noise cuts, and the final ET calibration. The output from the LUT has a scale of 1 GeV/count. The initial LUT values were generated based on measurements of calibration pulses.
The correlation between peak ADC input and LUT output for a single trigger tower is plotted. The correlation between peak ADC input and the LUT output for a single trigger tower in collision data is plotted. The expected gradient for a perfectly calibrated tower is 1/4 (250 MeV / 1 GeV). A straight line was fitted to the data and a gradient of 0.24 LUT/ADC was extracted. This shows that calibration and collision pulse shapes are comparable, and the initial calibration is already close to the final optimum LUT values required for collisions.

png eps
LUT calibration
L1Calo digitises trigger tower signals with a scale of 250 MeV per ADC. The digital pulses are passed through a filter to improve energy resolution, noise rejection and bunch crossing identification. The filter output is then passed into a look-up table (LUT) which performs pedestal subtraction, noise cuts, and the final ET calibration. The output from the LUT has a scale of 1 GeV/count. The initial LUT values were generated based on measurements of calibration pulses.
Straight lines were fitted to ADC peak vs LUT distributions for each trigger tower and the gradients extracted. The expected gradient for a perfectly calibrated tower is 1/4 (250 MeV / 1 GeV). The distribution of fit gradients for towers in the LAr Barrel A-side show that the initial LUT calibration worked well, as most towers are already close to the optimum value. Future calibration will be based on offline reconstructed physics objects.

png eps


Major updates:
-- MartinWessels - 24-Jun-2011 -- JoergStelzer - 13-Jun-2011

Responsible: JoergStelzer
Subject: public

Topic attachments
I Attachment History Action Size Date Who Comment
Unknown file formateps ATL-COM-DAQ-2011-037-fig01.eps r1 manage 12.7 K 2011-06-21 - 14:08 MartinWessels  
PNGpng ATL-COM-DAQ-2011-037-fig01.png r1 manage 31.2 K 2011-06-21 - 14:09 MartinWessels  
Unknown file formateps ATL-COM-DAQ-2011-037-fig02.eps r1 manage 15.4 K 2011-06-21 - 17:14 MartinWessels  
PNGpng ATL-COM-DAQ-2011-037-fig02.png r1 manage 33.0 K 2011-06-21 - 17:14 MartinWessels  
Unknown file formateps ATL-COM-DAQ-2011-037-fig03.eps r1 manage 121.0 K 2011-06-21 - 17:14 MartinWessels  
PNGpng ATL-COM-DAQ-2011-037-fig03.png r1 manage 50.0 K 2011-06-21 - 17:15 MartinWessels  
Unknown file formateps ATL-COM-DAQ-2011-037-fig04.eps r1 manage 120.2 K 2011-06-21 - 17:15 MartinWessels  
PNGpng ATL-COM-DAQ-2011-037-fig04.png r1 manage 48.8 K 2011-06-21 - 17:15 MartinWessels  
Unknown file formateps ATL-COM-DAQ-2011-037-fig05.eps r1 manage 110.7 K 2011-06-21 - 17:15 MartinWessels  
PNGpng ATL-COM-DAQ-2011-037-fig05.png r1 manage 46.5 K 2011-06-21 - 17:15 MartinWessels  
Unknown file formateps ATL-COM-DAQ-2011-037-fig06.eps r1 manage 111.9 K 2011-06-21 - 17:16 MartinWessels  
PNGpng ATL-COM-DAQ-2011-037-fig06.png r1 manage 46.9 K 2011-06-21 - 17:16 MartinWessels  
Unknown file formateps ATL-COM-DAQ-2011-037-fig07.eps r1 manage 21.4 K 2011-06-21 - 17:16 MartinWessels  
PNGpng ATL-COM-DAQ-2011-037-fig07.png r1 manage 23.7 K 2011-06-21 - 17:16 MartinWessels  
Unknown file formateps ATL-COM-DAQ-2011-037-fig08.eps r1 manage 13.8 K 2011-06-21 - 17:17 MartinWessels  
PNGpng ATL-COM-DAQ-2011-037-fig08.png r1 manage 20.8 K 2011-06-21 - 17:18 MartinWessels  
Unknown file formateps ATL-COM-DAQ-2011-037-fig09.eps r1 manage 13.5 K 2011-06-21 - 17:18 MartinWessels  
PNGpng ATL-COM-DAQ-2011-037-fig09.png r1 manage 28.1 K 2011-06-21 - 17:19 MartinWessels  
Unknown file formateps ATL-COM-DAQ-2011-037-fig10.eps r1 manage 13.6 K 2011-06-21 - 17:20 MartinWessels  
PNGpng ATL-COM-DAQ-2011-037-fig10.png r1 manage 28.5 K 2011-06-21 - 17:20 MartinWessels  
Unknown file formateps ATL-COM-DAQ-2011-037-fig11.eps r1 manage 13.2 K 2011-06-21 - 17:21 MartinWessels  
PNGpng ATL-COM-DAQ-2011-037-fig11.png r1 manage 27.4 K 2011-06-21 - 17:21 MartinWessels  
Unknown file formateps ATL-COM-DAQ-2011-037-fig12.eps r1 manage 14.5 K 2011-06-21 - 17:21 MartinWessels  
PNGpng ATL-COM-DAQ-2011-037-fig12.png r1 manage 27.4 K 2011-06-21 - 17:21 MartinWessels  
Unknown file formateps ATL-COM-DAQ-2011-037-fig13.eps r1 manage 27.6 K 2011-06-21 - 17:22 MartinWessels  
PNGpng ATL-COM-DAQ-2011-037-fig13.png r1 manage 27.1 K 2011-06-21 - 17:22 MartinWessels  
Unknown file formateps ATL-COM-DAQ-2011-037-fig14.eps r1 manage 106.1 K 2011-06-21 - 17:22 MartinWessels  
PNGpng ATL-COM-DAQ-2011-037-fig14.png r1 manage 37.5 K 2011-06-21 - 17:22 MartinWessels  
Unknown file formateps ATL-COM-DAQ-2011-037-fig15.eps r1 manage 95.3 K 2011-06-21 - 17:23 MartinWessels  
PNGpng ATL-COM-DAQ-2011-037-fig15.png r1 manage 40.6 K 2011-06-21 - 17:23 MartinWessels  
Unknown file formateps ATL-COM-DAQ-2011-037-fig16.eps r1 manage 6.0 K 2011-06-21 - 17:23 MartinWessels  
PNGpng ATL-COM-DAQ-2011-037-fig16.png r1 manage 12.9 K 2011-06-21 - 17:23 MartinWessels  
Unknown file formateps ATL-COM-DAQ-2011-037-fig17.eps r1 manage 111.7 K 2011-06-21 - 17:24 MartinWessels  
PNGpng ATL-COM-DAQ-2011-037-fig17.png r1 manage 41.9 K 2011-06-21 - 17:24 MartinWessels  
Unknown file formateps ATL-COM-DAQ-2011-037-fig18.eps r1 manage 107.9 K 2011-06-21 - 17:25 MartinWessels  
PNGpng ATL-COM-DAQ-2011-037-fig18.png r1 manage 43.3 K 2011-06-21 - 17:25 MartinWessels  
Unknown file formateps ATL-COM-DAQ-2011-152-fig01.eps r1 manage 17.4 K 2011-12-12 - 12:46 SteveHillier MET/FCAL eps plots
PNGpng ATL-COM-DAQ-2011-152-fig01.png r1 manage 36.8 K 2011-12-12 - 12:46 SteveHillier MET/FCAL png plot
Unknown file formateps ATL-COM-DAQ-2012-033-fig01.eps r1 manage 24.2 K 2012-05-14 - 17:07 WillButtinger  
PNGpng ATL-COM-DAQ-2012-033-fig01.png r1 manage 21.1 K 2012-05-14 - 17:07 WillButtinger  
Unknown file formateps ATL-COM-DAQ-2012-033-fig02.eps r1 manage 13.8 K 2012-05-14 - 17:07 WillButtinger  
PNGpng ATL-COM-DAQ-2012-033-fig02.png r1 manage 17.9 K 2012-05-14 - 17:07 WillButtinger  
Unknown file formateps ATL-COM-DAQ-2012-033-fig03.eps r1 manage 18.0 K 2012-05-14 - 17:07 WillButtinger  
PNGpng ATL-COM-DAQ-2012-033-fig03.png r1 manage 18.1 K 2012-05-14 - 17:07 WillButtinger  
Unknown file formateps ATL-COM-DAQ-2012-033-fig04.eps r1 manage 11.6 K 2012-05-14 - 17:07 WillButtinger  
PNGpng ATL-COM-DAQ-2012-033-fig04.png r1 manage 16.9 K 2012-05-14 - 17:07 WillButtinger  
Unknown file formateps ATL-COM-DAQ-2012-033-fig05.eps r1 manage 15.8 K 2012-05-14 - 17:07 WillButtinger  
PNGpng ATL-COM-DAQ-2012-033-fig05.png r1 manage 17.1 K 2012-05-14 - 17:07 WillButtinger  
Unknown file formateps ATL-COM-DAQ-2012-033-fig06.eps r1 manage 11.1 K 2012-05-14 - 17:09 WillButtinger  
PNGpng ATL-COM-DAQ-2012-033-fig06.png r1 manage 16.5 K 2012-05-14 - 17:09 WillButtinger  
Unknown file formateps ATL-COM-DAQ-2012-033-fig07.eps r1 manage 26.1 K 2012-05-14 - 17:09 WillButtinger  
PNGpng ATL-COM-DAQ-2012-033-fig07.png r1 manage 22.1 K 2012-05-14 - 17:09 WillButtinger  
Unknown file formateps ATL-COM-DAQ-2012-033-fig08.eps r1 manage 13.5 K 2012-05-14 - 17:09 WillButtinger  
PNGpng ATL-COM-DAQ-2012-033-fig08.png r1 manage 18.6 K 2012-05-14 - 17:09 WillButtinger  
Unknown file formateps ATL-COM-DAQ-2012-033-fig11.eps r1 manage 20.3 K 2012-05-14 - 17:09 WillButtinger  
PNGpng ATL-COM-DAQ-2012-033-fig11.png r1 manage 17.5 K 2012-05-14 - 17:09 WillButtinger  
Unknown file formateps ATL-COM-DAQ-2012-033-fig13a.eps r1 manage 54.2 K 2012-05-14 - 17:09 WillButtinger  
PNGpng ATL-COM-DAQ-2012-033-fig13a.png r1 manage 22.7 K 2012-05-14 - 17:09 WillButtinger  
Unknown file formateps ATL-COM-DAQ-2012-033-fig13b.eps r1 manage 47.9 K 2012-05-14 - 17:10 WillButtinger  
PNGpng ATL-COM-DAQ-2012-033-fig13b.png r1 manage 18.7 K 2012-05-14 - 17:10 WillButtinger  
Unknown file formateps ATL-COM-DAQ-2013-016-fig1.eps r1 manage 124.4 K 2013-05-14 - 17:54 JurajBracinik  
PNGpng ATL-COM-DAQ-2013-016-fig1.png r1 manage 20.3 K 2013-05-14 - 17:54 JurajBracinik  
Unknown file formateps ATL-COM-DAQ-2013-016-fig2.eps r1 manage 120.4 K 2013-05-14 - 18:20 JurajBracinik  
PNGpng ATL-COM-DAQ-2013-016-fig2.png r1 manage 20.6 K 2013-05-14 - 18:20 JurajBracinik  
Unknown file formateps ATL-COM-DAQ-2013-150-fig1.eps r1 manage 11.6 K 2014-06-30 - 16:53 AndrewDaniells  
PNGpng ATL-COM-DAQ-2013-150-fig1.png r1 manage 22.8 K 2014-06-30 - 16:53 AndrewDaniells  
Unknown file formateps ATL-COM-DAQ-2013-150-fig2.eps r1 manage 11.9 K 2014-06-30 - 16:53 AndrewDaniells  
PNGpng ATL-COM-DAQ-2013-150-fig2.png r1 manage 22.7 K 2014-06-30 - 16:53 AndrewDaniells  
Unknown file formateps ATL-COM-DAQ-2016-143-fig1.eps r1 manage 20.7 K 2016-09-20 - 14:21 DavideGerbaudo L1Topo plots for ATL-COM-DAQ-2016-143
PNGpng ATL-COM-DAQ-2016-143-fig1.png r1 manage 20.1 K 2016-09-20 - 14:21 DavideGerbaudo L1Topo plots for ATL-COM-DAQ-2016-143
Unknown file formateps ATL-COM-DAQ-2016-143-fig2.eps r1 manage 15.0 K 2016-09-20 - 14:21 DavideGerbaudo L1Topo plots for ATL-COM-DAQ-2016-143
PNGpng ATL-COM-DAQ-2016-143-fig2.png r1 manage 17.3 K 2016-09-20 - 14:21 DavideGerbaudo L1Topo plots for ATL-COM-DAQ-2016-143
PNGpng ATL-COM-DAQ-2017-008.png r1 manage 84.9 K 2017-03-30 - 13:19 DavideGerbaudo L1Topo bitwise comparison
PDFpdf ATL-COM-DAQ-2017-064_l1calo_pedestal_correction.pdf r1 manage 47.6 K 2017-07-18 - 17:42 IvanaHristova  
PNGpng ATL-COM-DAQ-2017-064_l1calo_pedestal_correction.png r1 manage 8.4 K 2017-07-18 - 17:42 IvanaHristova  
PDFpdf ATL-COM-DAQ-2017-064_l1calo_pedestal_shift.pdf r1 manage 42.5 K 2017-07-18 - 17:42 IvanaHristova  
PNGpng ATL-COM-DAQ-2017-064_l1calo_pedestal_shift.png r1 manage 7.6 K 2017-07-18 - 17:42 IvanaHristova  
PDFpdf ATL-COM-DAQ-2018-004-fig01.pdf r1 manage 22.3 K 2018-01-30 - 09:51 MartinWessels Figures of ATL-COM-DAQ-2018-004
PNGpng ATL-COM-DAQ-2018-004-fig01.png r1 manage 23.9 K 2018-01-30 - 09:51 MartinWessels Figures of ATL-COM-DAQ-2018-004
PDFpdf ATL-COM-DAQ-2018-004-fig02.pdf r1 manage 24.0 K 2018-01-30 - 09:51 MartinWessels Figures of ATL-COM-DAQ-2018-004
PNGpng ATL-COM-DAQ-2018-004-fig02.png r1 manage 29.2 K 2018-01-30 - 09:51 MartinWessels Figures of ATL-COM-DAQ-2018-004
PDFpdf ATL-COM-DAQ-2018-004-fig03.pdf r1 manage 21.6 K 2018-01-30 - 09:51 MartinWessels Figures of ATL-COM-DAQ-2018-004
PNGpng ATL-COM-DAQ-2018-004-fig03.png r1 manage 26.0 K 2018-01-30 - 09:51 MartinWessels Figures of ATL-COM-DAQ-2018-004
PDFpdf ATL-COM-DAQ-2018-004-fig04.pdf r1 manage 22.3 K 2018-01-30 - 09:51 MartinWessels Figures of ATL-COM-DAQ-2018-004
PNGpng ATL-COM-DAQ-2018-004-fig04.png r1 manage 24.9 K 2018-01-30 - 09:51 MartinWessels Figures of ATL-COM-DAQ-2018-004
PDFpdf ATL-COM-DAQ-2018-004-fig05.pdf r1 manage 24.2 K 2018-01-30 - 09:51 MartinWessels Figures of ATL-COM-DAQ-2018-004
PNGpng ATL-COM-DAQ-2018-004-fig05.png r1 manage 29.5 K 2018-01-30 - 09:51 MartinWessels Figures of ATL-COM-DAQ-2018-004
PDFpdf ATL-COM-DAQ-2018-004-fig06.pdf r1 manage 23.8 K 2018-01-30 - 09:52 MartinWessels Figures of ATL-COM-DAQ-2018-004
PNGpng ATL-COM-DAQ-2018-004-fig06.png r1 manage 28.0 K 2018-01-30 - 09:52 MartinWessels Figures of ATL-COM-DAQ-2018-004
Unknown file formateps ATL-COM-DAQ-2018-170_plot_1.eps r1 manage 23.3 K 2018-11-22 - 10:06 IvanaHristova  
PDFpdf ATL-COM-DAQ-2018-170_plot_1.pdf r1 manage 16.6 K 2018-11-22 - 10:06 IvanaHristova  
PNGpng ATL-COM-DAQ-2018-170_plot_1.png r1 manage 19.2 K 2018-11-22 - 10:06 IvanaHristova  
Unknown file formateps ATL-COM-DAQ-2018-170_plot_2.eps r1 manage 20.9 K 2018-11-22 - 10:06 IvanaHristova  
PDFpdf ATL-COM-DAQ-2018-170_plot_2.pdf r1 manage 16.2 K 2018-11-22 - 10:06 IvanaHristova  
PNGpng ATL-COM-DAQ-2018-170_plot_2.png r1 manage 16.4 K 2018-11-22 - 10:06 IvanaHristova  
Unknown file formateps ATL-DAQ-PUB-2010-001-fig_01a.eps r1 manage 123.5 K 2011-06-23 - 16:43 MartinWessels  
PNGpng ATL-DAQ-PUB-2010-001-fig_01a.png r1 manage 17.3 K 2011-06-23 - 16:43 MartinWessels  
Unknown file formateps ATL-DAQ-PUB-2010-001-fig_01b.eps r1 manage 187.9 K 2011-06-23 - 16:43 MartinWessels  
PNGpng ATL-DAQ-PUB-2010-001-fig_01b.png r1 manage 23.0 K 2011-06-23 - 16:43 MartinWessels  
Unknown file formateps ATL-DAQ-PUB-2010-001-fig_02a.eps r1 manage 101.0 K 2011-06-24 - 12:32 MartinWessels  
PNGpng ATL-DAQ-PUB-2010-001-fig_02a.png r1 manage 43.2 K 2011-06-24 - 12:33 MartinWessels  
Unknown file formateps ATL-DAQ-PUB-2010-001-fig_02b.eps r1 manage 98.3 K 2011-06-24 - 12:33 MartinWessels  
PNGpng ATL-DAQ-PUB-2010-001-fig_02b.png r1 manage 42.7 K 2011-06-24 - 12:33 MartinWessels  
Unknown file formateps ATL-DAQ-PUB-2010-001-fig_03a.eps r1 manage 10.0 K 2011-06-24 - 12:33 MartinWessels  
PNGpng ATL-DAQ-PUB-2010-001-fig_03a.png r1 manage 23.1 K 2011-06-24 - 12:34 MartinWessels  
Unknown file formateps ATL-DAQ-PUB-2010-001-fig_03b.eps r1 manage 10.0 K 2011-06-24 - 12:34 MartinWessels  
PNGpng ATL-DAQ-PUB-2010-001-fig_03b.png r1 manage 23.2 K 2011-06-24 - 12:34 MartinWessels  
Unknown file formateps ATL-DAQ-PUB-2010-001-fig_05a.eps r1 manage 110.0 K 2011-06-24 - 12:34 MartinWessels  
PNGpng ATL-DAQ-PUB-2010-001-fig_05a.png r1 manage 13.6 K 2011-06-24 - 12:35 MartinWessels  
Unknown file formateps ATL-DAQ-PUB-2010-001-fig_05b.eps r1 manage 113.5 K 2011-06-24 - 12:35 MartinWessels  
PNGpng ATL-DAQ-PUB-2010-001-fig_05b.png r1 manage 15.0 K 2011-06-24 - 12:37 MartinWessels  
Unknown file formateps ATL-DAQ-PUB-2010-001-fig_06a.eps r1 manage 110.8 K 2011-06-24 - 12:35 MartinWessels  
PNGpng ATL-DAQ-PUB-2010-001-fig_06a.png r1 manage 12.8 K 2011-06-24 - 12:35 MartinWessels  
Unknown file formateps ATL-DAQ-PUB-2010-001-fig_06b.eps r1 manage 111.2 K 2011-06-24 - 12:37 MartinWessels  
PNGpng ATL-DAQ-PUB-2010-001-fig_06b.png r1 manage 13.3 K 2011-06-24 - 12:37 MartinWessels  
Unknown file formateps ATL-DAQ-PUB-2010-001-fig_07a.eps r1 manage 111.5 K 2011-06-24 - 12:38 MartinWessels  
PNGpng ATL-DAQ-PUB-2010-001-fig_07a.png r1 manage 14.2 K 2011-06-24 - 12:38 MartinWessels  
Unknown file formateps ATL-DAQ-PUB-2010-001-fig_07b.eps r1 manage 111.9 K 2011-06-24 - 12:38 MartinWessels  
PNGpng ATL-DAQ-PUB-2010-001-fig_07b.png r1 manage 14.1 K 2011-06-24 - 12:39 MartinWessels  
Unknown file formateps ATL-DAQ-PUB-2010-001-fig_08a.eps r1 manage 112.9 K 2011-06-24 - 12:39 MartinWessels  
PNGpng ATL-DAQ-PUB-2010-001-fig_08a.png r1 manage 46.7 K 2011-06-24 - 12:39 MartinWessels  
Unknown file formateps ATL-DAQ-PUB-2010-001-fig_08b.eps r1 manage 495.6 K 2011-06-24 - 12:39 MartinWessels  
PNGpng ATL-DAQ-PUB-2010-001-fig_08b.png r1 manage 44.7 K 2011-06-24 - 12:40 MartinWessels  
Unknown file formateps ATL-DAQ-PUB-2010-001-fig_09a.eps r1 manage 9.9 K 2011-06-24 - 12:40 MartinWessels  
PNGpng ATL-DAQ-PUB-2010-001-fig_09a.png r1 manage 22.9 K 2011-06-24 - 12:41 MartinWessels  
Unknown file formateps ATL-DAQ-PUB-2010-001-fig_09b.eps r1 manage 10.0 K 2011-06-24 - 12:41 MartinWessels  
PNGpng ATL-DAQ-PUB-2010-001-fig_09b.png r1 manage 23.3 K 2011-06-24 - 12:41 MartinWessels  
Unknown file formateps ATL-DAQ-PUB-2010-001-fig_10a.eps r1 manage 149.7 K 2011-06-24 - 12:41 MartinWessels  
PNGpng ATL-DAQ-PUB-2010-001-fig_10a.png r1 manage 21.6 K 2011-06-24 - 12:42 MartinWessels  
Unknown file formateps ATL-DAQ-PUB-2010-001-fig_10b.eps r1 manage 152.2 K 2011-06-24 - 12:42 MartinWessels  
PNGpng ATL-DAQ-PUB-2010-001-fig_10b.png r1 manage 22.9 K 2011-06-24 - 12:42 MartinWessels  
Unknown file formateps ATL-DAQ-PUB-2010-001-fig_11a.eps r1 manage 117.0 K 2011-06-24 - 12:42 MartinWessels  
PNGpng ATL-DAQ-PUB-2010-001-fig_11a.png r1 manage 47.0 K 2011-06-24 - 12:43 MartinWessels  
Unknown file formateps ATL-DAQ-PUB-2010-001-fig_11b.eps r1 manage 108.8 K 2011-06-24 - 12:43 MartinWessels  
PNGpng ATL-DAQ-PUB-2010-001-fig_11b.png r1 manage 45.0 K 2011-06-24 - 12:43 MartinWessels  
Unknown file formateps ATL-DAQ-PUB-2010-001-fig_12a.eps r1 manage 103.7 K 2011-06-24 - 12:43 MartinWessels  
PNGpng ATL-DAQ-PUB-2010-001-fig_12a.png r1 manage 35.3 K 2011-06-24 - 12:44 MartinWessels  
Unknown file formateps ATL-DAQ-PUB-2010-001-fig_12b.eps r1 manage 111.9 K 2011-06-24 - 12:44 MartinWessels  
PNGpng ATL-DAQ-PUB-2010-001-fig_12b.png r1 manage 40.1 K 2011-06-24 - 12:44 MartinWessels  
Unknown file formateps ATL_COM_DAQ-2013-016-fig10.eps r1 manage 16.1 K 2013-05-14 - 18:25 JurajBracinik  
PNGpng ATL_COM_DAQ-2013-016-fig10.png r1 manage 24.5 K 2013-05-14 - 18:25 JurajBracinik  
Unknown file formateps ATL_COM_DAQ-2013-016-fig11.eps r1 manage 17.1 K 2013-05-14 - 18:25 JurajBracinik  
PNGpng ATL_COM_DAQ-2013-016-fig11.png r1 manage 36.1 K 2013-05-14 - 18:25 JurajBracinik  
Unknown file formateps ATL_COM_DAQ-2013-016-fig12.eps r1 manage 15.6 K 2013-05-14 - 18:25 JurajBracinik  
PNGpng ATL_COM_DAQ-2013-016-fig12.png r1 manage 34.0 K 2013-05-14 - 18:25 JurajBracinik  
Unknown file formateps ATL_COM_DAQ-2013-016-fig13.eps r1 manage 120.8 K 2013-05-14 - 18:25 JurajBracinik  
PNGpng ATL_COM_DAQ-2013-016-fig13.png r1 manage 20.9 K 2013-05-14 - 18:25 JurajBracinik  
Unknown file formateps ATL_COM_DAQ-2013-016-fig14.eps r1 manage 72.5 K 2013-05-14 - 18:28 JurajBracinik  
PNGpng ATL_COM_DAQ-2013-016-fig14.png r1 manage 18.9 K 2013-05-14 - 18:28 JurajBracinik  
Unknown file formateps ATL_COM_DAQ-2013-016-fig15.eps r1 manage 60.2 K 2013-05-14 - 18:28 JurajBracinik  
PNGpng ATL_COM_DAQ-2013-016-fig15.png r1 manage 17.9 K 2013-05-14 - 18:28 JurajBracinik  
Unknown file formateps ATL_COM_DAQ-2013-016-fig16.eps r1 manage 49.9 K 2013-05-14 - 18:28 JurajBracinik  
PNGpng ATL_COM_DAQ-2013-016-fig16.png r1 manage 17.8 K 2013-05-14 - 18:28 JurajBracinik  
Unknown file formateps ATL_COM_DAQ-2013-016-fig17.eps r1 manage 12.3 K 2013-05-14 - 18:28 JurajBracinik  
PNGpng ATL_COM_DAQ-2013-016-fig17.png r1 manage 15.6 K 2013-05-14 - 18:28 JurajBracinik  
Unknown file formateps ATL_COM_DAQ-2013-016-fig18.eps r1 manage 12.3 K 2013-05-14 - 18:29 JurajBracinik  
PNGpng ATL_COM_DAQ-2013-016-fig18.png r1 manage 15.8 K 2013-05-14 - 18:29 JurajBracinik  
Unknown file formateps ATL_COM_DAQ-2013-016-fig19.eps r1 manage 12.3 K 2013-05-14 - 18:29 JurajBracinik  
PNGpng ATL_COM_DAQ-2013-016-fig19.png r1 manage 14.5 K 2013-05-14 - 18:29 JurajBracinik  
Unknown file formateps ATL_COM_DAQ-2013-016-fig20.eps r1 manage 12.8 K 2013-05-14 - 18:32 JurajBracinik  
PNGpng ATL_COM_DAQ-2013-016-fig20.png r1 manage 14.4 K 2013-05-14 - 18:32 JurajBracinik  
Unknown file formateps ATL_COM_DAQ-2013-016-fig21.eps r1 manage 10.9 K 2013-05-14 - 18:32 JurajBracinik  
PNGpng ATL_COM_DAQ-2013-016-fig21.png r1 manage 11.8 K 2013-05-14 - 18:32 JurajBracinik  
Unknown file formateps ATL_COM_DAQ-2013-016-fig22.eps r1 manage 11.4 K 2013-05-14 - 18:32 JurajBracinik  
PNGpng ATL_COM_DAQ-2013-016-fig22.png r1 manage 12.1 K 2013-05-14 - 18:32 JurajBracinik  
Unknown file formateps ATL_COM_DAQ-2013-016-fig3.eps r1 manage 11.6 K 2013-05-14 - 18:20 JurajBracinik  
PNGpng ATL_COM_DAQ-2013-016-fig3.png r1 manage 12.8 K 2013-05-14 - 18:20 JurajBracinik  
Unknown file formateps ATL_COM_DAQ-2013-016-fig4.eps r1 manage 11.4 K 2013-05-14 - 18:20 JurajBracinik  
PNGpng ATL_COM_DAQ-2013-016-fig4.png r1 manage 13.0 K 2013-05-14 - 18:20 JurajBracinik  
Unknown file formateps ATL_COM_DAQ-2013-016-fig5.eps r1 manage 39.7 K 2013-05-14 - 18:20 JurajBracinik  
PNGpng ATL_COM_DAQ-2013-016-fig5.png r1 manage 18.5 K 2013-05-14 - 18:20 JurajBracinik  
Unknown file formateps ATL_COM_DAQ-2013-016-fig6.eps r1 manage 39.7 K 2013-05-14 - 18:23 JurajBracinik  
PNGpng ATL_COM_DAQ-2013-016-fig6.png r1 manage 18.4 K 2013-05-14 - 18:23 JurajBracinik  
Unknown file formateps ATL_COM_DAQ-2013-016-fig7.eps r1 manage 19.8 K 2013-05-14 - 18:23 JurajBracinik  
PNGpng ATL_COM_DAQ-2013-016-fig7.png r1 manage 35.1 K 2013-05-14 - 18:23 JurajBracinik  
Unknown file formateps ATL_COM_DAQ-2013-016-fig8.eps r1 manage 19.3 K 2013-05-14 - 18:23 JurajBracinik  
PNGpng ATL_COM_DAQ-2013-016-fig8.png r1 manage 35.5 K 2013-05-14 - 18:23 JurajBracinik  
Unknown file formateps ATL_COM_DAQ-2013-016-fig9.eps r1 manage 15.9 K 2013-05-14 - 18:23 JurajBracinik  
PNGpng ATL_COM_DAQ-2013-016-fig9.png r1 manage 24.2 K 2013-05-14 - 18:23 JurajBracinik  
PNGpng BCID_Eff_EMB.png r1 manage 13.6 K 2015-11-23 - 13:16 IvanaHristova  
PNGpng BCID_Eff_EMEC.png r1 manage 13.2 K 2015-11-23 - 13:16 IvanaHristova  
PNGpng BCID_Eff_FCAL.png r1 manage 14.4 K 2015-11-23 - 13:16 IvanaHristova  
Unknown file formateps ClosebyJets.eps r1 manage 18.5 K 2018-07-02 - 14:38 BenCarlson  
PDFpdf ClosebyJets.pdf r1 manage 18.5 K 2018-07-02 - 14:38 BenCarlson  
PNGpng ClosebyJets.png r1 manage 23.8 K 2018-07-02 - 14:38 BenCarlson  
Unknown file formateps EMB.eps r1 manage 75.6 K 2015-12-04 - 00:02 IvanaHristova  
PDFpdf EMB.pdf r1 manage 17.6 K 2015-12-04 - 00:02 IvanaHristova  
PNGpng EMB.png r1 manage 27.2 K 2015-12-04 - 00:02 IvanaHristova  
Unknown file formateps EMB.prel.eps r1 manage 77.9 K 2015-12-28 - 09:09 IvanaHristova  
PDFpdf EMB.prel.pdf r1 manage 17.6 K 2015-12-28 - 08:56 IvanaHristova  
PNGpng EMB.prel.png r1 manage 10.9 K 2015-12-28 - 09:50 IvanaHristova  
Unknown file formateps EMEC_IW.eps r1 manage 62.1 K 2015-12-04 - 00:03 IvanaHristova  
PDFpdf EMEC_IW.pdf r1 manage 15.9 K 2015-12-04 - 00:03 IvanaHristova  
PNGpng EMEC_IW.png r1 manage 26.0 K 2015-12-04 - 00:03 IvanaHristova  
Unknown file formateps EMEC_IW.prel.eps r1 manage 64.6 K 2015-12-28 - 09:09 IvanaHristova  
PDFpdf EMEC_IW.prel.pdf r1 manage 15.9 K 2015-12-28 - 08:56 IvanaHristova  
PNGpng EMEC_IW.prel.png r1 manage 10.7 K 2015-12-28 - 09:50 IvanaHristova  
Unknown file formateps EM_Layer.eps r1 manage 779.0 K 2015-12-03 - 23:40 IvanaHristova  
PDFpdf EM_Layer.pdf r1 manage 73.6 K 2015-12-03 - 23:40 IvanaHristova  
PNGpng EM_Layer.png r2 r1 manage 141.0 K 2015-12-03 - 23:56 IvanaHristova  
Unknown file formateps EM_Layer_AC25.prel.eps r1 manage 781.2 K 2015-12-28 - 09:09 IvanaHristova  
PDFpdf EM_Layer_AC25.prel.pdf r1 manage 73.6 K 2015-12-28 - 08:56 IvanaHristova  
PNGpng EM_Layer_AC25.prel.png r1 manage 101.6 K 2015-12-28 - 09:50 IvanaHristova  
Unknown file formateps EM_Layer_Matched.eps r1 manage 936.7 K 2015-12-03 - 23:40 IvanaHristova  
PDFpdf EM_Layer_Matched.pdf r1 manage 84.3 K 2015-12-03 - 23:40 IvanaHristova  
PNGpng EM_Layer_Matched.png r2 r1 manage 120.7 K 2015-12-03 - 23:56 IvanaHristova  
Unknown file formateps EM_Layer_Matched.prel.eps r1 manage 938.8 K 2015-12-28 - 09:09 IvanaHristova  
PDFpdf EM_Layer_Matched.prel.pdf r1 manage 84.3 K 2015-12-28 - 08:56 IvanaHristova  
PNGpng EM_Layer_Matched.prel.png r1 manage 87.2 K 2015-12-28 - 09:50 IvanaHristova  
PDFpdf EMratesB_vs_instlumiB.pdf r1 manage 17.2 K 2015-11-23 - 14:13 IvanaHristova  
PNGpng EMratesB_vs_instlumiB.png r1 manage 26.8 K 2015-11-23 - 14:10 IvanaHristova  
Unknown file formateps EMratesB_vs_instlumiB_final.eps r1 manage 21.0 K 2015-12-17 - 14:14 AndrewDaniells  
PDFpdf EMratesB_vs_instlumiB_final.pdf r2 r1 manage 20.3 K 2015-12-17 - 14:12 AndrewDaniells  
PNGpng EMratesB_vs_instlumiB_final.png r3 r2 r1 manage 47.9 K 2015-12-17 - 14:12 AndrewDaniells  
Unknown file formateps Electron.eps r1 manage 18.9 K 2018-07-02 - 14:38 BenCarlson  
PDFpdf Electron.pdf r1 manage 19.8 K 2018-07-02 - 14:38 BenCarlson  
PNGpng Electron.png r1 manage 24.9 K 2018-07-02 - 14:38 BenCarlson  
Unknown file formateps FCAL1-3.4.prel.eps r1 manage 78.7 K 2015-12-28 - 09:09 IvanaHristova  
PDFpdf FCAL1-3.4.prel.pdf r1 manage 18.5 K 2015-12-28 - 08:56 IvanaHristova  
PNGpng FCAL1-3.4.prel.png r1 manage 12.3 K 2015-12-28 - 09:50 IvanaHristova  
Unknown file formateps FCAL1-34.eps r1 manage 76.2 K 2015-12-04 - 00:07 IvanaHristova  
PDFpdf FCAL1-34.pdf r1 manage 18.5 K 2015-12-04 - 00:07 IvanaHristova  
PNGpng FCAL1-34.png r1 manage 30.5 K 2015-12-04 - 00:07 IvanaHristova  
PNGpng FIR_autocorr_em.png r1 manage 42.7 K 2015-11-23 - 12:42 IvanaHristova  
PNGpng FIR_autocorr_had.png r1 manage 43.0 K 2015-11-23 - 13:01 IvanaHristova  
PNGpng FIR_matched_em.png r1 manage 39.1 K 2015-11-23 - 12:42 IvanaHristova  
PNGpng FIR_matched_had.png r1 manage 41.5 K 2015-11-23 - 13:01 IvanaHristova  
Unknown file formateps Had_Layer.eps r1 manage 794.9 K 2015-12-03 - 23:40 IvanaHristova  
PDFpdf Had_Layer.pdf r1 manage 75.0 K 2015-12-03 - 23:40 IvanaHristova  
PNGpng Had_Layer.png r2 r1 manage 142.1 K 2015-12-03 - 23:56 IvanaHristova  
Unknown file formateps Had_Layer_AC25.prel.eps r1 manage 797.1 K 2015-12-28 - 09:10 IvanaHristova  
PDFpdf Had_Layer_AC25.prel.pdf r1 manage 75.0 K 2015-12-28 - 08:56 IvanaHristova  
PNGpng Had_Layer_AC25.prel.png r1 manage 102.3 K 2015-12-28 - 09:50 IvanaHristova  
PNGpng Had_Layer_Matched.png r1 manage 122.0 K 2015-12-03 - 23:56 IvanaHristova  
Unknown file formateps Had_Layer_Matched.prel.eps r1 manage 938.1 K 2015-12-28 - 09:10 IvanaHristova  
PDFpdf Had_Layer_Matched.prel.pdf r1 manage 84.4 K 2015-12-28 - 08:56 IvanaHristova  
PNGpng Had_Layer_Matched.prel.png r1 manage 87.2 K 2015-12-28 - 09:50 IvanaHristova  
Unknown file formateps Inclusive.eps r1 manage 16.3 K 2018-07-02 - 14:38 BenCarlson  
PDFpdf Inclusive.pdf r1 manage 17.4 K 2018-07-02 - 14:38 BenCarlson  
PNGpng Inclusive.png r1 manage 20.9 K 2018-07-02 - 14:38 BenCarlson  
Unknown file formateps L1Calo_lar_barrel_lutslopes.eps r1 manage 9.9 K 2018-07-02 - 17:23 JoergStelzer  
PNGpng L1Calo_lar_barrel_lutslopes.png r1 manage 14.1 K 2018-07-02 - 17:23 JoergStelzer  
Unknown file formateps L1Calo_lutslope.eps r1 manage 8324.1 K 2018-07-02 - 17:23 JoergStelzer  
PNGpng L1Calo_lutslope.png r1 manage 28.3 K 2018-07-02 - 17:23 JoergStelzer  
Unknown file formateps MET.eps r1 manage 14.7 K 2018-07-02 - 14:38 BenCarlson  
PDFpdf MET.pdf r1 manage 14.9 K 2018-07-02 - 14:38 BenCarlson  
PNGpng MET.png r1 manage 21.0 K 2018-07-02 - 14:38 BenCarlson  
Unknown file formateps Scatter_EMB.eps r1 manage 13.7 K 2018-07-02 - 17:02 JoergStelzer  
PNGpng Scatter_EMB.png r1 manage 26.1 K 2018-07-02 - 17:02 JoergStelzer  
Unknown file formateps Scatter_TILE.eps r1 manage 13.5 K 2018-07-02 - 17:02 JoergStelzer  
PNGpng Scatter_TILE.png r1 manage 370.1 K 2018-07-02 - 17:02 JoergStelzer  
PNGpng XE35_BCID_25ns_PedCorrOn.png r2 r1 manage 26.1 K 2015-12-05 - 18:43 IvanaHristova  
PNGpng XE35_BCID_50ns_PedCorrOff.png r2 r1 manage 25.6 K 2015-12-05 - 18:43 IvanaHristova  
PNGpng XE35_BCID_50ns_PedCorrOn.png r2 r1 manage 26.0 K 2015-12-05 - 18:43 IvanaHristova  
PDFpdf XE35ratesB_vs_instlumiB_50ns.pdf r1 manage 17.7 K 2015-11-23 - 14:13 IvanaHristova  
PNGpng XE35ratesB_vs_instlumiB_50ns.png r1 manage 19.5 K 2015-11-23 - 14:10 IvanaHristova  
Unknown file formateps XE35ratesB_vs_instlumiB_50ns_final.eps r1 manage 13.8 K 2015-12-17 - 14:14 AndrewDaniells  
PDFpdf XE35ratesB_vs_instlumiB_50ns_final.pdf r2 r1 manage 17.0 K 2015-12-17 - 14:16 AndrewDaniells  
PNGpng XE35ratesB_vs_instlumiB_50ns_final.png r2 r1 manage 37.3 K 2015-12-17 - 14:15 AndrewDaniells  
PNGpng final_EMratesB_vs_instlumiB.png r1 manage 47.9 K 2015-12-17 - 14:07 AndrewDaniells  
Unknown file formateps final_XE35ratesB_vs_instlumiB_50ns.eps r1 manage 11.4 K 2016-07-21 - 13:33 IvanaHristova  
PDFpdf final_XE35ratesB_vs_instlumiB_50ns.pdf r1 manage 15.1 K 2016-07-21 - 13:33 IvanaHristova  
PNGpng final_XE35ratesB_vs_instlumiB_50ns.png r1 manage 34.3 K 2016-07-21 - 13:33 IvanaHristova  
Unknown file formateps final_XE50ratesB_vs_instlumiB_50ns.eps r1 manage 11.1 K 2016-07-21 - 13:33 IvanaHristova  
PDFpdf final_XE50ratesB_vs_instlumiB_50ns.pdf r1 manage 15.1 K 2016-07-21 - 13:33 IvanaHristova  
PNGpng final_XE50ratesB_vs_instlumiB_50ns.png r1 manage 33.7 K 2016-07-21 - 13:33 IvanaHristova  
Unknown file formateps ramp_emb.eps r1 manage 10.5 K 2018-07-02 - 17:02 JoergStelzer  
PNGpng ramp_emb.png r1 manage 332.7 K 2018-07-02 - 17:02 JoergStelzer  
Unknown file formateps ramp_tile.eps r1 manage 10.5 K 2018-07-02 - 17:02 JoergStelzer  
PNGpng ramp_tile.png r1 manage 331.0 K 2018-07-02 - 17:02 JoergStelzer  
Unknown file formateps roi.eps r1 manage 15.0 K 2015-09-03 - 20:33 IvanaHristova  
PDFpdf roi.pdf r1 manage 15.5 K 2015-09-03 - 20:33 IvanaHristova  
PNGpng roi.png r1 manage 21.6 K 2015-09-03 - 20:33 IvanaHristova  
Unknown file formateps roi_276731.eps r1 manage 18.6 K 2015-11-23 - 20:25 IvanaHristova  
PDFpdf roi_276731.pdf r1 manage 6.4 K 2015-11-23 - 20:29 IvanaHristova  
PNGpng roi_276731.png r1 manage 23.3 K 2015-11-23 - 20:29 IvanaHristova  
Unknown file formateps tob.eps r1 manage 15.2 K 2015-09-03 - 20:33 IvanaHristova  
PDFpdf tob.pdf r1 manage 15.5 K 2015-09-03 - 20:33 IvanaHristova  
PNGpng tob.png r1 manage 21.8 K 2015-09-03 - 20:33 IvanaHristova  
Unknown file formateps tob_276731.eps r1 manage 18.6 K 2015-11-23 - 20:29 IvanaHristova  
PDFpdf tob_276731.pdf r1 manage 6.4 K 2015-11-23 - 20:29 IvanaHristova  
PNGpng tob_276731.png r1 manage 23.3 K 2015-11-23 - 20:29 IvanaHristova  
Edit | Attach | Watch | Print version | History: r38 < r37 < r36 < r35 < r34 | Backlinks | Raw View | WYSIWYG | More topic actions
Topic revision: r38 - 2018-11-23 - ImmaRiu
 
    • 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