Difference: OnlineBeamSpotPublicResults (1 vs. 6)

Revision 62012-06-06 - FrankWinklmeier

Line: 1 to 1
 
META TOPICPARENT name="TriggerPublicResults"
AtlasPublicTopicHeader.png
Line: 36 to 36
 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.
Changed:
<
<

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

>
>

2012 running (8 TeV, beta*=0.6m, up to 1380 bunches)

Operational plots from 2011/12 pp-running

First Beam Spot Update

Number of luminosity blocks from the start of of a data-taking run until a valid beam spot has been determined and made available to the High Level Trigger processors during the 2011/12 proton-proton run. One luminosity block corresponds to about one minute of data-taking. A beam spot update is performed on the HLT farm if the position changes by more than 10% of the estimated luminous width; or the estimated luminous width changes by more than 10%; or the errors on these quantities decrease by more than 50%.


png pdf
Beam Spot Update Time

Time spent by the ca. 7600 Level-2 High Level Trigger applications loading the beam spot information from the conditions database. The time is measured between the reception of the update notification and the successful loading of the beam spot parameters from the conditions database. This extremely short update time is achieved by means of a database proxy hierarchy deployed on the High Level Trigger farm. The update time is significantly less than the average event processing time of 60ms and thus can be performed while data-taking is ongoing.


png pdf
Number of Beam Spot Updates

Number of beam spot updates to the High Level Trigger farm vs. luminosity block number for the 2011/12 proton-proton running period. The inset shows that the majority of beam spot updates are performed during the beginning of the fill. One luminosity block corresponds to about one minute of data-taking. A beam spot update is performed on the HLT farm if the position changes by more than 10% of the estimated luminous width; or the estimated luminous width changes by more than 10%; or the errors on these quantities decrease by more than 50%.


png pdf
Number of Beam Spot Updates per Run

Number of beam spot updates to the High Level Trigger farm for the 2011/12 proton-proton running period. Only runs with a duration of at least one hour are considered. Entries with very low number of beam spot updates per run are due to run re-starts during an ongoing LHC fill. A beam spot update is performed on the HLT farm if the position changes by more than 10% of the estimated luminous width; or the estimated luminous width changes by more than 10%; or the errors on these quantities decrease by more than 50%.


png pdf

Beam Spot Updates

Time-Evolution of Luminous Position in x

Time-evolution of the luminous centroid position in x measured in the High Level Trigger (HLT) during one LHC fill. The position is shown relative to the first valid beam spot and one luminosity block corresponds to about one minute of data-taking. The black dots are the current beam spot position measured in five minute intervals. If the position changes by more than 10% of the estimated luminous width; or the estimated luminous width changes by more than 10%; or the errors on these quantities decrease by more than 50% a beam spot update on the HLT farm is performed (red squares). The update is performed with a delay of about two luminosity blocks with respect to the current measurement. The green band indicates one of the update criteria, i.e. if the position changes by more than 10% of the estimated luminous width.


png pdf
Time-Evolution of Luminous Position in y

Time-evolution of the luminous centroid position in y measured in the High Level Trigger (HLT) during one LHC fill. The position is shown relative to the first valid beam spot and one luminosity block corresponds to about one minute of data-taking. The black dots are the current beam spot position measured in five minute intervals. If the position changes by more than 10% of the estimated luminous width; or the estimated luminous width changes by more than 10%; or the errors on these quantities decrease by more than 50% a beam spot update on the HLT farm is performed (red squares). The update is performed with a delay of about two luminosity blocks with respect to the current measurement. The green band indicates one of the update criteria, i.e. if the position changes by more than 10% of the estimated luminous width. The dip in the y-position at the beginning of the fill is currently under investigation and is possibly related to thermal effects.


png pdf
Time-Evolution of Luminous Position in z

Time-evolution of the luminous centroid position in z measured in the High Level Trigger (HLT) during one LHC fill. The position is shown relative to the first valid beam spot and one luminosity block corresponds to about one minute of data-taking. The black dots are the current beam spot position measured in five minute intervals. If the position changes by more than 10% of the estimated luminous width; or the estimated luminous width changes by more than 10%; or the errors on these quantities decrease by more than 50% a beam spot update on the HLT farm is performed (red squares). The update is performed with a delay of about two luminosity blocks with respect to the current measurement. The green band indicates one of the update criteria, i.e. if the position changes by more than 10% of the estimated luminous width.


png pdf
Time-Evolution of Luminous Width in x

Time-evolution of the estimated luminous width in x by measuring the width of the vertex distribution in the High Level Trigger (HLT) and applying a first-order resolution correction. One luminosity block corresponds to about one minute of data-taking. The black dots are the current estimated luminous width measured in five minute intervals. If the position changes by more than 10% of the estimated luminous width; or the estimated luminous width changes by more than 10%; or the errors on these quantities decrease by more than 50% a beam spot update on the HLT farm is performed (red squares). The update is performed with a delay of about two luminosity blocks with respect to the current measurement. The green band indicates one of the update criteria, i.e. if the estimated luminous width changes by more than 10% of the nominal estimated luminous width. The initial decrease of the luminous width is due to the bootstrapping procedure of the resolution correction. The sub-sequent increase of the width is caused by the increase in beam emittance during the fill.


png pdf
Time-Evolution of Luminous Width in y

Time-evolution of the estimated luminous width in y by measuring the width of the vertex distribution in the High Level Trigger (HLT) and applying a first-order resolution correction. One luminosity block corresponds to about one minute of data-taking. The black dots are the current estimated luminous width measured in five minute intervals. If the position changes by more than 10% of the estimated luminous width; or the estimated luminous width changes by more than 10%; or the errors on these quantities decrease by more than 50% a beam spot update on the HLT farm is performed (red squares). The update is performed with a delay of about two luminosity blocks with respect to the current measurement. The green band indicates one of the update criteria, i.e. if the estimated luminous width changes by more than 10% of the nominal estimated luminous width. The initial decrease of the luminous width is due to the bootstrapping procedure of the resolution correction. The sub-sequent increase of the width is caused by the increase in beam emittance during the fill.


