# 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.

# 2011 Running (7 TeV, beta*=1.5m, up to 1318 bunches)

## Vertex Distributions

 Online Primary Vertex x Distribution Transverse horizontal distribution of primary vertices reconstructed online in the High Level Trigger. The distribution corresponds to 1 minute of data taking. The mean of the distribution reflects the luminous centroid position, while its width shows the uncorrected luminous size, which at this stage is still dominated by the intrinsic resolution. png pdf Online Primary Vertex y Distribution Transverse vertical distribution of primary vertices reconstructed online in the High Level Trigger. The distribution corresponds to 1 minute of data taking. The mean of the distribution reflects the luminous centroid position, while its width shows the uncorrected luminous size, which at this stage is still dominated by the intrinsic resolution. png pdf Online Primary Vertex z Distribution Longitudinal distribution of primary vertices reconstructed online in the High Level Trigger. The distribution corresponds to 1 minute of data taking. The mean of the distribution reflects the luminous centroid position, while its width shows the luminous length, which is much larger than the intrinsic resolution. png pdf Online Primary Vertex Distribution (after one minute) The transverse distribution of primary vertices reconstructed online in the High Level Trigger. The distribution corresponds to 1 minute of data taking and contains well over 100\,000 vertices. png pdf Online Primary Vertex Distribution (entire fill) The transverse distribution of primary vertices reconstructed online in the High Level Trigger. The distribution contains over 70 million vertices collected during one LHC fill. png pdf Horizontal and Vertical Luminous Tilt Angle The horizontal and vertical luminous tilt angles with respect to the ATLAS coordinate system measured online by the High Level Trigger. Transverse vertex distributions are divided into bins along the z-axis. The error bars indicate the error on the mean and are mostly too small to be visible. The slope is extracted with a linear fit versus z to measure the horizontal and vertical tilt angles. png pdf png pdf

## Track Distributions

 Luminous Centroid Position Measured with Tracks Transverse luminous centroid position measured online by the High Level Trigger using only track transverse impact parameter and azimuth angle. The transverse impact parameter d0 versus azimuth angle phi distribution measures the transverse luminous centroid position through a sinusoidal fit. The distribution corresponds to 1 minute of data taking. Point-by-point error bars are too small to be visible. This method is used as a cross-check of the vertex method and is in excellent agreement with it. png pdf