png pdf
Time-Evolution of Luminous Width in z

Time-evolution of the estimated luminous width in z by measuring the width of the vertex distribution in the High Level Trigger (HLT) and applying a first-order resolution correction. One luminosity block corresponds to about one minute of data-taking. The black dots are the current estimated luminous width measured in five minute intervals. If the position changes by more than 10% of the estimated luminous width; or the estimated luminous width changes by more than 10%; or the errors on these quantities decrease by more than 50% a beam spot update on the HLT farm is performed (red squares). The update is performed with a delay of about two luminosity blocks with respect to the current measurement. The green band indicates one of the update criteria, i.e. if the estimated luminous width changes by more than 10% of the nominal estimated luminous width.


png pdf

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

 

Vertex Distributions

Line: 385 to 583
 
Changed:
<
<

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

>
>

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

  Show Hide
<!--/twistyPlugin twikiMakeVisibleInline-->
Line: 591 to 789
 
<!--For significant updates to the topic, consider adding your 'signature' (beneath this editing box)-->
Major updates:
-- RainerBartoldus - 13-Jun-2011
Added:
>
>
-- FrankWinklmeier - 06-Jun-2012
 
<!--Person responsible for the page: 
Either leave as is - the creator's name will be inserted; 
Line: 648 to 847
 
META FILEATTACHMENT attachment="bcid_vs_posZ_pm_posZErr.png" attr="" comment="Luminous centroid z for individual bunches of run 182787" date="1308428473" name="bcid_vs_posZ_pm_posZErr.png" path="bcid_vs_posZ_pm_posZErr.png" size="222412" stream="bcid_vs_posZ_pm_posZErr.png" tmpFilename="/usr/tmp/CGItemp18473" user="bartoldu" version="1"
META FILEATTACHMENT attachment="bcid_vs_posZ_pm_posZErr.pdf" attr="" comment="Luminous centroid z for individual bunches of run 182787" date="1308428528" name="bcid_vs_posZ_pm_posZErr.pdf" path="bcid_vs_posZ_pm_posZErr.pdf" size="73438" stream="bcid_vs_posZ_pm_posZErr.pdf" tmpFilename="/usr/tmp/CGItemp18483" user="bartoldu" version="1"
META FILEATTACHMENT attachment="Run182787_Vertex_XvsY_SiTrack_onelb.pdf" attr="" comment="2D x vs y histogram of beam spot vertices" date="1320072723" name="Run182787_Vertex_XvsY_SiTrack_onelb.pdf" path="Run182787_Vertex_XvsY_SiTrack_onelb.pdf" size="23564" stream="Run182787_Vertex_XvsY_SiTrack_onelb.pdf" tmpFilename="/usr/tmp/CGItemp44704" user="jcogan" version="1"
Added:
>
>
META FILEATTACHMENT attachment="beamspot_updatetime.pdf" attr="" comment="Beam spot update time" date="1338997971" name="beamspot_updatetime.pdf" path="beamspot_updatetime.pdf" size="14338" user="fwinkl" version="1"
META FILEATTACHMENT attachment="beamspot_updatetime.png" attr="" comment="Beam spot update time" date="1338997971" name="beamspot_updatetime.png" path="beamspot_updatetime.png" size="18240" user="fwinkl" version="1"
META FILEATTACHMENT attachment="first_update.pdf" attr="" comment="" date="1338997971" name="first_update.pdf" path="first_update.pdf" size="14182" user="fwinkl" version="1"
META FILEATTACHMENT attachment="first_update.png" attr="" comment="" date="1338997971" name="first_update.png" path="first_update.png" size="16884" user="fwinkl" version="1"
META FILEATTACHMENT attachment="run203602_beamposX.pdf" attr="" comment="" date="1338997971" name="run203602_beamposX.pdf" path="run203602_beamposX.pdf" size="24993" user="fwinkl" version="1"
META FILEATTACHMENT attachment="run203602_beamposX.png" attr="" comment="" date="1338997971" name="run203602_beamposX.png" path="run203602_beamposX.png" size="23684" user="fwinkl" version="1"
META FILEATTACHMENT attachment="run203602_beamposY.pdf" attr="" comment="" date="1338997971" name="run203602_beamposY.pdf" path="run203602_beamposY.pdf" size="25080" user="fwinkl" version="1"
META FILEATTACHMENT attachment="run203602_beamposY.png" attr="" comment="" date="1338997971" name="run203602_beamposY.png" path="run203602_beamposY.png" size="25091" user="fwinkl" version="1"
META FILEATTACHMENT attachment="run203602_beamposZ.pdf" attr="" comment="" date="1338997971" name="run203602_beamposZ.pdf" path="run203602_beamposZ.pdf" size="24729" user="fwinkl" version="1"
META FILEATTACHMENT attachment="run203602_beamposZ.png" attr="" comment="" date="1338997971" name="run203602_beamposZ.png" path="run203602_beamposZ.png" size="21809" user="fwinkl" version="1"
META FILEATTACHMENT attachment="run203602_beamsigmaX.pdf" attr="" comment="" date="1338998011" name="run203602_beamsigmaX.pdf" path="run203602_beamsigmaX.pdf" size="29431" user="fwinkl" version="1"
META FILEATTACHMENT attachment="run203602_beamsigmaX.png" attr="" comment="" date="1338998011" name="run203602_beamsigmaX.png" path="run203602_beamsigmaX.png" size="24496" user="fwinkl" version="1"
META FILEATTACHMENT attachment="run203602_beamsigmaY.pdf" attr="" comment="" date="1338998011" name="run203602_beamsigmaY.pdf" path="run203602_beamsigmaY.pdf" size="29424" user="fwinkl" version="1"
META FILEATTACHMENT attachment="run203602_beamsigmaY.png" attr="" comment="" date="1338998011" name="run203602_beamsigmaY.png" path="run203602_beamsigmaY.png" size="24713" user="fwinkl" version="1"
META FILEATTACHMENT attachment="run203602_beamsigmaZ.pdf" attr="" comment="" date="1338998011" name="run203602_beamsigmaZ.pdf" path="run203602_beamsigmaZ.pdf" size="22926" user="fwinkl" version="1"
META FILEATTACHMENT attachment="run203602_beamsigmaZ.png" attr="" comment="" date="1338998011" name="run203602_beamsigmaZ.png" path="run203602_beamsigmaZ.png" size="20316" user="fwinkl" version="1"
META FILEATTACHMENT attachment="update_count.pdf" attr="" comment="" date="1338998011" name="update_count.pdf" path="update_count.pdf" size="21519" user="fwinkl" version="1"
META FILEATTACHMENT attachment="update_count.png" attr="" comment="" date="1338998011" name="update_count.png" path="update_count.png" size="21429" user="fwinkl" version="1"
META FILEATTACHMENT attachment="update_perrun.pdf" attr="" comment="" date="1338998011" name="update_perrun.pdf" path="update_perrun.pdf" size="14142" user="fwinkl" version="1"
META FILEATTACHMENT attachment="update_perrun.png" attr="" comment="" date="1338998011" name="update_perrun.png" path="update_perrun.png" size="16079" user="fwinkl" version="1"

Revision 52011-10-31 - JoshCogan

Line: 1 to 1
 
META TOPICPARENT name="TriggerPublicResults"
AtlasPublicTopicHeader.png
Line: 608 to 608
 
META FILEATTACHMENT attachment="Run182787_Vertexz_SiTrack.png" attr="" comment="Vertex z distribution for one LB of run 182787" date="1308420566" name="Run182787_Vertexz_SiTrack.png" path="Run182787_Vertexz_SiTrack.png" size="267926" stream="Run182787_Vertexz_SiTrack.png" tmpFilename="/usr/tmp/CGItemp13589" user="bartoldu" version="1"
META FILEATTACHMENT attachment="Run182787_Vertexz_SiTrack.pdf" attr="" comment="Vertex z distribution for one LB of run 182787" date="1308420599" name="Run182787_Vertexz_SiTrack.pdf" path="Run182787_Vertexz_SiTrack.pdf" size="16963" stream="Run182787_Vertexz_SiTrack.pdf" tmpFilename="/usr/tmp/CGItemp13561" user="bartoldu" version="1"
META FILEATTACHMENT attachment="Run182787_Vertex_XvsY_SiTrack.png" attr="" comment="Vertex x vs y distribution for one LB of run 182787" date="1308421493" name="Run182787_Vertex_XvsY_SiTrack.png" path="Run182787_Vertex_XvsY_SiTrack.png" size="474930" stream="Run182787_Vertex_XvsY_SiTrack.png" tmpFilename="/usr/tmp/CGItemp18525" user="bartoldu" version="3"
Changed:
<
<
META FILEATTACHMENT attachment="Run182787_Vertex_XvsY_SiTrack.pdf" attr="" comment="Vertex x vs y distribution for run 182787" date="1308421619" name="Run182787_Vertex_XvsY_SiTrack.pdf" path="Run182787_Vertex_XvsY_SiTrack.pdf" size="36329" stream="Run182787_Vertex_XvsY_SiTrack.pdf" tmpFilename="/usr/tmp/CGItemp18498" user="bartoldu" version="2"
>
>
META FILEATTACHMENT attachment="Run182787_Vertex_XvsY_SiTrack.pdf" attr="" comment="Vertex x vs y distribution for run 182787" date="1320073058" name="Run182787_Vertex_XvsY_SiTrack.pdf" path="Run182787_Vertex_XvsY_SiTrack.pdf" size="23564" stream="Run182787_Vertex_XvsY_SiTrack.pdf" tmpFilename="/usr/tmp/CGItemp54521" user="jcogan" version="3"
 
META FILEATTACHMENT attachment="Run182787_Vertex_XvsY_SiTrack_EOR.png" attr="" comment="Vertex x vs y distribution for run 182787" date="1308421584" name="Run182787_Vertex_XvsY_SiTrack_EOR.png" path="Run182787_Vertex_XvsY_SiTrack_EOR.png" size="842670" stream="Run182787_Vertex_XvsY_SiTrack_EOR.png" tmpFilename="/usr/tmp/CGItemp18532" user="bartoldu" version="1"
META FILEATTACHMENT attachment="Run182787_Vertex_XvsY_SiTrack_EOR.pdf" attr="" comment="Vertex x vs y distribution for run 182787" date="1308422457" name="Run182787_Vertex_XvsY_SiTrack_EOR.pdf" path="Run182787_Vertex_XvsY_SiTrack_EOR.pdf" size="36329" stream="Run182787_Vertex_XvsY_SiTrack_EOR.pdf" tmpFilename="/usr/tmp/CGItemp18476" user="bartoldu" version="1"
META FILEATTACHMENT attachment="Run182787_TrackD0Phi_SiTrack.png" attr="" comment="Track d0 vs phi distribution for one LB of run 182787" date="1308422934" name="Run182787_TrackD0Phi_SiTrack.png" path="Run182787_TrackD0Phi_SiTrack.png" size="240882" stream="Run182787_TrackD0Phi_SiTrack.png" tmpFilename="/usr/tmp/CGItemp18523" user="bartoldu" version="1"
Line: 647 to 647
 