## Resolution Correction

 Displacement in x,y Between Split Vertices The displacements in x and y between each pair of separately reconstructed half vertices of a split primary vertex as a function of the number of tracks, measured online in the High Level Trigger. To measure the instrinsic vertex resolution, primary vertices are split, and the two resulting sets of tracks are fitted separately. The displacement measures the resolution of the vertex reconstruction as a function of the number of tracks per vertex, and is used to compute a correction that is applied in real time. The distributions illustrate the two competing features of this measurement: the resolution improves substantially the higher the number of tracks in the vertex, while the statistical precision is much higher for the lower track multiplicities. [png] [pdf] [png] [pdf] Displacement in z Between Split Vertices The displacements in z between each pair of separately reconstructed half vertices of a split primary vertex as a function of the number of tracks, measured online in the High Level Trigger. To measure the instrinsic vertex resolution, primary vertices are split, and the two resulting sets of tracks are fitted separately. The displacement measures the resolution of the vertex reconstruction as a function of the number of tracks per vertex, and is used to compute a correction that is applied in real time. The distributions illustrate the two competing features of this measurement: the resolution improves substantially the higher the number of tracks in the vertex, while the statistical precision is much higher for the lower track multiplicities. [png] [pdf] Beam Spot Transverse Resolution and Width The observed width of the primary vertex distribution, the measured resolution, and the resolution-corrected width, all as a function of the number of tracks per vertex. The observed width decreases with the track multiplicity as the resolution improves, while the corrected width stays essentially flat. The split vertex method is limited by the need for a corresponding sample of events with twice as many tracks per vertex. The method works well down to a certain multiplicity but then breaks down when the resolution becomes approximately twice the true width. The same behavior was observed for fills with larger beam sizes. [ [png] [pdf] [png] [pdf] Beam Spot Longitudinal Resolution and Width The width of the longitudinal primary vertex distribution along with the measured resolution as a function of the number of tracks per vertex. The z resolution has a similar dependence on the number of tracks as the resolution in the transverse plane. However, in contrast to the transverse plane, in the longitudinal direction the resolution-correction is entirely negligible. [png] [pdf]

## Time Evolutions

 Time-Variation of the Luminous Centroid Position (four days) Time-variation of the luminous centroid position in x, y, and z measured in the High Level Trigger every five minutes, for six separate LHC fills recorded over the span of four days. png pdf png pdf png pdf Time-Evolution of the Luminous Width (four days) Time-evolution of the luminous size in x, y, and z measured in the High Level Trigger every five minutes, for six separate LHC fills recorded over the span of four days. The effect of the transverse emittance blow-up is clearly visible during each fill and is on the order of 15\% on the horizontal width and 10\% on the vertical width for a 10 hour fill. Similarly, the luminous length increase from longitudinal emittance blow-up is on the order of 10\% for a 10 hour long fill. png pdf png pdf png pdf

## Bunch-by-bunch Distributions

 Luminous Centroid for Individual Bunches The luminous centroid position in x, y, and z measured in the High Level Trigger for each of the 1024 colliding bunch pairs separately. Distinct structures are visible, in particular in the vertical position of the interaction-point, with variations of up to 5\,$\mu$m and repeating patterns across the injected bunch trains. png pdf png pdf png pdf

# 2010 Running (7 TeV, beta*=2m, up to 368 bunches)

 Horizontal luminous centroid (horizontal "beam spot" position) Online luminous region measurements at $\sqrt{s}=7$~TeV. These measurements were available online in real time as soon as the high-level trigger was activated for the first high energy collisions at the LHC. Gaussian fits (within $\pm1\times RMS$ for $x$,$y$) are used to extract the luminous region mean position and width, where the latter is dominated by the vertexing resolution. An excellent agreement is observed using different tracking algorithms online and with respect to the more sophisticated offline beam spot measurement. png eps Vertical luminous centroid (vertical "beam spot" position) Online luminous region measurements at $\sqrt{s}=7$~TeV. These measurements were available online in real time as soon as the high-level trigger was activated for the first high energy collisions at the LHC. Gaussian fits (within $\pm1\times RMS$ for $x$,$y$) are used to extract the luminous region mean position and width, where the latter is dominated by the vertexing resolution. An excellent agreement is observed using different tracking algorithms online and with respect to the more sophisticated offline beam spot measurement. png eps Longitudinal luminous centroid (longitudinal "beam spot" position) Online luminous region measurements at $\sqrt{s}=7$~TeV. These measurements were available online in real time as soon as the high-level trigger was activated for the first high energy collisions at the LHC. Gaussian fits (within $\pm1\times RMS$ for $x$,$y$) are used to extract the luminous region mean position and width, where the latter is dominated by the vertexing resolution. An excellent agreement is observed using different tracking algorithms online and with respect to the more sophisticated offline beam spot measurement. [png] [eps] Luminous centroid ("beam spot") position measured with tracks Luminous centroid ("beam spot") position measured online using only level two tracking at $\sqrt{s}=7$ TeV. The transverse impact parameter ($d_{0}$) versus $\phi$ measures the transverse luminous centroid ("beam spot") position using a sinusoidal fit of $d_{0}$ as a function of $\phi$. The track-based result agrees to within 8 $\mu$m in $x$ and within 3 $\mu$m in $y$ with the positions measured via vertex fitting on an event-by-event basis. Point-by-point error bars are too small to be visible. [png] [eps] Horizontal luminous tilt angle The horizontal and vertical luminous tilt angles with respect to the ATLAS coordinate system are measured online at $\sqrt{s}=7$ TeV. Vertices are binned in two dimensions along $z$ and a Gaussian fit along the transverse direction is used to extract the mean position. The errors indicate the error on this mean. The slope is measured with a linear fit versus $z$ to extract the horizontal and vertical tilt angles, and in both cases agrees with the offline result to within 70 $\mu$rad. [png] [eps] Vertical luminous tilt angle The horizontal and vertical luminous tilt angles with respect to the ATLAS coordinate system are measured online at $\sqrt{s}=7$ TeV. Vertices are binned in two dimensions along $z$ and a Gaussian fit along the transverse direction is used to extract the mean position. The errors indicate the error on this mean. The slope is measured with a linear fit versus $z$ to extract the horizontal and vertical tilt angles, and in both cases agrees with the offline result to within 70 $\mu$rad. [png] [eps]

# 2009 Running (900 GeV, beta*=11m, 1-9 bunches)

## Vertex Distributions

 Vertex X distribution per colliding bunch (BCID) for run 142383 The monitored luminous region position (X,Y,Z) and relative luminosity per bunch ($N_{\rm vertex}$) are monitored as a function of the fill pattern of the LHC. These quantities are available online for every luminosity block and provide information relevant to the both the trigger and the data quality, as well as the machine conditions. [png] [eps] Vertex Y distribution per colliding bunch (BCID) for run 142383 The monitored luminous region position (X,Y,Z) and relative luminosity per bunch ($N_{\rm vertex}$) are monitored as a function of the fill pattern of the LHC. These quantities are available online for every luminosity block and provide information relevant to the both the trigger and the data quality, as well as the machine conditions. [png] [eps] Vertex Z distribution per colliding bunch (BCID) for run 142383 The monitored luminous region position (X,Y,Z) and relative luminosity per bunch ($N_{\rm vertex}$) are monitored as a function of the fill pattern of the LHC. These quantities are available online for every luminosity block and provide information relevant to the both the trigger and the data quality, as well as the machine conditions. [png] [eps] Average vertex multiplicity per event and per colliding bunch (BCID) for run 142383 The monitored luminous region position (X,Y,Z) and relative luminosity per bunch ($N_{\rm vertex}$) are monitored as a function of the fill pattern of the LHC. These quantities are available online for every luminosity block and provide information relevant to the both the trigger and the data quality, as well as the machine conditions. [png] [eps] Relative luminosity from HLT vertex counting Relative luminosity measurement measured via vertex counting and compared to the Liquid-Argon (LAr) calorimeter measurement for run 142193 (LHC fill number 911). The profile measured online using vertices follows the observed decay from the LAr with a very high precision after normalization to the LAr measurement. The nearly identical shape indicates that the level of background is likely to be small for the vertex counting method, or at least nearly constant with respect to time and luminosity. [png] [eps] Vertex X distribution for run 141811 This distribution represents the transverse distribution in X of vertices reconstructed by the LVL2 trigger (online) Atlas.BeamSpot algorithm in run141811. This is the first run for which the HLT was active (in passthrough mode) and the silicon detectors were at their fully operational bias voltages. We measure a horizontal position of X = 160.7 +/- 6um with an observed width of 240um for the core of the distribution. png eps Vertex Y distribution for run 141811 This distribution represents the transverse distribution in Y of vertices reconstructed by the LVL2 trigger (online) Atlas.BeamSpot algorithm in run141811.This is the first run for which the HLT was active (in passthrough mode) and the silicon detectors were at their fully operational bias voltages. We measure a vertical position of Y = 955 +/- 7um with an observed width of 280um for the core of the distribution. png eps Vertex Z distribution for run 141811 (BCID = 1, 2674) This plot represents the longitudinal distribution of vertices reconstructed by the LVL2 trigger (online) Atlas.BeamSpot algorithms for run 141811. Thiswas the very first run for which the HLT was active (in passthrough mode) and the Silcon detectors (Pixel and SCT) were at their fully operational bias voltages. We have separated the distribution into the two bunch crossing identifiers (BCID) for the two pairs of colliding bunches in the LHC machine. We can see that BCID = 2674 has a higher intensity than BCID = 1 due to the 50% larger number of vertices reconstructed. The mean longitudinal positions and extent are compatible within errors. png eps Track transverse impact parameter vs. phi distribution for run 141811 This distribution represents the track impact parameter variation as a function of the azimuthal angle, phi, of the track. Tracks used here arerequired to have a transverse momentum greater than 500 MeV. The sinusoidal variation is indicative of an underlying interaction point offset with respect to the center of the nominal ATLAS coordinate system, or (0,0,0). By fitting a sinusoidal function with two components, we can immediately extract the position of the interaction point in the transverse plane. We measure this position to be X = 163.6 +/- 8um and Y = 904.1 +/- 9um, which is in good agreement with the vertex-based measurement. /twiki/pub/AtlasPublic/TriggerOperationPublicResults png eps The transverse distribution in X of vertices reconstructed by the online beam spot algorithm in run 142913. We measure the average horizontal position as X = 253 +/- 2um with an observed width of 278um including resolution. png The transverse distribution in Y of vertices reconstructed by the online beam spot algorithm in run 142913. We measure the average vertical position as Y = 877 +/- 2um with an observed width of 345um including resolution. png The longitudinal distribution of vertices reconstructed by the online beam spot algorithm for run 142193. We measure an average position of Z = -7.99 +/- 0.24 mm with an observed width of 41 mm including resolution. png The distribution of primary vertices in the transverse plane reconstructed by the online beam spot algorithm for run 142193. Vertices are fitted from 2 or more tracks with a pT > 500 MeV. png The track impact parameter variation as a function of the azimuthal angle, phi, for tracks with pT > 500 MeV. From a sinusoidal fit, we extract the center of the interaction region as X = 241 +/- 3um and Y = 844 +/- 3um. png

## Timelines

 Mean vertex X distribution for vertices reconstructed in each 2 minute interval for 6 runs between 11-13 Dec. 2009. png Mean vertex Y distribution for vertices reconstructed in each 2 minute interval for 6 runs between 11-13 Dec. 2009. png Mean vertex Z distribution for vertices reconstructed in each 2 minute interval for 6 runs between 11-13 Dec. 2009. png Number of vertices reconstructed in each 2 minute interval for 6 runs between 11-13 Dec. 2009. png

-- RainerBartoldus - 13-Jun-2011 -- FrankWinklmeier - 06-Jun-2012

Responsible: RainerBartoldus
Subject: public

Topic attachments
I Attachment History Action Size Date Who Comment
pdf Run182787_Tiltx_SiTrack.pdf r2 r1 manage 16.1 K 2011-06-18 - 20:56 RainerBartoldus Luminous xz tilt for run 182787
png Run182787_Tiltx_SiTrack.png r2 r1 manage 199.8 K 2011-06-18 - 20:56 RainerBartoldus Luminous xz tilt for run 182787
pdf Run182787_Tilty_SiTrack.pdf r2 r1 manage 16.2 K 2011-06-18 - 20:57 RainerBartoldus Luminous yz tilt for run 182787
png Run182787_Tilty_SiTrack.png r2 r1 manage 216.2 K 2011-06-18 - 20:57 RainerBartoldus Luminous yz tilt for run 182787
pdf Run182787_TrackD0Phi_SiTrack.pdf r1 manage 16.5 K 2011-06-18 - 20:49 RainerBartoldus Track d0 vs phi distribution for one LB of run 182787
png Run182787_TrackD0Phi_SiTrack.png r1 manage 235.2 K 2011-06-18 - 20:48 RainerBartoldus Track d0 vs phi distribution for one LB of run 182787
pdf Run182787_Vertex_SplitDeltax_SiTrack.pdf r1 manage 97.4 K 2011-06-18 - 21:06 RainerBartoldus Split vertex displacement x vs number of tracks for run 182787
png Run182787_Vertex_SplitDeltax_SiTrack.png r1 manage 1772.3 K 2011-06-18 - 21:06 RainerBartoldus Split vertex displacement x vs number of tracks for run 182787
pdf Run182787_Vertex_SplitDeltay_SiTrack.pdf r1 manage 95.5 K 2011-06-18 - 21:09 RainerBartoldus Split vertex displacement y vs number of tracks for run 182787
png Run182787_Vertex_SplitDeltay_SiTrack.png r1 manage 1738.5 K 2011-06-18 - 21:08 RainerBartoldus Split vertex displacement y vs number of tracks for run 182787
pdf Run182787_Vertex_SplitDeltaz_SiTrack.pdf r1 manage 95.7 K 2011-06-18 - 21:10 RainerBartoldus Split vertex displacement z vs number of tracks for run 182787
png Run182787_Vertex_SplitDeltaz_SiTrack.png r1 manage 1795.3 K 2011-06-18 - 21:10 RainerBartoldus Split vertex displacement z vs number of tracks for run 182787
pdf Run182787_Vertex_XvsY_SiTrack.pdf r3 r2 r1 manage 23.0 K 2011-10-31 - 15:57 JoshCogan Vertex x vs y distribution for run 182787
png Run182787_Vertex_XvsY_SiTrack.png r3 r2 r1 manage 463.8 K 2011-06-18 - 20:24 RainerBartoldus Vertex x vs y distribution for one LB of run 182787
pdf Run182787_Vertex_XvsY_SiTrack_EOR.pdf r1 manage 35.5 K 2011-06-18 - 20:40 RainerBartoldus Vertex x vs y distribution for run 182787
png Run182787_Vertex_XvsY_SiTrack_EOR.png r1 manage 822.9 K 2011-06-18 - 20:26 RainerBartoldus Vertex x vs y distribution for run 182787
pdf Run182787_Vertex_XvsY_SiTrack_onelb.pdf r1 manage 23.0 K 2011-10-31 - 15:52 JoshCogan 2D x vs y histogram of beam spot vertices
pdf Run182787_Vertexx_SiTrack.pdf r1 manage 14.9 K 2011-06-18 - 20:04 RainerBartoldus Vertex x distribution for one LB of run 182787
png Run182787_Vertexx_SiTrack.png r1 manage 218.7 K 2011-06-18 - 20:03 RainerBartoldus Vertex x distribution for one LB of run 182787
pdf Run182787_Vertexy_SiTrack.pdf r1 manage 14.9 K 2011-06-18 - 20:07 RainerBartoldus Vertex y distribution for one LB of run 182787
png Run182787_Vertexy_SiTrack.png r1 manage 216.8 K 2011-06-18 - 20:07 RainerBartoldus Vertex y distribution for one LB of run 182787
pdf Run182787_Vertexz_SiTrack.pdf r1 manage 16.6 K 2011-06-18 - 20:09 RainerBartoldus Vertex z distribution for one LB of run 182787
png Run182787_Vertexz_SiTrack.png r1 manage 261.6 K 2011-06-18 - 20:09 RainerBartoldus Vertex z distribution for one LB of run 182787
pdf Run182787_X_Resolution_and_Width.pdf r1 manage 19.1 K 2011-06-18 - 21:50 RainerBartoldus Beamspot x,y resolution and width for run 182787
png Run182787_X_Resolution_and_Width.png r1 manage 233.9 K 2011-06-18 - 21:50 RainerBartoldus Beamspot x,y resolution and width for run 182787
pdf Run182787_Y_Resolution_and_Width.pdf r1 manage 19.0 K 2011-06-18 - 21:51 RainerBartoldus Beamspot x,y resolution and width for run 182787
png Run182787_Y_Resolution_and_Width.png r1 manage 232.4 K 2011-06-18 - 21:51 RainerBartoldus Beamspot x,y resolution and width for run 182787
pdf Run182787_Z_Resolution_and_Width.pdf r1 manage 19.1 K 2011-06-18 - 21:55 RainerBartoldus Beamspot z resolution and width for run 182787
png Run182787_Z_Resolution_and_Width.png r1 manage 217.0 K 2011-06-18 - 21:54 RainerBartoldus Beamspot z resolution and width for run 182787
pdf bcid_vs_posX_pm_posXErr.pdf r1 manage 71.2 K 2011-06-18 - 22:19 RainerBartoldus Luminous centroid x for individual bunches of run 182787
png bcid_vs_posX_pm_posXErr.png r1 manage 170.5 K 2011-06-18 - 22:19 RainerBartoldus Luminous centroid x for individual bunches of run 182787
pdf bcid_vs_posY_pm_posYErr.pdf r1 manage 71.7 K 2011-06-18 - 22:20 RainerBartoldus Luminous centroid y for individual bunches of run 182787
png bcid_vs_posY_pm_posYErr.png r1 manage 209.5 K 2011-06-18 - 22:20 RainerBartoldus Luminous centroid y for individual bunches of run 182787
pdf bcid_vs_posZ_pm_posZErr.pdf r1 manage 71.7 K 2011-06-18 - 22:22 RainerBartoldus Luminous centroid z for individual bunches of run 182787
png bcid_vs_posZ_pm_posZErr.png r1 manage 217.2 K 2011-06-18 - 22:21 RainerBartoldus Luminous centroid z for individual bunches of run 182787
pdf beamspot_updatetime.pdf r1 manage 14.0 K 2012-06-06 - 17:52 FrankWinklmeier Beam spot update time
png beamspot_updatetime.png r1 manage 17.8 K 2012-06-06 - 17:52 FrankWinklmeier Beam spot update time
pdf first_update.pdf r1 manage 13.8 K 2012-06-06 - 17:52 FrankWinklmeier
png first_update.png r1 manage 16.5 K 2012-06-06 - 17:52 FrankWinklmeier
pdf run203602_beamposX.pdf r1 manage 24.4 K 2012-06-06 - 17:52 FrankWinklmeier
png run203602_beamposX.png r1 manage 23.1 K 2012-06-06 - 17:52 FrankWinklmeier
pdf run203602_beamposY.pdf r1 manage 24.5 K 2012-06-06 - 17:52 FrankWinklmeier
png run203602_beamposY.png r1 manage 24.5 K 2012-06-06 - 17:52 FrankWinklmeier
pdf run203602_beamposZ.pdf r1 manage 24.1 K 2012-06-06 - 17:52 FrankWinklmeier
png run203602_beamposZ.png r1 manage 21.3 K 2012-06-06 - 17:52 FrankWinklmeier
pdf run203602_beamsigmaX.pdf r1 manage 28.7 K 2012-06-06 - 17:53 FrankWinklmeier
png run203602_beamsigmaX.png r1 manage 23.9 K 2012-06-06 - 17:53 FrankWinklmeier
pdf run203602_beamsigmaY.pdf r1 manage 28.7 K 2012-06-06 - 17:53 FrankWinklmeier
png run203602_beamsigmaY.png r1 manage 24.1 K 2012-06-06 - 17:53 FrankWinklmeier
pdf run203602_beamsigmaZ.pdf r1 manage 22.4 K 2012-06-06 - 17:53 FrankWinklmeier
png run203602_beamsigmaZ.png r1 manage 19.8 K 2012-06-06 - 17:53 FrankWinklmeier
pdf update_count.pdf r1 manage 21.0 K 2012-06-06 - 17:53 FrankWinklmeier
png update_count.png r1 manage 20.9 K 2012-06-06 - 17:53 FrankWinklmeier
pdf update_perrun.pdf r1 manage 13.8 K 2012-06-06 - 17:53 FrankWinklmeier
png update_perrun.png r1 manage 15.7 K 2012-06-06 - 17:53 FrankWinklmeier
pdf utc_vs_posX_pm_posXErr.pdf r1 manage 32.0 K 2011-06-18 - 22:03 RainerBartoldus Time evolution of x centroid position for runs 182747 to 182886
png utc_vs_posX_pm_posXErr.png r1 manage 115.5 K 2011-06-18 - 22:03 RainerBartoldus Time evolution of x centroid position for runs 182747 to 182886
pdf utc_vs_posY_pm_posYErr.pdf r1 manage 32.1 K 2011-06-18 - 22:04 RainerBartoldus Time evolution of y centroid position for runs 182747 to 182886
png utc_vs_posY_pm_posYErr.png r1 manage 117.9 K 2011-06-18 - 22:04 RainerBartoldus Time evolution of y centroid position for runs 182747 to 182886
pdf utc_vs_posZ_pm_posZErr.pdf r1 manage 32.8 K 2011-06-18 - 22:06 RainerBartoldus Time evolution of z centroid position for runs 182747 to 182886
png utc_vs_posZ_pm_posZErr.png r1 manage 125.1 K 2011-06-18 - 22:05 RainerBartoldus Time evolution of z centroid position for runs 182747 to 182886
pdf utc_vs_sigmaX_pm_sigmaXErr.pdf r1 manage 32.7 K 2011-06-18 - 22:12 RainerBartoldus Time evolution of luminous x width for runs 182747 to 182886
png utc_vs_sigmaX_pm_sigmaXErr.png r1 manage 144.1 K 2011-06-18 - 22:12 RainerBartoldus Time evolution of luminous x width for runs 182747 to 182886
pdf utc_vs_sigmaY_pm_sigmaYErr.pdf r3 r2 r1 manage 32.7 K 2011-06-18 - 22:33 RainerBartoldus Time evolution of luminous y width for runs 182747 to 182886
png utc_vs_sigmaY_pm_sigmaYErr.png r3 r2 r1 manage 136.5 K 2011-06-18 - 22:32 RainerBartoldus Time evolution of luminous y width for runs 182747 to 182886
pdf utc_vs_sigmaZ_pm_sigmaZErr.pdf r3 r2 r1 manage 32.6 K 2011-06-18 - 22:34 RainerBartoldus Time evolution of luminous length for runs 182747 to 182886
png utc_vs_sigmaZ_pm_sigmaZErr.png r3 r2 r1 manage 124.4 K 2011-06-18 - 22:33 RainerBartoldus Time evolution of luminous length for runs 182747 to 182886
Topic revision: r6 - 2012-06-06 - FrankWinklmeier

 Account
 Cern Search TWiki Search Google Search Atlas All webs
Copyright &© 2008-2021 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
or Ideas, requests, problems regarding TWiki? use Discourse or Send feedback