META FILEATTACHMENT attachment="bcid_vs_posY_pm_posYErr.pdf" attr="" comment="Luminous centroid y for individual bunches of run 182787" date="1308428432" name="bcid_vs_posY_pm_posYErr.pdf" path="bcid_vs_posY_pm_posYErr.pdf" size="73389" stream="bcid_vs_posY_pm_posYErr.pdf" tmpFilename="/usr/tmp/CGItemp18460" user="bartoldu" version="1"
META FILEATTACHMENT attachment="bcid_vs_posZ_pm_posZErr.png" attr="" comment="Luminous centroid z for individual bunches of run 182787" date="1308428473" name="bcid_vs_posZ_pm_posZErr.png" path="bcid_vs_posZ_pm_posZErr.png" size="222412" stream="bcid_vs_posZ_pm_posZErr.png" tmpFilename="/usr/tmp/CGItemp18473" user="bartoldu" version="1"
META FILEATTACHMENT attachment="bcid_vs_posZ_pm_posZErr.pdf" attr="" comment="Luminous centroid z for individual bunches of run 182787" date="1308428528" name="bcid_vs_posZ_pm_posZErr.pdf" path="bcid_vs_posZ_pm_posZErr.pdf" size="73438" stream="bcid_vs_posZ_pm_posZErr.pdf" tmpFilename="/usr/tmp/CGItemp18483" user="bartoldu" version="1"
Added:
>
>
META FILEATTACHMENT attachment="Run182787_Vertex_XvsY_SiTrack_onelb.pdf" attr="" comment="2D x vs y histogram of beam spot vertices" date="1320072723" name="Run182787_Vertex_XvsY_SiTrack_onelb.pdf" path="Run182787_Vertex_XvsY_SiTrack_onelb.pdf" size="23564" stream="Run182787_Vertex_XvsY_SiTrack_onelb.pdf" tmpFilename="/usr/tmp/CGItemp44704" user="jcogan" version="1"

Revision 42011-06-28 - RainerBartoldus

Line: 1 to 1
 
META TOPICPARENT name="TriggerPublicResults"
AtlasPublicTopicHeader.png
Line: 36 to 36
 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.
Changed:
<
<

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

>
>

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

 

Vertex Distributions

Revision 32011-06-27 - RainerBartoldus

Line: 1 to 1
 
META TOPICPARENT name="TriggerPublicResults"
AtlasPublicTopicHeader.png
Line: 7 to 7
 
Added:
>
>
<!-- 
 -->
<!-- 
-->
 

Introduction

<!-- Add an introduction here, describing the purpose of this topic. -->

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.

Changed:
<
<

2011 Data

>
>

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

 

Vertex Distributions

Changed:
<
<
>
>
 
Line: 34 to 56
  still dominated by the intrinsic resolution.
Changed:
<
<

[png] [pdf]
>
>

png pdf
 
Line: 52 to 74
  still dominated by the intrinsic resolution.
Changed:
<
<

[png] [pdf]
>
>

png pdf
 
Line: 69 to 91
  length, which is much larger than the intrinsic resolution.
Changed:
<
<

[png] [pdf]
>
>

png pdf
 
Line: 84 to 106
  1 minute of data taking and contains well over 100\,000 vertices.
Changed:
<
<

[png] [pdf]
>
>

png pdf
 
Line: 100 to 122
 
Changed:
<
<

[png] [pdf]
>
>

png pdf
 
Line: 119 to 141
  vertical tilt angles.
Changed:
<
<

[png] [pdf]
[png] [pdf]
>
>

png pdf
png pdf
 
Line: 134 to 156
 

Track Distributions

Changed:
<
<
>
>
 
Line: 153 to 174
  and is in excellent agreement with it.
Changed:
<
<

[png] [pdf]
>
>

png pdf
 
Line: 164 to 185
 

Resolution Correction

Changed:
<
<
>
>
 
Line: 187 to 207
 
Changed:
<
<

>
>

 [png] [pdf]
Changed:
<
<

>
>

 [png][pdf]
Deleted:
<
<
 
Displacement in z Between Split Vertices
Line: 219 to 235
 
Changed:
<
<

>
>

 [png][pdf]
Line: 243 to 259
 
Changed:
<
<

>
>
[
 [png] [pdf]
Changed:
<
<

>
>

 [png][pdf]
Line: 266 to 282
 
Changed:
<
<

>
>

 [png][pdf]
Line: 278 to 294
 

Time Evolutions

Changed:
<
<
>
>
 
Line: 292 to 307
  days.
Changed:
<
<

[png] [pdf]
[png] [pdf]
[png] [pdf]
>
>

png pdf
png pdf
png pdf
 
Added:
>
>
 
Time-Evolution of the Luminous Width (four days)
Line: 318 to 335
  the order of 10\% for a 10 hour long fill.
Changed:
<
<

[png] [pdf]
[png] [pdf]
[png] [pdf]
>
>

png pdf
png pdf
png pdf
 
Line: 336 to 353
 

Bunch-by-bunch Distributions

Changed:
<
<
>
>
 
Line: 345 to 361
  Luminous Centroid for Individual Bunches

The luminous centroid position in x, y, and z

Changed:
<
<
measured in the High Level Trigger for each colliding bunch pair
>
>
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.
Changed:
<
<

[png] [pdf]
[png] [pdf]
[png] [pdf]
>
>

png pdf
png pdf
png pdf
 
Line: 369 to 385
 
Changed:
<
<

2010 Data at 7 TeV

>
>

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

  Show Hide
<!--/twistyPlugin twikiMakeVisibleInline-->
Changed:
<
<
>
>
 
Changed:
<
<
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.
>
>
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.
 
Changed:
<
<

[png] [eps]
>
>

png eps
 
Changed:
<
<
Vertical luminous centroid (vertical "beam spot" position)
>
>
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
Line: 398 to 422
  online and with respect to the more sophisticated offline beam spot measurement.
Changed:
<
<

png eps
>
>

png eps
 
Changed:
<
<
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]
>
>

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]

<!--/twistyPlugin-->
 
Changed:
<
<
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]
>
>

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

 
Changed:
<
<
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]
>
>
Show Hide
<!--/twistyPlugin twikiMakeVisibleInline-->
 
Changed:
<
<
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]
>
>

Vertex Distributions

 
Changed:
<
<
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]
>
>
 
Changed:
<
<
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 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]
 
Changed:
<
<
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 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]
 
Changed:
<
<
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]
>
>
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]
 
Changed:
<
<
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]
>
>

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.
Changed:
<
<

png eps
>
>

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.
Changed:
<
<

png eps
>
>

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.
Changed:
<
<

png eps
>
>

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.
Changed:
<
<

png eps
>
>
/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.
Changed:
<
<

png
>
>

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.
Changed:
<
<

png
>
>

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.
Changed:
<
<

png
>
>

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.
Changed:
<
<

png
>
>

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.
Changed:
<
<

png
>
>

png
 
Added:
>
>

Timelines

 
Mean vertex X distribution for vertices reconstructed in each 2 minute interval for 6 runs between 11-13 Dec. 2009.
Changed:
<
<

png
>
>

png
 

Mean vertex Y distribution for vertices reconstructed in each 2 minute interval for 6 runs between 11-13 Dec. 2009.
Changed:
<
<

png
>
>

png
 

Mean vertex Z distribution for vertices reconstructed in each 2 minute interval for 6 runs between 11-13 Dec. 2009.
Changed:
<
<

png
>
>

png
 

Number of vertices reconstructed in each 2 minute interval for 6 runs between 11-13 Dec. 2009.
Changed:
<
<

png
>
>

png
 
Line: 535 to 583
 
<!--/twistyPlugin-->
Deleted:
<
<

2009 Data at 900 GeV

Show Hide

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

Revision 22011-06-18 - RainerBartoldus

Line: 1 to 1
 
META TOPICPARENT name="TriggerPublicResults"
AtlasPublicTopicHeader.png
Line: 13 to 13
 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.
Changed:
<
<

2011 Data at 7 TeV

>
>

2011 Data

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 colliding bunch pair 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 Data at 7 TeV

Changed: <
<

Online Beamspot

>
> Show Hide
<!--/twistyPlugin twikiMakeVisibleInline-->
 
Line: 178 to 532 
Added: >
>
<!--/twistyPlugin-->
 

2009 Data at 900 GeV

Added: >
> Show Hide
<!--/twistyPlugin twikiMakeVisibleInline-->
<!--/twistyPlugin-->
 
<!--***********************************************************-->
<!--Do NOT remove the remaining lines, but add requested info as appropriate-->
Line: 200 to 557 
<!--Once this page has been reviewed, please add the name and the date e.g. StephenHaywood - 31 Oct 2006 -->
Added: >
>
META FILEATTACHMENT attachment="Run182787_Vertexx_SiTrack.png" attr="" comment="Vertex x distribution for one LB of run 182787" date="1308420181" name="Run182787_Vertexx_SiTrack.png" path="Run182787_Vertexx_SiTrack.png" size="223999" stream="Run182787_Vertexx_SiTrack.png" tmpFilename="/usr/tmp/CGItemp13572" user="bartoldu" version="1"
META FILEATTACHMENT attachment="Run182787_Vertexx_SiTrack.pdf" attr="" comment="Vertex x distribution for one LB of run 182787" date="1308420258" name="Run182787_Vertexx_SiTrack.pdf" path="Run182787_Vertexx_SiTrack.pdf" size="15271" stream="Run182787_Vertexx_SiTrack.pdf" tmpFilename="/usr/tmp/CGItemp13585" user="bartoldu" version="1"
META FILEATTACHMENT attachment="Run182787_Vertexy_SiTrack.png" attr="" comment="Vertex y distribution for one LB of run 182787" date="1308420447" name="Run182787_Vertexy_SiTrack.png" path="Run182787_Vertexy_SiTrack.png" size="222032" stream="Run182787_Vertexy_SiTrack.png" tmpFilename="/usr/tmp/CGItemp13610" user="bartoldu" version="1"
META FILEATTACHMENT attachment="Run182787_Vertexy_SiTrack.pdf" attr="" comment="Vertex y distribution for one LB of run 182787" date="1308420471" name="Run182787_Vertexy_SiTrack.pdf" path="Run182787_Vertexy_SiTrack.pdf" size="15275" stream="Run182787_Vertexy_SiTrack.pdf" tmpFilename="/usr/tmp/CGItemp13576" user="bartoldu" version="1"
META FILEATTACHMENT attachment="Run182787_Vertexz_SiTrack.png" attr="" comment="Vertex z distribution for one LB of run 182787" date="1308420566" name="Run182787_Vertexz_SiTrack.png" path="Run182787_Vertexz_SiTrack.png" size="267926" stream="Run182787_Vertexz_SiTrack.png" tmpFilename="/usr/tmp/CGItemp13589" user="bartoldu" version="1"
META FILEATTACHMENT attachment="Run182787_Vertexz_SiTrack.pdf" attr="" comment="Vertex z distribution for one LB of run 182787" date="1308420599" name="Run182787_Vertexz_SiTrack.pdf" path="Run182787_Vertexz_SiTrack.pdf" size="16963" stream="Run182787_Vertexz_SiTrack.pdf" tmpFilename="/usr/tmp/CGItemp13561" user="bartoldu" version="1"
META FILEATTACHMENT attachment="Run182787_Vertex_XvsY_SiTrack.png" attr="" comment="Vertex x vs y distribution for one LB of run 182787" date="1308421493" name="Run182787_Vertex_XvsY_SiTrack.png" path="Run182787_Vertex_XvsY_SiTrack.png" size="474930" stream="Run182787_Vertex_XvsY_SiTrack.png" tmpFilename="/usr/tmp/CGItemp18525" user="bartoldu" version="3"
META FILEATTACHMENT attachment="Run182787_Vertex_XvsY_SiTrack.pdf" attr="" comment="Vertex x vs y distribution for run 182787" date="1308421619" name="Run182787_Vertex_XvsY_SiTrack.pdf" path="Run182787_Vertex_XvsY_SiTrack.pdf" size="36329" stream="Run182787_Vertex_XvsY_SiTrack.pdf" tmpFilename="/usr/tmp/CGItemp18498" user="bartoldu" version="2"
META FILEATTACHMENT attachment="Run182787_Vertex_XvsY_SiTrack_EOR.png" attr="" comment="Vertex x vs y distribution for run 182787" date="1308421584" name="Run182787_Vertex_XvsY_SiTrack_EOR.png" path="Run182787_Vertex_XvsY_SiTrack_EOR.png" size="842670" stream="Run182787_Vertex_XvsY_SiTrack_EOR.png" tmpFilename="/usr/tmp/CGItemp18532" user="bartoldu" version="1"
META FILEATTACHMENT attachment="Run182787_Vertex_XvsY_SiTrack_EOR.pdf" attr="" comment="Vertex x vs y distribution for run 182787" date="1308422457" name="Run182787_Vertex_XvsY_SiTrack_EOR.pdf" path="Run182787_Vertex_XvsY_SiTrack_EOR.pdf" size="36329" stream="Run182787_Vertex_XvsY_SiTrack_EOR.pdf" tmpFilename="/usr/tmp/CGItemp18476" user="bartoldu" version="1"
META FILEATTACHMENT attachment="Run182787_TrackD0Phi_SiTrack.png" attr="" comment="Track d0 vs phi distribution for one LB of run 182787" date="1308422934" name="Run182787_TrackD0Phi_SiTrack.png" path="Run182787_TrackD0Phi_SiTrack.png" size="240882" stream="Run182787_TrackD0Phi_SiTrack.png" tmpFilename="/usr/tmp/CGItemp18523" user="bartoldu" version="1"
META FILEATTACHMENT attachment="Run182787_TrackD0Phi_SiTrack.pdf" attr="" comment="Track d0 vs phi distribution for one LB of run 182787" date="1308422955" name="Run182787_TrackD0Phi_SiTrack.pdf" path="Run182787_TrackD0Phi_SiTrack.pdf" size="16889" stream="Run182787_TrackD0Phi_SiTrack.pdf" tmpFilename="/usr/tmp/CGItemp18460" user="bartoldu" version="1"
META FILEATTACHMENT attachment="Run182787_Tiltx_SiTrack.png" attr="" comment="Luminous xz tilt for run 182787" date="1308423385" name="Run182787_Tiltx_SiTrack.png" path="Run182787_Tiltx_SiTrack.png" size="204584" stream="Run182787_Tiltx_SiTrack.png" tmpFilename="/usr/tmp/CGItemp18469" user="bartoldu" version="2"
META FILEATTACHMENT attachment="Run182787_Tiltx_SiTrack.pdf" attr="" comment="Luminous xz tilt for run 182787" date="1308423403" name="Run182787_Tiltx_SiTrack.pdf" path="Run182787_Tiltx_SiTrack.pdf" size="16468" stream="Run182787_Tiltx_SiTrack.pdf" tmpFilename="/usr/tmp/CGItemp18537" user="bartoldu" version="2"
META FILEATTACHMENT attachment="Run182787_Tilty_SiTrack.png" attr="" comment="Luminous yz tilt for run 182787" date="1308423430" name="Run182787_Tilty_SiTrack.png" path="Run182787_Tilty_SiTrack.png" size="221382" stream="Run182787_Tilty_SiTrack.png" tmpFilename="/usr/tmp/CGItemp18477" user="bartoldu" version="2"
META FILEATTACHMENT attachment="Run182787_Tilty_SiTrack.pdf" attr="" comment="Luminous yz tilt for run 182787" date="1308423451" name="Run182787_Tilty_SiTrack.pdf" path="Run182787_Tilty_SiTrack.pdf" size="16563" stream="Run182787_Tilty_SiTrack.pdf" tmpFilename="/usr/tmp/CGItemp18441" user="bartoldu" version="2"
META FILEATTACHMENT attachment="Run182787_Vertex_SplitDeltax_SiTrack.png" attr="" comment="Split vertex displacement x vs number of tracks for run 182787" date="1308423962" name="Run182787_Vertex_SplitDeltax_SiTrack.png" path="Run182787_Vertex_SplitDeltax_SiTrack.png" size="1814823" stream="Run182787_Vertex_SplitDeltax_SiTrack.png" tmpFilename="/usr/tmp/CGItemp18535" user="bartoldu" version="1"
META FILEATTACHMENT attachment="Run182787_Vertex_SplitDeltax_SiTrack.pdf" attr="" comment="Split vertex displacement x vs number of tracks for run 182787" date="1308423984" name="Run182787_Vertex_SplitDeltax_SiTrack.pdf" path="Run182787_Vertex_SplitDeltax_SiTrack.pdf" size="99777" stream="Run182787_Vertex_SplitDeltax_SiTrack.pdf" tmpFilename="/usr/tmp/CGItemp18470" user="bartoldu" version="1"
META FILEATTACHMENT attachment="Run182787_Vertex_SplitDeltay_SiTrack.png" attr="" comment="Split vertex displacement y vs number of tracks for run 182787" date="1308424118" name="Run182787_Vertex_SplitDeltay_SiTrack.png" path="Run182787_Vertex_SplitDeltay_SiTrack.png" size="1780254" stream="Run182787_Vertex_SplitDeltay_SiTrack.png" tmpFilename="/usr/tmp/CGItemp18424" user="bartoldu" version="1"
META FILEATTACHMENT attachment="Run182787_Vertex_SplitDeltay_SiTrack.pdf" attr="" comment="Split vertex displacement y vs number of tracks for run 182787" date="1308424142" name="Run182787_Vertex_SplitDeltay_SiTrack.pdf" path="Run182787_Vertex_SplitDeltay_SiTrack.pdf" size="97801" stream="Run182787_Vertex_SplitDeltay_SiTrack.pdf" tmpFilename="/usr/tmp/CGItemp18344" user="bartoldu" version="1"
META FILEATTACHMENT attachment="Run182787_Vertex_SplitDeltaz_SiTrack.png" attr="" comment="Split vertex displacement z vs number of tracks for run 182787" date="1308424238" name="Run182787_Vertex_SplitDeltaz_SiTrack.png" path="Run182787_Vertex_SplitDeltaz_SiTrack.png" size="1838372" stream="Run182787_Vertex_SplitDeltaz_SiTrack.png" tmpFilename="/usr/tmp/CGItemp18566" user="bartoldu" version="1"
META FILEATTACHMENT attachment="Run182787_Vertex_SplitDeltaz_SiTrack.pdf" attr="" comment="Split vertex displacement z vs number of tracks for run 182787" date="1308424258" name="Run182787_Vertex_SplitDeltaz_SiTrack.pdf" path="Run182787_Vertex_SplitDeltaz_SiTrack.pdf" size="98005" stream="Run182787_Vertex_SplitDeltaz_SiTrack.pdf" tmpFilename="/usr/tmp/CGItemp18561" user="bartoldu" version="1"
META FILEATTACHMENT attachment="Run182787_X_Resolution_and_Width.png" attr="" comment="Beamspot x,y resolution and width for run 182787" date="1308426624" name="Run182787_X_Resolution_and_Width.png" path="Run182787_X_Resolution_and_Width.png" size="239558" stream="Run182787_X_Resolution_and_Width.png" tmpFilename="/usr/tmp/CGItemp18404" user="bartoldu" version="1"
META FILEATTACHMENT attachment="Run182787_X_Resolution_and_Width.pdf" attr="" comment="Beamspot x,y resolution and width for run 182787" date="1308426640" name="Run182787_X_Resolution_and_Width.pdf" path="Run182787_X_Resolution_and_Width.pdf" size="19551" stream="Run182787_X_Resolution_and_Width.pdf" tmpFilename="/usr/tmp/CGItemp18425" user="bartoldu" version="1"
META FILEATTACHMENT attachment="Run182787_Y_Resolution_and_Width.png" attr="" comment="Beamspot x,y resolution and width for run 182787" date="1308426686" name="Run182787_Y_Resolution_and_Width.png" path="Run182787_Y_Resolution_and_Width.png" size="238017" stream="Run182787_Y_Resolution_and_Width.png" tmpFilename="/usr/tmp/CGItemp18570" user="bartoldu" version="1"
META FILEATTACHMENT attachment="Run182787_Y_Resolution_and_Width.pdf" attr="" comment="Beamspot x,y resolution and width for run 182787" date="1308426705" name="Run182787_Y_Resolution_and_Width.pdf" path="Run182787_Y_Resolution_and_Width.pdf" size="19493" stream="Run182787_Y_Resolution_and_Width.pdf" tmpFilename="/usr/tmp/CGItemp18425" user="bartoldu" version="1"
META FILEATTACHMENT attachment="Run182787_Z_Resolution_and_Width.png" attr="" comment="Beamspot z resolution and width for run 182787" date="1308426885" name="Run182787_Z_Resolution_and_Width.png" path="Run182787_Z_Resolution_and_Width.png" size="222199" stream="Run182787_Z_Resolution_and_Width.png" tmpFilename="/usr/tmp/CGItemp18533" user="bartoldu" version="1"
META FILEATTACHMENT attachment="Run182787_Z_Resolution_and_Width.pdf" attr="" comment="Beamspot z resolution and width for run 182787" date="1308426927" name="Run182787_Z_Resolution_and_Width.pdf" path="Run182787_Z_Resolution_and_Width.pdf" size="19551" stream="Run182787_Z_Resolution_and_Width.pdf" tmpFilename="/usr/tmp/CGItemp18416" user="bartoldu" version="1"
META FILEATTACHMENT attachment="utc_vs_posX_pm_posXErr.png" attr="" comment="Time evolution of x centroid position for runs 182747 to 182886" date="1308427414" name="utc_vs_posX_pm_posXErr.png" path="utc_vs_posX_pm_posXErr.png" size="118319" stream="utc_vs_posX_pm_posXErr.png" tmpFilename="/usr/tmp/CGItemp18419" user="bartoldu" version="1"
META FILEATTACHMENT attachment="utc_vs_posX_pm_posXErr.pdf" attr="" comment="Time evolution of x centroid position for runs 182747 to 182886" date="1308427435" name="utc_vs_posX_pm_posXErr.pdf" path="utc_vs_posX_pm_posXErr.pdf" size="32748" stream="utc_vs_posX_pm_posXErr.pdf" tmpFilename="/usr/tmp/CGItemp18369" user="bartoldu" version="1"
META FILEATTACHMENT attachment="utc_vs_posY_pm_posYErr.png" attr="" comment="Time evolution of y centroid position for runs 182747 to 182886" date="1308427458" name="utc_vs_posY_pm_posYErr.png" path="utc_vs_posY_pm_posYErr.png" size="120689" stream="utc_vs_posY_pm_posYErr.png" tmpFilename="/usr/tmp/CGItemp18457" user="bartoldu" version="1"
META FILEATTACHMENT attachment="utc_vs_posY_pm_posYErr.pdf" attr="" comment="Time evolution of y centroid position for runs 182747 to 182886" date="1308427482" name="utc_vs_posY_pm_posYErr.pdf" path="utc_vs_posY_pm_posYErr.pdf" size="32857" stream="utc_vs_posY_pm_posYErr.pdf" tmpFilename="/usr/tmp/CGItemp18490" user="bartoldu" version="1"
META FILEATTACHMENT attachment="utc_vs_posZ_pm_posZErr.png" attr="" comment="Time evolution of z centroid position for runs 182747 to 182886" date="1308427528" name="utc_vs_posZ_pm_posZErr.png" path="utc_vs_posZ_pm_posZErr.png" size="128152" stream="utc_vs_posZ_pm_posZErr.png" tmpFilename="/usr/tmp/CGItemp18508" user="bartoldu" version="1"
META FILEATTACHMENT attachment="utc_vs_posZ_pm_posZErr.pdf" attr="" comment="Time evolution of z centroid position for runs 182747 to 182886" date="1308427572" name="utc_vs_posZ_pm_posZErr.pdf" path="utc_vs_posZ_pm_posZErr.pdf" size="33567" stream="utc_vs_posZ_pm_posZErr.pdf" tmpFilename="/usr/tmp/CGItemp18356" user="bartoldu" version="1"
META FILEATTACHMENT attachment="utc_vs_sigmaX_pm_sigmaXErr.png" attr="" comment="Time evolution of luminous x width for runs 182747 to 182886" date="1308427939" name="utc_vs_sigmaX_pm_sigmaXErr.png" path="utc_vs_sigmaX_pm_sigmaXErr.png" size="147584" stream="utc_vs_sigmaX_pm_sigmaXErr.png" tmpFilename="/usr/tmp/CGItemp18463" user="bartoldu" version="1"
META FILEATTACHMENT attachment="utc_vs_sigmaX_pm_sigmaXErr.pdf" attr="" comment="Time evolution of luminous x width for runs 182747 to 182886" date="1308427964" name="utc_vs_sigmaX_pm_sigmaXErr.pdf" path="utc_vs_sigmaX_pm_sigmaXErr.pdf" size="33499" stream="utc_vs_sigmaX_pm_sigmaXErr.pdf" tmpFilename="/usr/tmp/CGItemp18453" user="bartoldu" version="1"
META FILEATTACHMENT attachment="utc_vs_sigmaY_pm_sigmaYErr.png" attr="" comment="Time evolution of luminous y width for runs 182747 to 182886" date="1308429154" name="utc_vs_sigmaY_pm_sigmaYErr.png" path="utc_vs_sigmaY_pm_sigmaYErr.png" size="139737" stream="utc_vs_sigmaY_pm_sigmaYErr.png" tmpFilename="/usr/tmp/CGItemp18477" user="bartoldu" version="3"
META FILEATTACHMENT attachment="utc_vs_sigmaY_pm_sigmaYErr.pdf" attr="" comment="Time evolution of luminous y width for runs 182747 to 182886" date="1308429194" name="utc_vs_sigmaY_pm_sigmaYErr.pdf" path="utc_vs_sigmaY_pm_sigmaYErr.pdf" size="33505" stream="utc_vs_sigmaY_pm_sigmaYErr.pdf" tmpFilename="/usr/tmp/CGItemp18502" user="bartoldu" version="3"
META FILEATTACHMENT attachment="utc_vs_sigmaZ_pm_sigmaZErr.png" attr="" comment="Time evolution of luminous length for runs 182747 to 182886" date="1308429218" name="utc_vs_sigmaZ_pm_sigmaZErr.png" path="utc_vs_sigmaZ_pm_sigmaZErr.png" size="127352" stream="utc_vs_sigmaZ_pm_sigmaZErr.png" tmpFilename="/usr/tmp/CGItemp18497" user="bartoldu" version="3"
META FILEATTACHMENT attachment="utc_vs_sigmaZ_pm_sigmaZErr.pdf" attr="" comment="Time evolution of luminous length for runs 182747 to 182886" date="1308429246" name="utc_vs_sigmaZ_pm_sigmaZErr.pdf" path="utc_vs_sigmaZ_pm_sigmaZErr.pdf" size="33405" stream="utc_vs_sigmaZ_pm_sigmaZErr.pdf" tmpFilename="/usr/tmp/CGItemp18353" user="bartoldu" version="3"
META FILEATTACHMENT attachment="bcid_vs_posX_pm_posXErr.png" attr="" comment="Luminous centroid x for individual bunches of run 182787" date="1308428345" name="bcid_vs_posX_pm_posXErr.png" path="bcid_vs_posX_pm_posXErr.png" size="174640" stream="bcid_vs_posX_pm_posXErr.png" tmpFilename="/usr/tmp/CGItemp18418" user="bartoldu" version="1"
META FILEATTACHMENT attachment="bcid_vs_posX_pm_posXErr.pdf" attr="" comment="Luminous centroid x for individual bunches of run 182787" date="1308428373" name="bcid_vs_posX_pm_posXErr.pdf" path="bcid_vs_posX_pm_posXErr.pdf" size="72951" stream="bcid_vs_posX_pm_posXErr.pdf" tmpFilename="/usr/tmp/CGItemp18481" user="bartoldu" version="1"
META FILEATTACHMENT attachment="bcid_vs_posY_pm_posYErr.png" attr="" comment="Luminous centroid y for individual bunches of run 182787" date="1308428411" name="bcid_vs_posY_pm_posYErr.png" path="bcid_vs_posY_pm_posYErr.png" size="214551" stream="bcid_vs_posY_pm_posYErr.png" tmpFilename="/usr/tmp/CGItemp18449" user="bartoldu" version="1"
META FILEATTACHMENT attachment="bcid_vs_posY_pm_posYErr.pdf" attr="" comment="Luminous centroid y for individual bunches of run 182787" date="1308428432" name="bcid_vs_posY_pm_posYErr.pdf" path="bcid_vs_posY_pm_posYErr.pdf" size="73389" stream="bcid_vs_posY_pm_posYErr.pdf" tmpFilename="/usr/tmp/CGItemp18460" user="bartoldu" version="1"
META FILEATTACHMENT attachment="bcid_vs_posZ_pm_posZErr.png" attr="" comment="Luminous centroid z for individual bunches of run 182787" date="1308428473" name="bcid_vs_posZ_pm_posZErr.png" path="bcid_vs_posZ_pm_posZErr.png" size="222412" stream="bcid_vs_posZ_pm_posZErr.png" tmpFilename="/usr/tmp/CGItemp18473" user="bartoldu" version="1"
META FILEATTACHMENT attachment="bcid_vs_posZ_pm_posZErr.pdf" attr="" comment="Luminous centroid z for individual bunches of run 182787" date="1308428528" name="bcid_vs_posZ_pm_posZErr.pdf" path="bcid_vs_posZ_pm_posZErr.pdf" size="73438" stream="bcid_vs_posZ_pm_posZErr.pdf" tmpFilename="/usr/tmp/CGItemp18483" user="bartoldu" version="1"

Revision 12011-06-13 - RainerBartoldus

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

Online Beam Spot Public Results

<!--optional-->

Introduction

<!-- Add an introduction here, describing the purpose of this topic. -->

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 Data at 7 TeV

2010 Data at 7 TeV

Online Beamspot

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

2009 Data at 900 GeV

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


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

<!--Person responsible for the page: 
Either leave as is - the creator's name will be inserted; 
Or replace the complete REVINFO tag (including percentages symbols) with a name in the form TwikiUsersName-->
Responsible: RainerBartoldus
Subject: public
<!--Once this page has been reviewed, please add the name and the date e.g. StephenHaywood - 31 Oct 2006 -->
 
This site is powered by the TWiki collaboration platform Powered by PerlCopyright & 2008-2019 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback