Difference: AtlasBackgrounds (1 vs. 28)

Revision 282010-02-25 - AlbertoPalma

Line: 1 to 1
 
<!-- Header + table of content !-->

ATLAS Beam Backgrounds

Line: 106 to 106
  atlas_bkg_haloAC.png
Changed:
<
<
The plot shows the rate of particles that are out-of-time. This particular plot shows the ATLAS BLMs rates during a run with cosmics. The time granularity at which the data is accumulated is 320 us and what is shown is the sum of data from the stations in side A and side C. The BLMs monitor the leakage current, which is proportional to the local particle flux, (...).
>
>
The plot shows the rate of particles that are out-of-time. This particular plot shows the ATLAS BLMs rates during a run with cosmics. The time granularity at which the data is accumulated is 320 us and what is shown is the sum of data from the stations in side A and side C.
  Monitored for BCM, MBTS and LAr: Out-of-time hits
Monitored for BLMs: Leakage current
Changed:
<
<
Units: Hz (for BLM the Hz is equivalent to 50 uA)
Trigger requirements:
>
>
Units: Hz
Trigger requirements: free running (independent from the ATLAS trigger)
 Typical 'good' levels: depends on the beam conditions
Typical 'warning' levels: to define but it is expected a very small fraction of background events when the beam is "clean"

Line: 137 to 137
 

Forward Detectors' Hit Rates (A + C)

Forward_13Jan2010_1.bmp
Changed:
<
<
The plot shows the total hit rates for LUCID. There are two detectors installed, one in side A and the other in side C of the ATLAS detector, in the end-cap region. The A + C hit rate is a simple sum of the two individual side rates, without any external trigger or timing requirement (for this reason the signal is noisy).
>
>
The plot shows the total hit rates for LUCID. There are two detectors installed, one in side A and the other in side C of the ATLAS detector, in the end-cap region. The A + C hit rate is a simple sum of the two individual side rates, without any external trigger or timing requirement.
 
Changed:
<
<
In the absence of beam, the hit rates mostly reflect cosmic muons traversing the quartz window of the LUCID photomultiplier. Rates of a few hundred Hz, with a regular line stretch, are visible during LUCID calibration. When the beam conditions are "clean", the hit rate is dominated by the luminosity, as we see here. However, if the beam conditions are not optimal, the hit rate will be dominated by backgrounds, as can be seen in the following plot taken during an aperture scan.
>
>
In the absence of beam, the hit rates mostly reflect cosmic muons traversing the quartz window of the LUCID photomultiplier and are typically inferior to 1Hz. Rates of a few hundred Hz, with a regular time structure, are visible during LUCID calibration. When the beam conditions are "clean", the hit rate is dominated by the luminosity, as we see here. However, if the beam conditions are not optimal, the hit rate will be dominated by backgrounds, as can be seen in the following plot taken during an aperture scan.
  forward_detectors_aperture_scan.png
Changed:
<
<
Hit rates for ZDC are equally available and follow the same behaviour of the LUCID hit rates: dominated by the luminosity signal on normal beam conditions, dominated by background events when the beam is "durty" and a regular line stretch is visible during calibration runs, but with a few Hz.
>
>
Hit rates for ZDC are equally available. The ZDC doesn't "see" cosmic muons since it is localized to deep in the tunnel. Rates of a few Hz, with a regular structure, are visible during ZDC calibration.
  Monitored: LUCID and ZDC total hit rates
Units: Hz
Trigger requirement: free running (independent of the ATLAS trigger)
Typical 'good' levels: depends on the luminosity signal
Changed:
<
<
Typical 'warning' levels: any signal that is much larger than the luminosity signal (more than the double of the amplitude)

>
>
Typical 'warning' levels: any signal that is much larger than the luminosity signal (more than the double of the luminosity signal)

 

ATLAS Normalized Beam Backgrounds

Line: 157 to 157
  collision_halo_normalized.png
Changed:
<
<
History display of BKGD1, defined as 100 * (TRT occupancy / 0.30), BKGD2, defined as 100 * (BCM Halo / Danger Level), and ATLAS BLM rates A + C. 30% is the optimized TRT occupancy at nominal LHC luminosity. The Danger Level is still to define. If BKGD1 or BKGD2 are above 50%, the beam is very "dirty"
>
>
History display of BKGD1, defined as 100 * (TRT occupancy / Danger Level), BKGD2, defined as 100 * (BCM Halo / Danger Level), and ATLAS BLM rates A + C. The Danger Level is 0.30 (30%) for BKGD1, corresponding to the expected TRT occupancy at nominal LHC luminosity. The Danger Level for BKGD2 is still to define. If BKGD1 or BKGD2 are above 50%, the beam is very "dirty".
  Monitored: BKGD1, BKGD2 and ATLAS BLM rates
Units for BLM rates: Hz (the others are dimensionless)
Changed:
<
<
Trigger requirement:
Typical 'good' levels for BKGD1 and BKGD2:
Typical 'good' levels for BLM rates:
Typical 'warning' levels for BKGD1 and BKGD2:
Typical 'warning' levels for BLM rates:

>
>
Trigger requirement for BKGD1: any event in the beam pick-up detectors (BPTX) stream; if we are taking cosmics, no requirements are made
Trigger requirement for BKGD2: to be determined
Typical 'good' levels for BKGD1 and BKGD2: to be determined
Typical 'good' levels for BLM rates: to be determined
Typical 'warning' levels for BKGD1 and BKGD2: 50%
Typical 'warning' levels for BLM rates: to be determined

 

Abort Level & Dead Time

abort_level.png

Changed:
<
<
History display of Abort Level and Dead Time. The Abort Level is defined as the fraction of BCM abort threshold. If the Abort Level is close to 100% we are about to abort.
>
>
History display of Abort Level and Dead Time. The Abort Level is defined as the fraction of BCM abort threshold. If the Abort Level is close to 50% we are about to abort.
  Monitored: Abort Level and Dead Time
Changed:
<
<
Units for Dead Time:
Trigger requirement:
Typical 'good' levels:
Typical 'warning' levels:

>
>
Units for Dead Time: dimensionless (1 means 100%)
Trigger requirement: full ATLAS trigger menu
Typical 'good' levels: to be determined
Typical 'warning' levels: to be determined

 

Beam Currents & Inverse Lifetimes

beam_currents.png

Changed:
<
<
History display of the two beam currents, B1 and B2, and inverse lifetimes of the beams. The beam current measurement is provided by DC current transformers (DCCT), which measure the total current (bunch and non bunch current). The inverse lifetimes of the beams are directly proportional to the beam loss, giving the indication of how fast the beam is lost.
>
>
History display of the two beam currents, B1 and B2, and inverse lifetimes of the beams. The beam current measurement is provided by DC current transformers (DCCT), which measure the total current (bunched and unbunched). The inverse lifetimes of the beams are directly proportional to the beam loss rate, giving the indication of the overall background level around the machine as a whole.
  Monitored: Beam currents and inverse lifetimes
Changed:
<
<
Units for beam curresnts:
Units for inverse lifetimes:
Trigger requirement:
Typical 'good' levels:
Typical 'warning' levels:

>
>
Units for beam curresnts: *e11 protons
Units for inverse lifetimes: to be determined
Trigger requirement: no trigger requirements
Typical 'good' levels: to be determined
Typical 'warning' levels: to be determined

 

BEAM HALO

Line: 202 to 203
  Monitored: Out-of-time hits in the BCM
Units: Hz
Changed:
<
<
Trigger requirement:
>
>
Trigger requirement: BCM is self triggered gated on the bunches
 Typical 'good' levels: depends on the beam conditions
Typical 'warning' levels: to define but it is expected a very small fraction of background events when the beam is "clean"

Line: 214 to 215
  Monitored: Out-of-time hits in MBTS and LAr
Units: Hz
Changed:
<
<
Trigger requirement:
Typical 'good' levels: to define
Typical 'warning' levels: to define

>
>
Trigger requirement: to be determined
Typical 'good' levels: to be determined
Typical 'warning' levels: to be determined

 

Halo Fractions (A + C / All)

Line: 226 to 227
  Monitored: fraction of out-of-time hits
Units: dimensionless (1 means 100%)
Changed:
<
<
Trigger requirement:
Typical 'good' levels: to define
Typical 'warning' levels: to define

>
>
Trigger requirement: BCM is self triggered
Typical 'good' levels: to be determined
Typical 'warning' levels: to be determined

 

ATLAS HIT RATES

Line: 240 to 241
  Monitored: BCM hit rates
Units: Hz
Changed:
<
<
Trigger requirement:
Typical 'good' levels: to define
Typical 'warning' levels: to define

>
>
Trigger requirement: no trigger requirements
Typical 'good' levels: to be determined
Typical 'warning' levels: to be determined

 

MBTS & L1Calo

Line: 254 to 255
  Monitored: MBTS and L1Calo rates
Units: Hz
Changed:
<
<
Trigger requirement:
Typical 'good' levels: to define
Typical 'warning' levels: to define

>
>
Trigger requirement for MBTS: sampled at 1Hz
Trigger requirement for L1Calo: to be determined
Typical 'good' levels: to be determined
Typical 'warning' levels: to be determined

 

Forward Detectors

Line: 268 to 270
 Units: Hz
Trigger requirement: free running (independent of the ATLAS trigger)
Typical 'good' levels: depends on the luminosity signal
Changed:
<
<
Typical 'warning' levels: any signal that is much larger than the luminosity signal (more than the double of the amplitude)

>
>
Typical 'warning' levels: any signal that is much larger than the luminosity signal (more than the double of the luminosity signal)

 

CALO CURRENTS

Line: 280 to 282
  tile_currents.png
Added:
>
>
The current is integrated at the output of a 3-1 card.
 Monitored: Current supplied to the PMTs
Changed:
<
<
Trigger requirement:
Typical 'good' levels:
Typical 'warning' levels:

>
>
Units: nA
Typical 'good' levels: to be determined
Typical 'warning' levels: to be determined

 

MBTS

MBTS_currents.png

Added:
>
>
The current is integrated at the output of a 3-1 card.
 Monitored: Current supplied to the PMTs
Changed:
<
<
Trigger requirement:
Typical 'good' levels:
Typical 'warning' levels:

>
>
Units: nA
Typical 'good' levels: to be determined
Typical 'warning' levels: to be determined

 

FCAL

FCAL_currents.png

Monitored: Current supplied to the electrodes

Changed:
<
<
Trigger requirement:
>
>
Units:
 Typical 'good' levels:
Typical 'warning' levels:

Line: 314 to 320
  MDT_muon_currents.png

Monitored: Current supplied to the electrodes

Changed:
<
<
Trigger requirement:
>
>
Units:
 Typical 'good' levels:
Typical 'warning' levels:

Line: 323 to 329
  TGC_HR_muon_currents.png

Monitored: Current supplied to the electrodes

Changed:
<
<
Trigger requirement:
Typical 'good' levels:
Typical 'warning' levels:

>
>
Units: uA
Typical 'good' levels: less than 15 uA
Typical 'warning' levels: 15 uA

 

TGC LR

TGC_LR_muon_currents.png

Monitored: Current supplied to the electrodes

Changed:
<
<
Trigger requirement:
Typical 'good' levels:
Typical 'warning' levels:

>
>
Units: uA
Typical 'good' levels: less than 15 uA
Typical 'warning' levels: 15 uA

 

Detailed description of timing and bunch-by-bunch beam conditions diagnostics

Revision 272010-02-25 - AlbertoPalma

Line: 1 to 1
 
<!-- Header + table of content !-->

ATLAS Beam Backgrounds

Revision 262010-02-25 - AlbertoPalma

Line: 1 to 1
 
<!-- Header + table of content !-->

ATLAS Beam Backgrounds

Line: 106 to 106
  atlas_bkg_haloAC.png
Changed:
<
<
The plot shows the rate of particles that are out-of-time in the ATLAS BLMs during a run with cosmics. The time granularity at which the data is accumulated is 320 us and the what is shown is the sum of data from the stations in side A and side C.
>
>
The plot shows the rate of particles that are out-of-time. This particular plot shows the ATLAS BLMs rates during a run with cosmics. The time granularity at which the data is accumulated is 320 us and what is shown is the sum of data from the stations in side A and side C. The BLMs monitor the leakage current, which is proportional to the local particle flux, (...).
  Monitored for BCM, MBTS and LAr: Out-of-time hits
Changed:
<
<
Monitored for BLMs: Leakage current, which is proportional to the local particle flux
>
>
Monitored for BLMs: Leakage current
 Units: Hz (for BLM the Hz is equivalent to 50 uA)
Trigger requirements:
Typical 'good' levels: depends on the beam conditions
Line: 117 to 117
 

ID Occupancies & Dead Time

IDoccupancy_13Jan2010.bmp
Changed:
<
<
The plot shows, as different colour trend lines, the TRT occupancy, averaged over all straws, and the total SCT space points, built from cluster pairs from the opposite sides of a given module, or from separate modules which overlap in eta or in phi. The TRT occupancy is counted by looking at straws with long Time Over Threshold, which reduces the noise, by almost two orders of magnitude, while still being sensitive to any particle fluxes.
>
>
The plot shows, as different colour trend lines, the TRT occupancy, averaged over all straws, and the total SCT space points, built from cluster pairs from the opposite sides of a given module, or from separate modules which overlap in eta or in phi. The TRT occupancy is counted by looking at straws with long Time Over Threshold (TOT), which reduces the noise, by almost two orders of magnitude, while still being sensitive to any particle fluxes.
 
Changed:
<
<
The fluctuations observed, in this case, are due essentially to beam halo fluctuations.

This history plot is updated every second. Every entry is an average over 10 events.

>
>
The fluctuations observed, in this case, are due essentially to beam halo fluctuations. The plot is updated every second. Every entry is an average over 10 events.
  Displays of the Pixel occupancy and total dead time are in preparation.

Monitored: Pixel and TRT total occupancies (1 means 100% occupancy), total SCT space points and total dead time (1 means 100% dead time)
Units: dimensionless
Trigger requirements for SCT/TRT: any event in the beam pick-up detectors (BPTX) stream; if we are taking cosmics, no requirements are made

Added:
>
>
Trigger requirements for Pixel: to be determined
Trigger requirements for Dead Time: to be determined
 Typical 'good' levels for SCT/TRT: TRT occupancy ~ 0.5%; SCT space points = 100 - 500
Changed:
<
<
Typical 'warning' levels SCT/TRT: to be determined
>
>
Typical 'good' levels for Pixel: to be determined
Typical 'good' levels for Dead Time: to be determined
Typical 'warning' levels for SCT/TRT: to be determined
Typical 'warning' levels for Pixel: to be determined
Typical 'warning' levels for Dead Time: to be determined
 

Forward Detectors' Hit Rates (A + C)

Forward_13Jan2010_1.bmp
The plot shows the total hit rates for LUCID. There are two detectors installed, one in side A and the other in side C of the ATLAS detector, in the end-cap region. The A + C hit rate is a simple sum of the two individual side rates, without any external trigger or timing requirement (for this reason the signal is noisy).
Changed:
<
<
In the absence of beam, the hit rates mostly reflect cosmic muons traversing the quartz window of the LUCID photomultiplier. Rates of a few hundred Hz, with a regular line stretch, are visible during LUCID calibration (see the plot in the ATLAS HIT RATES section, in this document). When the beam conditions are "clean", the hit rate is dominated by the luminosity, as we see here. However, if the beam conditions are not optimal, the hit rate will be dominated by backgrounds, as can be seen in the following plot taken during an aperture scan.
>
>
In the absence of beam, the hit rates mostly reflect cosmic muons traversing the quartz window of the LUCID photomultiplier. Rates of a few hundred Hz, with a regular line stretch, are visible during LUCID calibration. When the beam conditions are "clean", the hit rate is dominated by the luminosity, as we see here. However, if the beam conditions are not optimal, the hit rate will be dominated by backgrounds, as can be seen in the following plot taken during an aperture scan.
  forward_detectors_aperture_scan.png
Changed:
<
<
Hit rates for ZDC are equally available and follow the same behaviour of the LUCID hit rates: dominated by the luminosity signal on normal beam conditions, dominated by background events when the beam is not "clean" and a regular line stretch is visible during calibration runs, but with a few Hz.
>
>
Hit rates for ZDC are equally available and follow the same behaviour of the LUCID hit rates: dominated by the luminosity signal on normal beam conditions, dominated by background events when the beam is "durty" and a regular line stretch is visible during calibration runs, but with a few Hz.
  Monitored: LUCID and ZDC total hit rates
Units: Hz
Line: 156 to 160
 History display of BKGD1, defined as 100 * (TRT occupancy / 0.30), BKGD2, defined as 100 * (BCM Halo / Danger Level), and ATLAS BLM rates A + C. 30% is the optimized TRT occupancy at nominal LHC luminosity. The Danger Level is still to define. If BKGD1 or BKGD2 are above 50%, the beam is very "dirty"

Monitored: BKGD1, BKGD2 and ATLAS BLM rates

Changed:
<
<
Units for BLM rates: Hz
>
>
Units for BLM rates: Hz (the others are dimensionless)
 Trigger requirement:
Typical 'good' levels for BKGD1 and BKGD2:
Typical 'good' levels for BLM rates:
Line: 167 to 171
  abort_level.png
Changed:
<
<
History display of Abort Level and Dead Time. The Abort Level is defined as the fraction of BCM above threshold. If the Abort Level is close to 100% we are about to abort.
>
>
History display of Abort Level and Dead Time. The Abort Level is defined as the fraction of BCM abort threshold. If the Abort Level is close to 100% we are about to abort.
  Monitored: Abort Level and Dead Time
Changed:
<
<
Units for Dead Time: Hz
>
>
Units for Dead Time:
 Trigger requirement:
Typical 'good' levels:
Typical 'warning' levels:

Line: 182 to 186
 History display of the two beam currents, B1 and B2, and inverse lifetimes of the beams. The beam current measurement is provided by DC current transformers (DCCT), which measure the total current (bunch and non bunch current). The inverse lifetimes of the beams are directly proportional to the beam loss, giving the indication of how fast the beam is lost.

Monitored: Beam currents and inverse lifetimes

Changed:
<
<
Units for beam curresnts: *e11
>
>
Units for beam curresnts:
 Units for inverse lifetimes:
Trigger requirement:
Typical 'good' levels:
Line: 211 to 215
 Monitored: Out-of-time hits in MBTS and LAr
Units: Hz
Trigger requirement:
Changed:
<
<
Typical 'good' levels:
Typical 'warning' levels:

>
>
Typical 'good' levels: to define
Typical 'warning' levels: to define

 

Halo Fractions (A + C / All)

Line: 223 to 227
 Monitored: fraction of out-of-time hits
Units: dimensionless (1 means 100%)
Trigger requirement:
Changed:
<
<
Typical 'good' levels:
Typical 'warning' levels:

>
>
Typical 'good' levels: to define
Typical 'warning' levels: to define

 

ATLAS HIT RATES

Line: 237 to 241
 Monitored: BCM hit rates
Units: Hz
Trigger requirement:
Changed:
<
<
Typical 'good' levels:
Typical 'warning' levels:

>
>
Typical 'good' levels: to define
Typical 'warning' levels: to define

 

MBTS & L1Calo

Line: 251 to 255
 Monitored: MBTS and L1Calo rates
Units: Hz
Trigger requirement:
Changed:
<
<
Typical 'good' levels:
Typical 'warning' levels:

>
>
Typical 'good' levels: to define
Typical 'warning' levels: to define

 

Forward Detectors

Forward_12Dez2009.bmp

Changed:
<
<
History display of rates for LUCID and ZDC stations. The hit rates are dominated by the luminosity. However, they are sensitive to background when beam conditions are bad.
>
>
History display of rates for LUCID and ZDC stations. The hit rates are dominated by the luminosity during normal beam conditions. However, they are sensitive to background when beam conditions are bad.
  Monitored: LUCID and ZDC single-paddle rates
Units: Hz
Line: 276 to 280
  tile_currents.png
Changed:
<
<
Monitored:
>
>
Monitored: Current supplied to the PMTs
 Trigger requirement:
Typical 'good' levels:
Typical 'warning' levels:

Line: 285 to 289
  MBTS_currents.png
Changed:
<
<
Monitored:
>
>
Monitored: Current supplied to the PMTs
 Trigger requirement:
Typical 'good' levels:
Typical 'warning' levels:

Line: 294 to 298
  FCAL_currents.png
Changed:
<
<
Monitored:
>
>
Monitored: Current supplied to the electrodes
 Trigger requirement:
Typical 'good' levels:
Typical 'warning' levels:

Line: 309 to 313
  MDT_muon_currents.png
Changed:
<
<
Monitored:
>
>
Monitored: Current supplied to the electrodes
 Trigger requirement:
Typical 'good' levels:
Typical 'warning' levels:

Line: 318 to 322
  TGC_HR_muon_currents.png
Changed:
<
<
Monitored:
>
>
*Monitored:*Current supplied to the electrodes
 Trigger requirement:
Typical 'good' levels:
Typical 'warning' levels:

Line: 327 to 331
  TGC_LR_muon_currents.png
Changed:
<
<
Monitored:
>
>
Monitored: Current supplied to the electrodes
 Trigger requirement:
Typical 'good' levels:
Typical 'warning' levels:

Revision 252010-02-25 - AlbertoPalma

Line: 1 to 1
 
<!-- Header + table of content !-->

ATLAS Beam Backgrounds

Line: 151 to 151
 

Collision (BKGD1, BLM) & Halo (BKGD2)

Added:
>
>
collision_halo_normalized.png
 History display of BKGD1, defined as 100 * (TRT occupancy / 0.30), BKGD2, defined as 100 * (BCM Halo / Danger Level), and ATLAS BLM rates A + C. 30% is the optimized TRT occupancy at nominal LHC luminosity. The Danger Level is still to define. If BKGD1 or BKGD2 are above 50%, the beam is very "dirty"

Monitored: BKGD1, BKGD2 and ATLAS BLM rates

Line: 163 to 165
 

Abort Level & Dead Time

Added:
>
>
abort_level.png
 History display of Abort Level and Dead Time. The Abort Level is defined as the fraction of BCM above threshold. If the Abort Level is close to 100% we are about to abort.

Monitored: Abort Level and Dead Time

Line: 173 to 177
 

Beam Currents & Inverse Lifetimes

Added:
>
>
beam_currents.png
 History display of the two beam currents, B1 and B2, and inverse lifetimes of the beams. The beam current measurement is provided by DC current transformers (DCCT), which measure the total current (bunch and non bunch current). The inverse lifetimes of the beams are directly proportional to the beam loss, giving the indication of how fast the beam is lost.

Monitored: Beam currents and inverse lifetimes

Line: 182 to 188
 Typical 'good' levels:
Typical 'warning' levels:

Changed:
<
<

BEAM_HALO

>
>

BEAM HALO

 

BCM Halo Rates

Line: 236 to 242
 

MBTS & L1Calo

Changed:
<
<
MBTS_L1Calo_hit_rates.png
>
>
MBTS_LCD_AC_12Dec09_1.bmp
 
Changed:
<
<
History display of MBTS hit rates and level-1 trigger information based on the calorimeters, sampled at 1Hz, without any external trigger or timing requirement. MBTS hit rates are dominated by luminosity, as can be seen in the following plot that shows the sum of the two stations rates for MBTS:

Hits_all_12Dec2009.bmp

>
>
History display of MBTS hit rates and level-1 trigger information based on the calorimeters, sampled at 1Hz, without any external trigger or timing requirement. MBTS hit rates are dominated by luminosity, as can be seen.
  At the very low luminosities achieved so far, the randomly sampled L1 Calo rate is dominated by noise.
Line: 262 to 266
 Typical 'good' levels: depends on the luminosity signal
Typical 'warning' levels: any signal that is much larger than the luminosity signal (more than the double of the amplitude)

Changed:
<
<

CALO_CURRENTS

>
>

CALO CURRENTS

  The amount of current that is needed to supply to the PMTs and the electrodes of the LAr calorimeter is proportional to the number of charged particles detected. So we can try to use the supplied currents to monitor beam conditions.
Line: 295 to 299
 Typical 'good' levels:
Typical 'warning' levels:

Changed:
<
<

MUON_CURRENTS

>
>

MUON CURRENTS

The amount of current that is needed to supply to the electrodes of the muon chambers is proportional to the number of charged particles detected. So we can try to use the supplied currents to monitor beam conditions.

In the 2009 run was not seen any sensibility from the muon chambers currents to the beam conditions.

 

Forward MDT's

Line: 329 to 337
 To explain in a near future.

META FILEATTACHMENT attachment="button.png" attr="" comment="" date="1266090398" name="button.png" path="button.png" size="2311" stream="button.png" tmpFilename="/usr/tmp/CGItemp24804" user="apalma" version="1"
Deleted:
<
<
META FILEATTACHMENT attachment="Hits_all_12Dec2009.bmp" attr="" comment="" date="1266182366" name="Hits_all_12Dec2009.bmp" path="Hits_all_12Dec2009.bmp" size="683694" stream="Hits_all_12Dec2009.bmp" tmpFilename="/usr/tmp/CGItemp25222" user="apalma" version="1"
 
META FILEATTACHMENT attachment="IDoccupancy_13Jan2010.bmp" attr="" comment="" date="1266585124" name="IDoccupancy_13Jan2010.bmp" path="IDoccupancy_13Jan2010.bmp" size="678630" stream="IDoccupancy_13Jan2010.bmp" tmpFilename="/usr/tmp/CGItemp36502" user="apalma" version="1"
META FILEATTACHMENT attachment="Forward_13Jan2010_1.bmp" attr="" comment="" date="1266588728" name="Forward_13Jan2010_1.bmp" path="Forward_13Jan2010_1.bmp" size="633510" stream="Forward_13Jan2010_1.bmp" tmpFilename="/usr/tmp/CGItemp36597" user="apalma" version="1"
META FILEATTACHMENT attachment="dt_allruns_v5.png" attr="" comment="" date="1266851861" name="dt_allruns_v5.png" path="dt_allruns_v5.png" size="7932" stream="dt_allruns_v5.png" tmpFilename="/usr/tmp/CGItemp43115" user="apalma" version="1"
Line: 346 to 353
 
META FILEATTACHMENT attachment="TGC_HR_muon_currents.png" attr="" comment="" date="1266861992" name="TGC_HR_muon_currents.png" path="TGC_HR_muon_currents.png" size="29490" stream="TGC_HR_muon_currents.png" tmpFilename="/usr/tmp/CGItemp43142" user="apalma" version="1"
META FILEATTACHMENT attachment="TGC_LR_muon_currents.png" attr="" comment="" date="1266862009" name="TGC_LR_muon_currents.png" path="TGC_LR_muon_currents.png" size="34129" stream="TGC_LR_muon_currents.png" tmpFilename="/usr/tmp/CGItemp43091" user="apalma" version="1"
META FILEATTACHMENT attachment="Forward_12Dez2009.bmp" attr="" comment="" date="1267044853" name="Forward_12Dez2009.bmp" path="Forward_12Dez2009.bmp" size="674630" stream="Forward_12Dez2009.bmp" tmpFilename="/usr/tmp/CGItemp42129" user="apalma" version="1"
Added:
>
>
META FILEATTACHMENT attachment="MBTS_LCD_AC_12Dec09_1.bmp" attr="" comment="" date="1267081476" name="MBTS_LCD_AC_12Dec09_1.bmp" path="MBTS_LCD_AC_12Dec09_1.bmp" size="688014" stream="MBTS_LCD_AC_12Dec09_1.bmp" tmpFilename="/usr/tmp/CGItemp42289" user="apalma" version="1"
META FILEATTACHMENT attachment="abort_level.png" attr="" comment="" date="1267081513" name="abort_level.png" path="abort_level.png" size="16122" stream="abort_level.png" tmpFilename="/usr/tmp/CGItemp42186" user="apalma" version="1"
META FILEATTACHMENT attachment="beam_currents.png" attr="" comment="" date="1267081595" name="beam_currents.png" path="beam_currents.png" size="27961" stream="beam_currents.png" tmpFilename="/usr/tmp/CGItemp42057" user="apalma" version="1"
META FILEATTACHMENT attachment="collision_halo_normalized.png" attr="" comment="" date="1267081644" name="collision_halo_normalized.png" path="collision_halo_normalized.png" size="24234" stream="collision_halo_normalized.png" tmpFilename="/usr/tmp/CGItemp42120" user="apalma" version="1"

Revision 242010-02-24 - AlbertoPalma

Line: 1 to 1
 
<!-- Header + table of content !-->

ATLAS Beam Backgrounds

Line: 27 to 27
 
  • normalized values (the ones sent to the LHC)
Changed:
<
<
In the next levels of the panel structure, we find history plots concerning the following subjects and monitors:
>
>
In the next levels of the tree structure, we find history plots concerning the following subjects and monitors:
  Beam Halo
  • Beam Conditions Monitor (BCM)
Line: 106 to 106
  atlas_bkg_haloAC.png
Changed:
<
<
The plot shows the hits of particles that are out-of-time, in the ATLAS BLMs during a run with cosmics. The counts are made during a period of 320 us in each side stations and are summed.
>
>
The plot shows the rate of particles that are out-of-time in the ATLAS BLMs during a run with cosmics. The time granularity at which the data is accumulated is 320 us and the what is shown is the sum of data from the stations in side A and side C.
  Monitored for BCM, MBTS and LAr: Out-of-time hits
Changed:
<
<
Monitored for BLMs: Leakage current through the junction, proportional to the local particle flux
>
>
Monitored for BLMs: Leakage current, which is proportional to the local particle flux
 Units: Hz (for BLM the Hz is equivalent to 50 uA)
Trigger requirements:
Typical 'good' levels: depends on the beam conditions
Line: 126 to 126
 Displays of the Pixel occupancy and total dead time are in preparation.

Monitored: Pixel and TRT total occupancies (1 means 100% occupancy), total SCT space points and total dead time (1 means 100% dead time)

Added:
>
>
Units: dimensionless
 Trigger requirements for SCT/TRT: any event in the beam pick-up detectors (BPTX) stream; if we are taking cosmics, no requirements are made
Typical 'good' levels for SCT/TRT: TRT occupancy ~ 0.5%; SCT space points = 100 - 500
Changed:
<
<
Typical 'warning' levels SCT/TRT: to be determined

>
>
Typical 'warning' levels SCT/TRT: to be determined
 

Forward Detectors' Hit Rates (A + C)

Forward_13Jan2010_1.bmp
Changed:
<
<
The plot shows the total hit rates for LUCID. There are two detectors installed, one in side A and the other in side C of the ATLAS detector, in the end-cap region. The A + C hit rate is a simple sum of the two individual paddle rates.
>
>
The plot shows the total hit rates for LUCID. There are two detectors installed, one in side A and the other in side C of the ATLAS detector, in the end-cap region. The A + C hit rate is a simple sum of the two individual side rates, without any external trigger or timing requirement (for this reason the signal is noisy).
 
Changed:
<
<
The hit rate is dominated by the luminosity signal when the beam conditions are "clean", as we see here. However, if the beam conditions are not optimal, the hit rate will be dominated by backgrounds, as can be seen in the following plot taken during an aperture scan.
>
>
In the absence of beam, the hit rates mostly reflect cosmic muons traversing the quartz window of the LUCID photomultiplier. Rates of a few hundred Hz, with a regular line stretch, are visible during LUCID calibration (see the plot in the ATLAS HIT RATES section, in this document). When the beam conditions are "clean", the hit rate is dominated by the luminosity, as we see here. However, if the beam conditions are not optimal, the hit rate will be dominated by backgrounds, as can be seen in the following plot taken during an aperture scan.
  forward_detectors_aperture_scan.png
Changed:
<
<
Hit rates for ZDC are equally available and are also dominated by the luminosity signal on normal beam conditions and by background events when the beam is not "clean".
>
>
Hit rates for ZDC are equally available and follow the same behaviour of the LUCID hit rates: dominated by the luminosity signal on normal beam conditions, dominated by background events when the beam is not "clean" and a regular line stretch is visible during calibration runs, but with a few Hz.
  Monitored: LUCID and ZDC total hit rates
Added:
>
>
Units: Hz
 Trigger requirement: free running (independent of the ATLAS trigger)
Typical 'good' levels: depends on the luminosity signal
Typical 'warning' levels: any signal that is much larger than the luminosity signal (more than the double of the amplitude)

ATLAS Normalized Beam Backgrounds

Added:
>
>

Collision (BKGD1, BLM) & Halo (BKGD2)

History display of BKGD1, defined as 100 * (TRT occupancy / 0.30), BKGD2, defined as 100 * (BCM Halo / Danger Level), and ATLAS BLM rates A + C. 30% is the optimized TRT occupancy at nominal LHC luminosity. The Danger Level is still to define. If BKGD1 or BKGD2 are above 50%, the beam is very "dirty"

Monitored: BKGD1, BKGD2 and ATLAS BLM rates
Units for BLM rates: Hz
Trigger requirement:
Typical 'good' levels for BKGD1 and BKGD2:
Typical 'good' levels for BLM rates:
Typical 'warning' levels for BKGD1 and BKGD2:
Typical 'warning' levels for BLM rates:

Abort Level & Dead Time

History display of Abort Level and Dead Time. The Abort Level is defined as the fraction of BCM above threshold. If the Abort Level is close to 100% we are about to abort.

Monitored: Abort Level and Dead Time
Units for Dead Time: Hz
Trigger requirement:
Typical 'good' levels:
Typical 'warning' levels:

Beam Currents & Inverse Lifetimes

History display of the two beam currents, B1 and B2, and inverse lifetimes of the beams. The beam current measurement is provided by DC current transformers (DCCT), which measure the total current (bunch and non bunch current). The inverse lifetimes of the beams are directly proportional to the beam loss, giving the indication of how fast the beam is lost.

Monitored: Beam currents and inverse lifetimes
Units for beam curresnts: *e11
Units for inverse lifetimes:
Trigger requirement:
Typical 'good' levels:
Typical 'warning' levels:

 

BEAM_HALO

BCM Halo Rates

BCM_halo_rate.png

Changed:
<
<
History display of out-of-time coincidence hits in each one of the BCM stations, side A and side C. Secondary particles from collisions will reach both BCM stations at the same time, while particles from upstream background interactions reach the nearest station 12.5 ns before the secondary particles from collisions (6 ns before collisions). So out-of-time coincidence hits are used to identify background events and in-time coincidence hits to monitor luminosity.
>
>
History display of the rate of out-of-time hits in each one of the BCM stations, side A and side C. Secondary particles from collisions will reach both BCM stations at the same time, while particles from upstream background interactions reach the nearest station 12.5 ns before the secondary particles from collisions (6 ns before collisions). So out-of-time hits are used to identify background events and in-time coincidence hits to monitor luminosity.
 
Changed:
<
<
Monitored: Out-of-time coincidence hits in the BCM
>
>
Monitored: Out-of-time hits in the BCM
Units: Hz
 Trigger requirement:
Typical 'good' levels: depends on the beam conditions
Changed:
<
<
Typical 'warning' levels: it is expected that when beam is steable, the fraction of background events will be very small, visible only on logarithmic scale when compared with signal events

>
>
Typical 'warning' levels: to define but it is expected a very small fraction of background events when the beam is "clean"

 

MBTS & LAr Halo Rates

MBTS_LAr_halo_rates.png

Changed:
<
<
History display of out-of-time coincidence hits in each one of the MBTS and LAr stations, side A and side C.
>
>
History display of the rate of out-of-time hits in each one of the MBTS and LAr stations, side A and side C.
 
Changed:
<
<
Monitored: Out-of-time coincidence hits in MBTS and LAr
>
>
Monitored: Out-of-time hits in MBTS and LAr
Units: Hz
 Trigger requirement:
Typical 'good' levels:
Typical 'warning' levels:

Line: 175 to 212
  halo_fractions.png
Changed:
<
<
History display of the fraction of out-of-time coincidence hits in BCM, MBTS and LAr. The fraction is simply the out-of-time coincidence hits divided by all the hits (out-of-time and in-time coincidence). When the beam is "clean" the fraction is expected to be extremely small.
>
>
History display of the fraction of out-of-time hits in BCM, MBTS and LAr, normalized to the total rate (out-of-time and in-time coincidence).
 
Changed:
<
<
Monitored: fraction of out-of-time coincidence hits
>
>
Monitored: fraction of out-of-time hits
Units: dimensionless (1 means 100%)
 Trigger requirement:
Typical 'good' levels:
Typical 'warning' levels:

Line: 188 to 226
  BCM_BLM_hit_rates.png
Changed:
<
<
The plot shows hit rates for each one of the MBTS stations, side A and side C. BLMs hit rates will be available in a near future.
>
>
The plot shows hit rates for each one of the MBTS stations, side A and side C, sampled at 1 Hz, without external trigger or timing requirements.
 
Changed:
<
<
Monitored: BCM and BLMs hit rates
>
>
Monitored: BCM hit rates
Units: Hz
 Trigger requirement:
Typical 'good' levels:
Typical 'warning' levels:

Line: 199 to 238
  MBTS_L1Calo_hit_rates.png
Changed:
<
<
History display of MBTS hit rates and level-1 trigger information based on the calorimeters. MBTS hit rates are dominated by luminosity, as can be seen in the following plot that shows the sum of the two single-paddle rates for MBTS:
>
>
History display of MBTS hit rates and level-1 trigger information based on the calorimeters, sampled at 1Hz, without any external trigger or timing requirement. MBTS hit rates are dominated by luminosity, as can be seen in the following plot that shows the sum of the two stations rates for MBTS:
  Hits_all_12Dec2009.bmp
Changed:
<
<
Level-1 trigger information based on the calorimeters is dominated by noise.
>
>
At the very low luminosities achieved so far, the randomly sampled L1 Calo rate is dominated by noise.
 
Changed:
<
<
Monitored: MBTS and L1Calo single-paddle rates
>
>
Monitored: MBTS and L1Calo rates
Units: Hz
 Trigger requirement:
Typical 'good' levels:
Typical 'warning' levels:

Forward Detectors

Changed:
<
<
Forward_Detectors_hit_rates.png
>
>
Forward_12Dez2009.bmp
 
Changed:
<
<
History display of single-paddle rates for LUCID and ZDC. The hit rates are dominated by the luminosity. However, they are sensitive to background when beam conditions are bad.
>
>
History display of rates for LUCID and ZDC stations. The hit rates are dominated by the luminosity. However, they are sensitive to background when beam conditions are bad.
  Monitored: LUCID and ZDC single-paddle rates
Added:
>
>
Units: Hz
 Trigger requirement: free running (independent of the ATLAS trigger)
Typical 'good' levels: depends on the luminosity signal
Typical 'warning' levels: any signal that is much larger than the luminosity signal (more than the double of the amplitude)

CALO_CURRENTS

Changed:
<
<
The amount of current that is needed to supply to the PMTs and the copper electrodes in the calorimeters is proportional to the number of charged particles detected. So we can try to use the supplied currents to monitor beam conditions.
>
>
The amount of current that is needed to supply to the PMTs and the electrodes of the LAr calorimeter is proportional to the number of charged particles detected. So we can try to use the supplied currents to monitor beam conditions.
  In the 2009 run was not seen any sensibility from the calorimeter currents to the beam conditions.
Line: 298 to 339
 
META FILEATTACHMENT attachment="MBTS_LAr_halo_rates.png" attr="" comment="" date="1266858185" name="MBTS_LAr_halo_rates.png" path="MBTS_LAr_halo_rates.png" size="22457" stream="MBTS_LAr_halo_rates.png" tmpFilename="/usr/tmp/CGItemp43007" user="apalma" version="1"
META FILEATTACHMENT attachment="halo_fractions.png" attr="" comment="" date="1266859244" name="halo_fractions.png" path="halo_fractions.png" size="20188" stream="halo_fractions.png" tmpFilename="/usr/tmp/CGItemp43014" user="apalma" version="1"
META FILEATTACHMENT attachment="BCM_BLM_hit_rates.png" attr="" comment="" date="1266859875" name="BCM_BLM_hit_rates.png" path="BCM_BLM_hit_rates.png" size="20133" stream="BCM_BLM_hit_rates.png" tmpFilename="/usr/tmp/CGItemp43122" user="apalma" version="1"
Deleted:
<
<
META FILEATTACHMENT attachment="MBTS_L1Calo_hit_rates.png" attr="" comment="" date="1266860517" name="MBTS_L1Calo_hit_rates.png" path="MBTS_L1Calo_hit_rates.png" size="23974" stream="MBTS_L1Calo_hit_rates.png" tmpFilename="/usr/tmp/CGItemp43188" user="apalma" version="1"
META FILEATTACHMENT attachment="Forward_Detectors_hit_rates.png" attr="" comment="" date="1266860625" name="Forward_Detectors_hit_rates.png" path="Forward_Detectors_hit_rates.png" size="24090" stream="Forward_Detectors_hit_rates.png" tmpFilename="/usr/tmp/CGItemp43082" user="apalma" version="1"
 
META FILEATTACHMENT attachment="tile_currents.png" attr="" comment="" date="1266861439" name="tile_currents.png" path="tile_currents.png" size="23161" stream="tile_currents.png" tmpFilename="/usr/tmp/CGItemp43169" user="apalma" version="1"
META FILEATTACHMENT attachment="MBTS_currents.png" attr="" comment="" date="1266861457" name="MBTS_currents.png" path="MBTS_currents.png" size="31779" stream="MBTS_currents.png" tmpFilename="/usr/tmp/CGItemp43057" user="apalma" version="1"
META FILEATTACHMENT attachment="FCAL_currents.png" attr="" comment="" date="1266861477" name="FCAL_currents.png" path="FCAL_currents.png" size="24290" stream="FCAL_currents.png" tmpFilename="/usr/tmp/CGItemp43109" user="apalma" version="1"
META FILEATTACHMENT attachment="MDT_muon_currents.png" attr="" comment="" date="1266861967" name="MDT_muon_currents.png" path="MDT_muon_currents.png" size="25961" stream="MDT_muon_currents.png" tmpFilename="/usr/tmp/CGItemp43044" user="apalma" version="1"
META FILEATTACHMENT attachment="TGC_HR_muon_currents.png" attr="" comment="" date="1266861992" name="TGC_HR_muon_currents.png" path="TGC_HR_muon_currents.png" size="29490" stream="TGC_HR_muon_currents.png" tmpFilename="/usr/tmp/CGItemp43142" user="apalma" version="1"
META FILEATTACHMENT attachment="TGC_LR_muon_currents.png" attr="" comment="" date="1266862009" name="TGC_LR_muon_currents.png" path="TGC_LR_muon_currents.png" size="34129" stream="TGC_LR_muon_currents.png" tmpFilename="/usr/tmp/CGItemp43091" user="apalma" version="1"
Added:
>
>
META FILEATTACHMENT attachment="Forward_12Dez2009.bmp" attr="" comment="" date="1267044853" name="Forward_12Dez2009.bmp" path="Forward_12Dez2009.bmp" size="674630" stream="Forward_12Dez2009.bmp" tmpFilename="/usr/tmp/CGItemp42129" user="apalma" version="1"

Revision 232010-02-24 - AlbertoPalma

Line: 1 to 1
 
<!-- Header + table of content !-->

ATLAS Beam Backgrounds

Line: 15 to 15
  Different monitoring tools are available to provide checks on the beam backgrounds and the quality of the data collected:
Changed:
<
<
1) Beam crossing identifier (BCID) blind background displays
>
>
1) Beam crossing identifier (BCID)-blind background displays
 
Changed:
<
<
2) Bunch by bunch beam conditions diagnostic displays (they will become active in the near future and will be explained then)
>
>
2) Bunch-by-bunch beam conditions diagnostic displays (they will become active in the near future and will be explained then)
 
Changed:
<
<

BCID blind background displays

>
>

BCID-blind background displays

 
Changed:
<
<
The BCID blind background displays are part of the Detector Control System (DCS) and are organized hierarchically in a panels structure. In the top level panel "ATLAS Backgrounds" there are two tabs with background history plots (known in PVSS jargon as "trending plots"), placed in this prominent position for its relevance in the current operating conditions, with:
>
>
The BCID-blind background displays are part of the Detector Control System (DCS) and are organized hierarchically in a tree structure. In the top level panel "ATLAS Backgrounds" there are two tabs with background history plots (known in PVSS jargon as "trending plots"), placed in this prominent position for its relevance in the current operating conditions, with:
 
  • absolute values
Line: 57 to 57
 
  • Forward Monitored Drift Tubes (MDT) chambers
  • Thin Gap Chambers (TGC)
Added:
>
>

Timing and bunch-by-bunch background diagnostics

To explain in a near future.

 

Path to the panels

To see the beam background panels on the LBCF desk computer screens follow the instructions:

Line: 84 to 88
 
  • In each of those navigation panels are sub-branches and we can navigate further down
  • If the "No panel available" appears, this means that the display is under development, being available soon
Changed:
<
<

Detailed description of beam conditions history displays

>
>

Detailed description of beam-condition history displays

 
Changed:
<
<

ATL_BACKGROUNDS (Absolute Values)

>
>

ATLAS BACKGROUNDS

In every display the y axis are shown simultaneously in a Grey box and can be modified by the roller button of the mouse. The x axis can present different time ranges.

 

Halo (A + C)

Changed:
<
<
Time of flight measurements with two detector stations, one at each side of the ATLAS detector, are used to distinguish between interactions and background (beam gas, halo, TAS collimator scrapping). Particles originated in the interaction point arrive almost at the same time at the two stations, and therefore are in-time coincidence, and particles from the background are out-of-time coincidence, since they arrive first to one of the stations.
>
>
Time of flight measurements with two detector stations, one at each side of the ATLAS detector, are used to distinguish between interactions and background (beam gas, halo, scraping on the TCT collimators). Particles originating in the interaction point arrive at the same time at the two stations, and therefore form an in-time coincidence, and particles from the background are out-of-time, since they reach the station on the incoming beam side earlier then the interaction point.
 
Changed:
<
<
The following plot is a distribution of time difference between hit on side A (z>0) and hit on side C (z<0) in the same event, in the BCM stations, during the 2009 run. Collisions as well as background due to beam 1 and beam 2 are clearly visible.
>
>
The following plot is a distribution of time difference between hits on side A (z>0) and hits on side C (z<0) in the same event, in the BCM stations, during the 2009 run. Collisions as well as background due to beam 1 and beam 2 are clearly visible.
  dt_allruns_v5.png
Changed:
<
<
Other subdetectors also have this ability to distinguish between signal and background.
>
>
Other subdetectors (MBTS, LAr, BLM) also have this ability to distinguish between signal and background; these plots are available at the LBCF desk as part of the timing and bunch-by-bunch diagnostics, discussed later in this document.
  atlas_bkg_haloAC.png
Changed:
<
<
The plot shows the hits of particles that are out-of-time coincidence, in the ATLAS BLMs during a run with cosmics.
>
>
The plot shows the hits of particles that are out-of-time, in the ATLAS BLMs during a run with cosmics. The counts are made during a period of 320 us in each side stations and are summed.
 
Changed:
<
<
Monitored: Out-of-time coincidence hits in the BCM, MBTS, BLMs and LAr
>
>
Monitored for BCM, MBTS and LAr: Out-of-time hits
Monitored for BLMs: Leakage current through the junction, proportional to the local particle flux
Units: Hz (for BLM the Hz is equivalent to 50 uA)
 Trigger requirements:
Typical 'good' levels: depends on the beam conditions
Changed:
<
<
Typical 'warning' levels: it is expected that when beam is steable, the fraction of background events will be very small, visible only on logarithmic scale when compared with signal events

>
>
Typical 'warning' levels: to define but it is expected a very small fraction of background events when the beam is "clean"

 

ID Occupancies & Dead Time

IDoccupancy_13Jan2010.bmp
The plot shows, as different colour trend lines, the TRT occupancy, averaged over all straws, and the total SCT space points, built from cluster pairs from the opposite sides of a given module, or from separate modules which overlap in eta or in phi. The TRT occupancy is counted by looking at straws with long Time Over Threshold, which reduces the noise, by almost two orders of magnitude, while still being sensitive to any particle fluxes.
Changed:
<
<
The fluctuations observed, in this case, are due essentially to beam halo fluctuations. This plot was made during an aperture test, when the beam is moved to near the edge of the copper collimator (TAS) that protects ATLAS. Many particles arise from the interaction of the beam with the collimator.
>
>
The fluctuations observed, in this case, are due essentially to beam halo fluctuations.
 
Changed:
<
<
This history plot is updated every second. The y axis are shown simultaneously in a Grey box and can be modified by the roller button of the mouse. The x axis can present different time ranges.
>
>
This history plot is updated every second. Every entry is an average over 10 events.
  Displays of the Pixel occupancy and total dead time are in preparation.
Changed:
<
<
Monitored: Pixel and TRT total occupancies, total SCT space points and total dead time
>
>
Monitored: Pixel and TRT total occupancies (1 means 100% occupancy), total SCT space points and total dead time (1 means 100% dead time)
 Trigger requirements for SCT/TRT: any event in the beam pick-up detectors (BPTX) stream; if we are taking cosmics, no requirements are made
Typical 'good' levels for SCT/TRT: TRT occupancy ~ 0.5%; SCT space points = 100 - 500
Typical 'warning' levels SCT/TRT: to be determined

Line: 137 to 145
 Typical 'good' levels: depends on the luminosity signal
Typical 'warning' levels: any signal that is much larger than the luminosity signal (more than the double of the amplitude)

Added:
>
>

ATLAS Normalized Beam Backgrounds

 

BEAM_HALO

Line: 274 to 283
 Typical 'good' levels:
Typical 'warning' levels:

Changed:
<
<

Detailed description of bunch by bunch beam conditions history displays

>
>

Detailed description of timing and bunch-by-bunch beam conditions diagnostics

  To explain in a near future.

Revision 222010-02-23 - AlbertoPalma

Line: 1 to 1
 
<!-- Header + table of content !-->

ATLAS Beam Backgrounds

Line: 92 to 92
  Time of flight measurements with two detector stations, one at each side of the ATLAS detector, are used to distinguish between interactions and background (beam gas, halo, TAS collimator scrapping). Particles originated in the interaction point arrive almost at the same time at the two stations, and therefore are in-time coincidence, and particles from the background are out-of-time coincidence, since they arrive first to one of the stations.
Changed:
<
<
The following plot is a distribution of time difference between hit on side A and hit on side C in the same event, in the BCM stations, during the 2009 run. Collisions as well as background due to beam 1 and beam 2 are clearly visible.
>
>
The following plot is a distribution of time difference between hit on side A (z>0) and hit on side C (z<0) in the same event, in the BCM stations, during the 2009 run. Collisions as well as background due to beam 1 and beam 2 are clearly visible.
  dt_allruns_v5.png
Line: 130 to 130
  forward_detectors_aperture_scan.png
Changed:
<
<
Hit rates for ZDC are equally available and are also dominated by the luminosity signal on normal beam conditions.
>
>
Hit rates for ZDC are equally available and are also dominated by the luminosity signal on normal beam conditions and by background events when the beam is not "clean".
  Monitored: LUCID and ZDC total hit rates
Trigger requirement: free running (independent of the ATLAS trigger)
Line: 144 to 144
  BCM_halo_rate.png
Added:
>
>
History display of out-of-time coincidence hits in each one of the BCM stations, side A and side C. Secondary particles from collisions will reach both BCM stations at the same time, while particles from upstream background interactions reach the nearest station 12.5 ns before the secondary particles from collisions (6 ns before collisions). So out-of-time coincidence hits are used to identify background events and in-time coincidence hits to monitor luminosity.
 Monitored: Out-of-time coincidence hits in the BCM
Trigger requirement:
Typical 'good' levels: depends on the beam conditions
Line: 153 to 155
  MBTS_LAr_halo_rates.png
Added:
>
>
History display of out-of-time coincidence hits in each one of the MBTS and LAr stations, side A and side C.
 Monitored: Out-of-time coincidence hits in MBTS and LAr
Trigger requirement:
Typical 'good' levels:
Line: 162 to 166
  halo_fractions.png
Added:
>
>
History display of the fraction of out-of-time coincidence hits in BCM, MBTS and LAr. The fraction is simply the out-of-time coincidence hits divided by all the hits (out-of-time and in-time coincidence). When the beam is "clean" the fraction is expected to be extremely small.
 Monitored: fraction of out-of-time coincidence hits
Trigger requirement:
Typical 'good' levels:
Line: 173 to 179
  BCM_BLM_hit_rates.png
Changed:
<
<
Hits_all_12Dec2009.bmp
The plot shows hit rates (the sum of the two single-paddle rates) for MBTS. We could also see hit rates for BCM, ATLAS BLMs and level-1 trigger information based on the calorimeters.

Monitored:
>
>
The plot shows hit rates for each one of the MBTS stations, side A and side C. BLMs hit rates will be available in a near future.

Monitored: BCM and BLMs hit rates

 Trigger requirement:
Typical 'good' levels:
Typical 'warning' levels:

Changed:
<
<

MBTS & L1Calo

>
>

MBTS & L1Calo

  MBTS_L1Calo_hit_rates.png
Changed:
<
<
Monitored:
>
>
History display of MBTS hit rates and level-1 trigger information based on the calorimeters. MBTS hit rates are dominated by luminosity, as can be seen in the following plot that shows the sum of the two single-paddle rates for MBTS:

Hits_all_12Dec2009.bmp

Level-1 trigger information based on the calorimeters is dominated by noise.

Monitored: MBTS and L1Calo single-paddle rates

 Trigger requirement:
Typical 'good' levels:
Typical 'warning' levels:

Line: 193 to 205
  Forward_Detectors_hit_rates.png
Changed:
<
<
Monitored:
Trigger requirement:
Typical 'good' levels:
Typical 'warning' levels:

>
>
History display of single-paddle rates for LUCID and ZDC. The hit rates are dominated by the luminosity. However, they are sensitive to background when beam conditions are bad.

Monitored: LUCID and ZDC single-paddle rates
Trigger requirement: free running (independent of the ATLAS trigger)
Typical 'good' levels: depends on the luminosity signal
Typical 'warning' levels: any signal that is much larger than the luminosity signal (more than the double of the amplitude)

 

CALO_CURRENTS

Added:
>
>
The amount of current that is needed to supply to the PMTs and the copper electrodes in the calorimeters is proportional to the number of charged particles detected. So we can try to use the supplied currents to monitor beam conditions.

In the 2009 run was not seen any sensibility from the calorimeter currents to the beam conditions.

 

Tile

tile_currents.png

Revision 212010-02-22 - AlbertoPalma

Line: 1 to 1
 
<!-- Header + table of content !-->

ATLAS Beam Backgrounds

Line: 33 to 33
 
  • Beam Conditions Monitor (BCM)
  • Liquid Argon calorimeters (LAr)
  • Minimum Bias Trigger Scintillator (MBTS)
Added:
>
>
  • ATLAS Beam Loss Monitors (BLM)
  Hit rates
  • Beam Conditions Monitor (BCM)
Line: 85 to 86
 

Detailed description of beam conditions history displays

Changed:
<
<

ATL_BACKGROUNDS

>
>

ATL_BACKGROUNDS (Absolute Values)

Halo (A + C)

Time of flight measurements with two detector stations, one at each side of the ATLAS detector, are used to distinguish between interactions and background (beam gas, halo, TAS collimator scrapping). Particles originated in the interaction point arrive almost at the same time at the two stations, and therefore are in-time coincidence, and particles from the background are out-of-time coincidence, since they arrive first to one of the stations.

The following plot is a distribution of time difference between hit on side A and hit on side C in the same event, in the BCM stations, during the 2009 run. Collisions as well as background due to beam 1 and beam 2 are clearly visible.

dt_allruns_v5.png

Other subdetectors also have this ability to distinguish between signal and background.

 
Changed:
<
<

ID Occupancies and Dead Time

>
>
atlas_bkg_haloAC.png

The plot shows the hits of particles that are out-of-time coincidence, in the ATLAS BLMs during a run with cosmics.

Monitored: Out-of-time coincidence hits in the BCM, MBTS, BLMs and LAr
Trigger requirements:
Typical 'good' levels: depends on the beam conditions
Typical 'warning' levels: it is expected that when beam is steable, the fraction of background events will be very small, visible only on logarithmic scale when compared with signal events

ID Occupancies & Dead Time

  IDoccupancy_13Jan2010.bmp
The plot shows, as different colour trend lines, the TRT occupancy, averaged over all straws, and the total SCT space points, built from cluster pairs from the opposite sides of a given module, or from separate modules which overlap in eta or in phi. The TRT occupancy is counted by looking at straws with long Time Over Threshold, which reduces the noise, by almost two orders of magnitude, while still being sensitive to any particle fluxes.
Line: 102 to 122
 Typical 'good' levels for SCT/TRT: TRT occupancy ~ 0.5%; SCT space points = 100 - 500
Typical 'warning' levels SCT/TRT: to be determined

Changed:
<
<

Forward Detectors Hit Rates

>
>

Forward Detectors' Hit Rates (A + C)

  Forward_13Jan2010_1.bmp
The plot shows the total hit rates for LUCID. There are two detectors installed, one in side A and the other in side C of the ATLAS detector, in the end-cap region. The A + C hit rate is a simple sum of the two individual paddle rates.
Changed:
<
<
The hit rate is dominated by the luminosity signal when the beam conditions are "clean", as we see here. However, if the beam conditions are not optimal, the hit rate will be dominated by backgrounds.
>
>
The hit rate is dominated by the luminosity signal when the beam conditions are "clean", as we see here. However, if the beam conditions are not optimal, the hit rate will be dominated by backgrounds, as can be seen in the following plot taken during an aperture scan.

forward_detectors_aperture_scan.png

  Hit rates for ZDC are equally available and are also dominated by the luminosity signal on normal beam conditions.
Line: 118 to 140
 

BEAM_HALO

Added:
>
>

BCM Halo Rates

BCM_halo_rate.png

Monitored: Out-of-time coincidence hits in the BCM
Trigger requirement:
Typical 'good' levels: depends on the beam conditions
Typical 'warning' levels: it is expected that when beam is steable, the fraction of background events will be very small, visible only on logarithmic scale when compared with signal events

MBTS & LAr Halo Rates

MBTS_LAr_halo_rates.png

Monitored: Out-of-time coincidence hits in MBTS and LAr
Trigger requirement:
Typical 'good' levels:
Typical 'warning' levels:

Halo Fractions (A + C / All)

halo_fractions.png

Monitored: fraction of out-of-time coincidence hits
Trigger requirement:
Typical 'good' levels:
Typical 'warning' levels:

 

ATLAS HIT RATES

Added:
>
>

BCM & BLM

BCM_BLM_hit_rates.png

  Hits_all_12Dec2009.bmp
The plot shows hit rates (the sum of the two single-paddle rates) for MBTS. We could also see hit rates for BCM, ATLAS BLMs and level-1 trigger information based on the calorimeters.

Monitored:
Line: 127 to 180
 Typical 'good' levels:
Typical 'warning' levels:

Added:
>
>

MBTS & L1Calo

MBTS_L1Calo_hit_rates.png

Monitored:
Trigger requirement:
Typical 'good' levels:
Typical 'warning' levels:

Forward Detectors

Forward_Detectors_hit_rates.png

Monitored:
Trigger requirement:
Typical 'good' levels:
Typical 'warning' levels:

 

CALO_CURRENTS

Added:
>
>

Tile

tile_currents.png

Monitored:
Trigger requirement:
Typical 'good' levels:
Typical 'warning' levels:

MBTS

MBTS_currents.png

Monitored:
Trigger requirement:
Typical 'good' levels:
Typical 'warning' levels:

FCAL

FCAL_currents.png

Monitored:
Trigger requirement:
Typical 'good' levels:
Typical 'warning' levels:

 

MUON_CURRENTS

Added:
>
>

Forward MDT's

MDT_muon_currents.png

Monitored:
Trigger requirement:
Typical 'good' levels:
Typical 'warning' levels:

TGC HR

TGC_HR_muon_currents.png

Monitored:
Trigger requirement:
Typical 'good' levels:
Typical 'warning' levels:

TGC LR

TGC_LR_muon_currents.png

Monitored:
Trigger requirement:
Typical 'good' levels:
Typical 'warning' levels:

 

Detailed description of bunch by bunch beam conditions history displays

To explain in a near future.

Line: 141 to 264
 
META FILEATTACHMENT attachment="Hits_all_12Dec2009.bmp" attr="" comment="" date="1266182366" name="Hits_all_12Dec2009.bmp" path="Hits_all_12Dec2009.bmp" size="683694" stream="Hits_all_12Dec2009.bmp" tmpFilename="/usr/tmp/CGItemp25222" user="apalma" version="1"
META FILEATTACHMENT attachment="IDoccupancy_13Jan2010.bmp" attr="" comment="" date="1266585124" name="IDoccupancy_13Jan2010.bmp" path="IDoccupancy_13Jan2010.bmp" size="678630" stream="IDoccupancy_13Jan2010.bmp" tmpFilename="/usr/tmp/CGItemp36502" user="apalma" version="1"
META FILEATTACHMENT attachment="Forward_13Jan2010_1.bmp" attr="" comment="" date="1266588728" name="Forward_13Jan2010_1.bmp" path="Forward_13Jan2010_1.bmp" size="633510" stream="Forward_13Jan2010_1.bmp" tmpFilename="/usr/tmp/CGItemp36597" user="apalma" version="1"
Added:
>
>
META FILEATTACHMENT attachment="dt_allruns_v5.png" attr="" comment="" date="1266851861" name="dt_allruns_v5.png" path="dt_allruns_v5.png" size="7932" stream="dt_allruns_v5.png" tmpFilename="/usr/tmp/CGItemp43115" user="apalma" version="1"
META FILEATTACHMENT attachment="atlas_bkg_haloAC.png" attr="" comment="" date="1266855775" name="atlas_bkg_haloAC.png" path="atlas_bkg_haloAC.png" size="25450" stream="atlas_bkg_haloAC.png" tmpFilename="/usr/tmp/CGItemp43163" user="apalma" version="1"
META FILEATTACHMENT attachment="forward_detectors_aperture_scan.png" attr="" comment="" date="1266857804" name="forward_detectors_aperture_scan.png" path="forward_detectors_aperture_scan.png" size="6626" stream="forward_detectors_aperture_scan.png" tmpFilename="/usr/tmp/CGItemp43116" user="apalma" version="1"
META FILEATTACHMENT attachment="BCM_halo_rate.png" attr="" comment="" date="1266858021" name="BCM_halo_rate.png" path="BCM_halo_rate.png" size="16829" stream="BCM_halo_rate.png" tmpFilename="/usr/tmp/CGItemp43063" user="apalma" version="1"
META FILEATTACHMENT attachment="MBTS_LAr_halo_rates.png" attr="" comment="" date="1266858185" name="MBTS_LAr_halo_rates.png" path="MBTS_LAr_halo_rates.png" size="22457" stream="MBTS_LAr_halo_rates.png" tmpFilename="/usr/tmp/CGItemp43007" user="apalma" version="1"
META FILEATTACHMENT attachment="halo_fractions.png" attr="" comment="" date="1266859244" name="halo_fractions.png" path="halo_fractions.png" size="20188" stream="halo_fractions.png" tmpFilename="/usr/tmp/CGItemp43014" user="apalma" version="1"
META FILEATTACHMENT attachment="BCM_BLM_hit_rates.png" attr="" comment="" date="1266859875" name="BCM_BLM_hit_rates.png" path="BCM_BLM_hit_rates.png" size="20133" stream="BCM_BLM_hit_rates.png" tmpFilename="/usr/tmp/CGItemp43122" user="apalma" version="1"
META FILEATTACHMENT attachment="MBTS_L1Calo_hit_rates.png" attr="" comment="" date="1266860517" name="MBTS_L1Calo_hit_rates.png" path="MBTS_L1Calo_hit_rates.png" size="23974" stream="MBTS_L1Calo_hit_rates.png" tmpFilename="/usr/tmp/CGItemp43188" user="apalma" version="1"
META FILEATTACHMENT attachment="Forward_Detectors_hit_rates.png" attr="" comment="" date="1266860625" name="Forward_Detectors_hit_rates.png" path="Forward_Detectors_hit_rates.png" size="24090" stream="Forward_Detectors_hit_rates.png" tmpFilename="/usr/tmp/CGItemp43082" user="apalma" version="1"
META FILEATTACHMENT attachment="tile_currents.png" attr="" comment="" date="1266861439" name="tile_currents.png" path="tile_currents.png" size="23161" stream="tile_currents.png" tmpFilename="/usr/tmp/CGItemp43169" user="apalma" version="1"
META FILEATTACHMENT attachment="MBTS_currents.png" attr="" comment="" date="1266861457" name="MBTS_currents.png" path="MBTS_currents.png" size="31779" stream="MBTS_currents.png" tmpFilename="/usr/tmp/CGItemp43057" user="apalma" version="1"
META FILEATTACHMENT attachment="FCAL_currents.png" attr="" comment="" date="1266861477" name="FCAL_currents.png" path="FCAL_currents.png" size="24290" stream="FCAL_currents.png" tmpFilename="/usr/tmp/CGItemp43109" user="apalma" version="1"
META FILEATTACHMENT attachment="MDT_muon_currents.png" attr="" comment="" date="1266861967" name="MDT_muon_currents.png" path="MDT_muon_currents.png" size="25961" stream="MDT_muon_currents.png" tmpFilename="/usr/tmp/CGItemp43044" user="apalma" version="1"
META FILEATTACHMENT attachment="TGC_HR_muon_currents.png" attr="" comment="" date="1266861992" name="TGC_HR_muon_currents.png" path="TGC_HR_muon_currents.png" size="29490" stream="TGC_HR_muon_currents.png" tmpFilename="/usr/tmp/CGItemp43142" user="apalma" version="1"
META FILEATTACHMENT attachment="TGC_LR_muon_currents.png" attr="" comment="" date="1266862009" name="TGC_LR_muon_currents.png" path="TGC_LR_muon_currents.png" size="34129" stream="TGC_LR_muon_currents.png" tmpFilename="/usr/tmp/CGItemp43091" user="apalma" version="1"

Revision 202010-02-19 - AlbertoPalma

Line: 1 to 1
 
<!-- Header + table of content !-->

ATLAS Beam Backgrounds

Line: 86 to 86
 

Detailed description of beam conditions history displays

ATL_BACKGROUNDS

Deleted:
<
<
IDoccupancy_14Dec2009.bmp
The plot shows, as different colour trend lines, the TRT occupancy, averaged over all straws, and the total SCT space points, built from cluster pairs from the opposite sides of a given module, or from separate modules which overlap in eta or in phi. The fluctuations observed, in this case, are due essentially to beam halo fluctuations. The plot is updated every second. The y axis are shown simultaneously in a Grey box and can be modified by the roller button of the mouse. The x axis can present different time ranges.
Displays of the Pixel occupancy and total dead time are in preparation.

Monitored: Pixel and TRT total occupancies, total SCT space points and total dead time
Trigger requirement:
Typical 'good' levels:
Typical 'warning' levels:

 
Changed:
<
<
Forward_14Dec2009.bmp
The plot shows hit rates for LUCID. We could also see hit rates for ZDC.

Monitored:
Trigger requirement:
Typical 'good' levels:
Typical 'warning' levels:

>
>

ID Occupancies and Dead Time

IDoccupancy_13Jan2010.bmp
The plot shows, as different colour trend lines, the TRT occupancy, averaged over all straws, and the total SCT space points, built from cluster pairs from the opposite sides of a given module, or from separate modules which overlap in eta or in phi. The TRT occupancy is counted by looking at straws with long Time Over Threshold, which reduces the noise, by almost two orders of magnitude, while still being sensitive to any particle fluxes.

The fluctuations observed, in this case, are due essentially to beam halo fluctuations. This plot was made during an aperture test, when the beam is moved to near the edge of the copper collimator (TAS) that protects ATLAS. Many particles arise from the interaction of the beam with the collimator.

This history plot is updated every second. The y axis are shown simultaneously in a Grey box and can be modified by the roller button of the mouse. The x axis can present different time ranges.

Displays of the Pixel occupancy and total dead time are in preparation.

Monitored: Pixel and TRT total occupancies, total SCT space points and total dead time
Trigger requirements for SCT/TRT: any event in the beam pick-up detectors (BPTX) stream; if we are taking cosmics, no requirements are made
Typical 'good' levels for SCT/TRT: TRT occupancy ~ 0.5%; SCT space points = 100 - 500
Typical 'warning' levels SCT/TRT: to be determined

Forward Detectors Hit Rates

Forward_13Jan2010_1.bmp
The plot shows the total hit rates for LUCID. There are two detectors installed, one in side A and the other in side C of the ATLAS detector, in the end-cap region. The A + C hit rate is a simple sum of the two individual paddle rates.

The hit rate is dominated by the luminosity signal when the beam conditions are "clean", as we see here. However, if the beam conditions are not optimal, the hit rate will be dominated by backgrounds.

Hit rates for ZDC are equally available and are also dominated by the luminosity signal on normal beam conditions.

Monitored: LUCID and ZDC total hit rates
Trigger requirement: free running (independent of the ATLAS trigger)
Typical 'good' levels: depends on the luminosity signal
Typical 'warning' levels: any signal that is much larger than the luminosity signal (more than the double of the amplitude)

 

BEAM_HALO

Line: 124 to 138
 To explain in a near future.

META FILEATTACHMENT attachment="button.png" attr="" comment="" date="1266090398" name="button.png" path="button.png" size="2311" stream="button.png" tmpFilename="/usr/tmp/CGItemp24804" user="apalma" version="1"
Deleted:
<
<
META FILEATTACHMENT attachment="IDoccupancy_14Dec2009.bmp" attr="" comment="" date="1266181016" name="IDoccupancy_14Dec2009.bmp" path="IDoccupancy_14Dec2009.bmp" size="688014" stream="IDoccupancy_14Dec2009.bmp" tmpFilename="/usr/tmp/CGItemp25279" user="apalma" version="1"
 
META FILEATTACHMENT attachment="Hits_all_12Dec2009.bmp" attr="" comment="" date="1266182366" name="Hits_all_12Dec2009.bmp" path="Hits_all_12Dec2009.bmp" size="683694" stream="Hits_all_12Dec2009.bmp" tmpFilename="/usr/tmp/CGItemp25222" user="apalma" version="1"
Changed:
<
<
META FILEATTACHMENT attachment="Forward_14Dec2009.bmp" attr="" comment="" date="1266244444" name="Forward_14Dec2009.bmp" path="Forward_14Dec2009.bmp" size="642674" stream="Forward_14Dec2009.bmp" tmpFilename="/usr/tmp/CGItemp25736" user="apalma" version="1"
>
>
META FILEATTACHMENT attachment="IDoccupancy_13Jan2010.bmp" attr="" comment="" date="1266585124" name="IDoccupancy_13Jan2010.bmp" path="IDoccupancy_13Jan2010.bmp" size="678630" stream="IDoccupancy_13Jan2010.bmp" tmpFilename="/usr/tmp/CGItemp36502" user="apalma" version="1"
META FILEATTACHMENT attachment="Forward_13Jan2010_1.bmp" attr="" comment="" date="1266588728" name="Forward_13Jan2010_1.bmp" path="Forward_13Jan2010_1.bmp" size="633510" stream="Forward_13Jan2010_1.bmp" tmpFilename="/usr/tmp/CGItemp36597" user="apalma" version="1"

Revision 192010-02-19 - AlbertoPalma

Line: 1 to 1
 
<!-- Header + table of content !-->

ATLAS Beam Backgrounds

Line: 15 to 15
  Different monitoring tools are available to provide checks on the beam backgrounds and the quality of the data collected:
Changed:
<
<
1) Blind background displays (those referred in this Twiki page)
>
>
1) Beam crossing identifier (BCID) blind background displays
 
Changed:
<
<
2) Bunch by bunch and timing beam conditions diagnostic displays (they will become active in the near future and will be explained then)
>
>
2) Bunch by bunch beam conditions diagnostic displays (they will become active in the near future and will be explained then)
 
Changed:
<
<

DCS background displays

>
>

BCID blind background displays

 
Changed:
<
<
The blind background displays are part of the Detector Control System (DCS). There are two levels of information in them:
>
>
The BCID blind background displays are part of the Detector Control System (DCS) and are organized hierarchically in a panels structure. In the top level panel "ATLAS Backgrounds" there are two tabs with background history plots (known in PVSS jargon as "trending plots"), placed in this prominent position for its relevance in the current operating conditions, with:
 
  • absolute values
Changed:
<
<
  • normalized values (the ones sent to the machine)
>
>
  • normalized values (the ones sent to the LHC)
 
Changed:
<
<
Histograms are produced and presented in different panels as a function of time. These panels are organized hierarchically and they concern the following subjects and monitors:
>
>
In the next levels of the panel structure, we find history plots concerning the following subjects and monitors:
  Beam Halo
  • Beam Conditions Monitor (BCM)
Line: 72 to 72
  2) The ATL_BACKGROUNDS navigation panel:
  • Click on the “ATL_BACKGROUNDS” navigation panel to get information on the "Beam Halo", "ID Occupancies & Dead Time" and "Forward Detectors Hit Rates"
Changed:
<
<
  • A button like this button.png on the right side above the histograms, allows to commute between absolute and normalized values
>
>
  • A button like this button.png on the right side above the history plots, allows to commute between absolute and normalized values
 
  • The ATL_BACKGROUNDS brings up the following navigation panels:
    -- BEAM_HALO
    -- ATLAS HIT RATES
Line: 80 to 80
  -- MUON_CURRENTS

3) Explore each one of these new navigation panels

Added:
>
>
  • In each of those navigation panels are sub-branches and we can navigate further down
  • If the "No panel available" appears, this means that the display is under development, being available soon
 
Changed:
<
<

Plots

>
>

Detailed description of beam conditions history displays

 

ATL_BACKGROUNDS

IDoccupancy_14Dec2009.bmp
The plot shows, as different colour trend lines, the TRT occupancy, averaged over all straws, and the total SCT space points, built from cluster pairs from the opposite sides of a given module, or from separate modules which overlap in eta or in phi. The fluctuations observed, in this case, are due essentially to beam halo fluctuations. The plot is updated every second. The y axis are shown simultaneously in a Grey box and can be modified by the roller button of the mouse. The x axis can present different time ranges.
Changed:
<
<
There is also the possibility to see the Pixel occupancy and total dead time for the Inner Detector (ID).

Monitored: Pixel and TRT total occupancies, total SCT space points and ID dead time
>
>
Displays of the Pixel occupancy and total dead time are in preparation.

Monitored: Pixel and TRT total occupancies, total SCT space points and total dead time
 Trigger requirement:
Typical 'good' levels:
Typical 'warning' levels:

Line: 117 to 119
 

MUON_CURRENTS

Added:
>
>

Detailed description of bunch by bunch beam conditions history displays

To explain in a near future.

 
META FILEATTACHMENT attachment="button.png" attr="" comment="" date="1266090398" name="button.png" path="button.png" size="2311" stream="button.png" tmpFilename="/usr/tmp/CGItemp24804" user="apalma" version="1"
META FILEATTACHMENT attachment="IDoccupancy_14Dec2009.bmp" attr="" comment="" date="1266181016" name="IDoccupancy_14Dec2009.bmp" path="IDoccupancy_14Dec2009.bmp" size="688014" stream="IDoccupancy_14Dec2009.bmp" tmpFilename="/usr/tmp/CGItemp25279" user="apalma" version="1"
META FILEATTACHMENT attachment="Hits_all_12Dec2009.bmp" attr="" comment="" date="1266182366" name="Hits_all_12Dec2009.bmp" path="Hits_all_12Dec2009.bmp" size="683694" stream="Hits_all_12Dec2009.bmp" tmpFilename="/usr/tmp/CGItemp25222" user="apalma" version="1"

Revision 182010-02-16 - AlbertoPalma

Line: 1 to 1
 
<!-- Header + table of content !-->

ATLAS Beam Backgrounds

Line: 85 to 85
 

ATL_BACKGROUNDS

IDoccupancy_14Dec2009.bmp
Changed:
<
<
The plot shows the TRT occupancy, averaged over all straws, and the total SCT space points, built from cluster pairs from the opposite sides of a given module, or from separate modules which overlap in eta or in phi. The fluctuations observed, in this case, are due essentially to beam halo fluctuations. The plot is updated every minute. The y axis are shown simultaneously in a Grey box and can be modified by the roller button of the mouse. The x axis can present different time ranges.
>
>
The plot shows, as different colour trend lines, the TRT occupancy, averaged over all straws, and the total SCT space points, built from cluster pairs from the opposite sides of a given module, or from separate modules which overlap in eta or in phi. The fluctuations observed, in this case, are due essentially to beam halo fluctuations. The plot is updated every second. The y axis are shown simultaneously in a Grey box and can be modified by the roller button of the mouse. The x axis can present different time ranges.
 There is also the possibility to see the Pixel occupancy and total dead time for the Inner Detector (ID).

Monitored: Pixel and TRT total occupancies, total SCT space points and ID dead time
Trigger requirement:
Line: 105 to 105
 

ATLAS HIT RATES

Hits_all_12Dec2009.bmp
Changed:
<
<
The plot shows hit rates (the sum of the two single-paddle rates), as different color trend lines, for MBTS. We could also see hit rates for BCM, ATLAS BLMs and level-1 trigger information based on the calorimeters.

>
>
The plot shows hit rates (the sum of the two single-paddle rates) for MBTS. We could also see hit rates for BCM, ATLAS BLMs and level-1 trigger information based on the calorimeters.

 Monitored:
Trigger requirement:
Typical 'good' levels:

Revision 172010-02-15 - AlbertoPalma

Line: 1 to 1
 
<!-- Header + table of content !-->

ATLAS Beam Backgrounds

Line: 85 to 85
 

ATL_BACKGROUNDS

IDoccupancy_14Dec2009.bmp
Changed:
<
<
The plot shows the TRT occupancy, averaged over all straws, and the total SCT space points, built from cluster pairs from the opposite sides of a given module, or from separate modules which overlap in eta or in phi. The fluctuations observed are due essentially to beam halo fluctuations. The plot is updated every minute. The y axis are shown simultaneously in a Grey box and can be modified by the roller button of the mouse. The x axis can present different time ranges.
>
>
The plot shows the TRT occupancy, averaged over all straws, and the total SCT space points, built from cluster pairs from the opposite sides of a given module, or from separate modules which overlap in eta or in phi. The fluctuations observed, in this case, are due essentially to beam halo fluctuations. The plot is updated every minute. The y axis are shown simultaneously in a Grey box and can be modified by the roller button of the mouse. The x axis can present different time ranges.
 There is also the possibility to see the Pixel occupancy and total dead time for the Inner Detector (ID).

Monitored: Pixel and TRT total occupancies, total SCT space points and ID dead time
Trigger requirement:

Revision 162010-02-15 - AlbertoPalma

Line: 1 to 1
 
<!-- Header + table of content !-->

ATLAS Beam Backgrounds

Line: 61 to 61
 To see the beam background panels on the LBCF desk computer screens follow the instructions:

1) The top level page for the LHC Finite State Machine (FSM):

Changed:
<
<
  • Click on the “LBC” bottom, on the toolbar of the leftmost computer screen, and on “Beam Conditions DCS”
>
>
  • Click on the “LBC” button, on the tool bar of the leftmost computer screen, and on “Beam Conditions DCS”
 
  • The “ATL_FORWARD:fwUiAtlasFrame” window will pop up
  • Find the LHC box on the top of the window and click on “LHC” to get “LHC and BEAM PARAMETERS”. This brings up the LHC navigation panels:
    -- LHC INTERFACES
Line: 85 to 85
 

ATL_BACKGROUNDS

IDoccupancy_14Dec2009.bmp
Changed:
<
<
The plot shows the TRT occupancy and SCT space points during a physics run. There is also the possibility to see the Pixel occupancy and total dead time for the Inner Detector (ID).

Monitored: Pixel, TRT and ID occupancies, SCT space points and ID dead time
>
>
The plot shows the TRT occupancy, averaged over all straws, and the total SCT space points, built from cluster pairs from the opposite sides of a given module, or from separate modules which overlap in eta or in phi. The fluctuations observed are due essentially to beam halo fluctuations. The plot is updated every minute. The y axis are shown simultaneously in a Grey box and can be modified by the roller button of the mouse. The x axis can present different time ranges.
There is also the possibility to see the Pixel occupancy and total dead time for the Inner Detector (ID).

Monitored: Pixel and TRT total occupancies, total SCT space points and ID dead time
 Trigger requirement:
Typical 'good' levels:
Typical 'warning' levels:

Line: 104 to 105
 

ATLAS HIT RATES

Hits_all_12Dec2009.bmp
Changed:
<
<
The plot shows hit rates (the sum of the two single-paddle rates), as different color trend lines, for MBTS. We could also see hit rates for BCM, ATLAS BLMs and level-1 trigger information based on the calorimeters. The y axis are shown simultaneously in a Grey box and can be modified by the roller button of the mouse. The x axis can present different time ranges.

>
>
The plot shows hit rates (the sum of the two single-paddle rates), as different color trend lines, for MBTS. We could also see hit rates for BCM, ATLAS BLMs and level-1 trigger information based on the calorimeters.

 Monitored:
Trigger requirement:
Typical 'good' levels:

Revision 152010-02-15 - AlbertoPalma

Line: 1 to 1
 
<!-- Header + table of content !-->

ATLAS Beam Backgrounds

Line: 7 to 7
 

Introduction

Changed:
<
<
This page is intended to include information useful for Luminosity / Beam Conditions / Forward Detectors (LBCF) shifters related to the beam background monitoring tools.
>
>
This page is intended to include up-to-date information useful for Luminosity / Beam Conditions / Forward Detectors (LBCF) shifters related to the beam background monitoring tools.
 

Beam background panels

Line: 29 to 29
  Histograms are produced and presented in different panels as a function of time. These panels are organized hierarchically and they concern the following subjects and monitors:
Changed:
<
<
Halo
>
>
Beam Halo
 
  • Beam Conditions Monitor (BCM)
  • Liquid Argon calorimeters (LAr)
  • Minimum Bias Trigger Scintillator (MBTS)
Line: 83 to 83
 

Plots

Changed:
<
<

1) ATL_BACKGROUNDS

atlas_bckg_hit_rates.png
The plot shows hit rates (the sum of the two single-paddle rates), as different color trend lines, for BCM, MBTS, ATLAS BLMs and level-1 trigger information based on the calorimeters. The y axis are shown simultaneously in a Grey box and can be modified by the roller button of the mouse. The x axis can present different time ranges.

>
>

ATL_BACKGROUNDS

IDoccupancy_14Dec2009.bmp
The plot shows the TRT occupancy and SCT space points during a physics run. There is also the possibility to see the Pixel occupancy and total dead time for the Inner Detector (ID).

Monitored: Pixel, TRT and ID occupancies, SCT space points and ID dead time
Trigger requirement:
Typical 'good' levels:
Typical 'warning' levels:

Forward_14Dec2009.bmp
The plot shows hit rates for LUCID. We could also see hit rates for ZDC.

 Monitored:
Trigger requirement:
Changed:
<
<
Typical 'good' levels:
Typical 'warning' levels:

>
>
Typical 'good' levels:
Typical 'warning' levels:

 
Changed:
<
<
atlas_bckg_id_occup.png
The plot shows the TRT occupancy and SCT space points during a physics run. There is also the possibility to see the Pixel occupancy and total dead time for the Inner Detector (ID).

Monitored: Pixel, TRT and ID occupancies, SCT space points and ID dead time
>
>

BEAM_HALO

ATLAS HIT RATES

Hits_all_12Dec2009.bmp
The plot shows hit rates (the sum of the two single-paddle rates), as different color trend lines, for MBTS. We could also see hit rates for BCM, ATLAS BLMs and level-1 trigger information based on the calorimeters. The y axis are shown simultaneously in a Grey box and can be modified by the roller button of the mouse. The x axis can present different time ranges.

Monitored:
 Trigger requirement:
Changed:
<
<
Typical 'good' levels:
Typical 'warning' levels:

>
>
Typical 'good' levels:
Typical 'warning' levels:

CALO_CURRENTS

MUON_CURRENTS

 
META FILEATTACHMENT attachment="button.png" attr="" comment="" date="1266090398" name="button.png" path="button.png" size="2311" stream="button.png" tmpFilename="/usr/tmp/CGItemp24804" user="apalma" version="1"
META FILEATTACHMENT attachment="IDoccupancy_14Dec2009.bmp" attr="" comment="" date="1266181016" name="IDoccupancy_14Dec2009.bmp" path="IDoccupancy_14Dec2009.bmp" size="688014" stream="IDoccupancy_14Dec2009.bmp" tmpFilename="/usr/tmp/CGItemp25279" user="apalma" version="1"
META FILEATTACHMENT attachment="Hits_all_12Dec2009.bmp" attr="" comment="" date="1266182366" name="Hits_all_12Dec2009.bmp" path="Hits_all_12Dec2009.bmp" size="683694" stream="Hits_all_12Dec2009.bmp" tmpFilename="/usr/tmp/CGItemp25222" user="apalma" version="1"
Added:
>
>
META FILEATTACHMENT attachment="Forward_14Dec2009.bmp" attr="" comment="" date="1266244444" name="Forward_14Dec2009.bmp" path="Forward_14Dec2009.bmp" size="642674" stream="Forward_14Dec2009.bmp" tmpFilename="/usr/tmp/CGItemp25736" user="apalma" version="1"

Revision 142010-02-14 - AlbertoPalma

Line: 1 to 1
 
<!-- Header + table of content !-->

ATLAS Beam Backgrounds

Line: 43 to 43
 
  • Zero Degree Calorimeter (ZDC)

Inner Detector Occupancies

Changed:
<
<
  • Silicon Pixel occupancy
  • Semiconductor Tracker (SCT) occupancy
>
>
  • Pixel occupancy
  • Semiconductor Tracker (SCT) space points
 
  • Transition Radiation Tracker (TRT) occupancy

Calorimeter Currents

Line: 83 to 83
 

Plots

Changed:
<
<
1) ATL_BACKGROUNDS
atlas_bckg_hit_rates.png
This plot shows hit rates (the sum of the two single-paddle rates), as different color trend lines, for BCM, MBTS, ATLAS BLMs and level-1 trigger information based on the calorimeters. The y axis are shown simultaneously in a Grey box and can be modified by the roller bottom of the mouse. The x axis can present different time ranges.

2) ATL_BACKGROUNDS
atlas_bckg_id_occup.png
This plot shows the occupancies for the Pixel, SCT and TRT detectors. It also shows the total dead time for the Inner Detector.

>
>

1) ATL_BACKGROUNDS

atlas_bckg_hit_rates.png
The plot shows hit rates (the sum of the two single-paddle rates), as different color trend lines, for BCM, MBTS, ATLAS BLMs and level-1 trigger information based on the calorimeters. The y axis are shown simultaneously in a Grey box and can be modified by the roller button of the mouse. The x axis can present different time ranges.

Monitored:
Trigger requirement:
Typical 'good' levels:
Typical 'warning' levels:

atlas_bckg_id_occup.png
The plot shows the TRT occupancy and SCT space points during a physics run. There is also the possibility to see the Pixel occupancy and total dead time for the Inner Detector (ID).

Monitored: Pixel, TRT and ID occupancies, SCT space points and ID dead time
Trigger requirement:
Typical 'good' levels:
Typical 'warning' levels:

 
Deleted:
<
<
3) ATL_BACKGROUNDS

META FILEATTACHMENT attachment="atlas_bckg_hit_rates.png" attr="" comment="" date="1265487504" name="atlas_bckg_hit_rates.png" path="atlas_bckg_hit_rates.png" size="30888" stream="atlas_bckg_hit_rates.png" tmpFilename="/usr/tmp/CGItemp24903" user="apalma" version="1"
META FILEATTACHMENT attachment="atlas_bckg_id_occup.png" attr="" comment="" date="1265488285" name="atlas_bckg_id_occup.png" path="atlas_bckg_id_occup.png" size="29237" stream="atlas_bckg_id_occup.png" tmpFilename="/usr/tmp/CGItemp24774" user="apalma" version="1"
 
META FILEATTACHMENT attachment="button.png" attr="" comment="" date="1266090398" name="button.png" path="button.png" size="2311" stream="button.png" tmpFilename="/usr/tmp/CGItemp24804" user="apalma" version="1"
Added:
>
>
META FILEATTACHMENT attachment="IDoccupancy_14Dec2009.bmp" attr="" comment="" date="1266181016" name="IDoccupancy_14Dec2009.bmp" path="IDoccupancy_14Dec2009.bmp" size="688014" stream="IDoccupancy_14Dec2009.bmp" tmpFilename="/usr/tmp/CGItemp25279" user="apalma" version="1"
META FILEATTACHMENT attachment="Hits_all_12Dec2009.bmp" attr="" comment="" date="1266182366" name="Hits_all_12Dec2009.bmp" path="Hits_all_12Dec2009.bmp" size="683694" stream="Hits_all_12Dec2009.bmp" tmpFilename="/usr/tmp/CGItemp25222" user="apalma" version="1"

Revision 132010-02-13 - AlbertoPalma

Line: 1 to 1
 
<!-- Header + table of content !-->

ATLAS Beam Backgrounds

Line: 72 to 72
  2) The ATL_BACKGROUNDS navigation panel:
  • Click on the “ATL_BACKGROUNDS” navigation panel to get information on the "Beam Halo", "ID Occupancies & Dead Time" and "Forward Detectors Hit Rates"
Changed:
<
<
  • A button on the right side, above the histograms, allows to comute between absolute and normalized values: button.png
>
>
  • A button like this button.png on the right side above the histograms, allows to commute between absolute and normalized values
 
  • The ATL_BACKGROUNDS brings up the following navigation panels:
    -- BEAM_HALO
    -- ATLAS HIT RATES
Line: 95 to 95
 
META FILEATTACHMENT attachment="atlas_bckg_hit_rates.png" attr="" comment="" date="1265487504" name="atlas_bckg_hit_rates.png" path="atlas_bckg_hit_rates.png" size="30888" stream="atlas_bckg_hit_rates.png" tmpFilename="/usr/tmp/CGItemp24903" user="apalma" version="1"
META FILEATTACHMENT attachment="atlas_bckg_id_occup.png" attr="" comment="" date="1265488285" name="atlas_bckg_id_occup.png" path="atlas_bckg_id_occup.png" size="29237" stream="atlas_bckg_id_occup.png" tmpFilename="/usr/tmp/CGItemp24774" user="apalma" version="1"
Changed:
<
<
META FILEATTACHMENT attachment="button.png" attr="" comment="" date="1266084807" name="button.png" path="button.png" size="2317" stream="button.png" tmpFilename="/usr/tmp/CGItemp24714" user="apalma" version="1"
>
>
META FILEATTACHMENT attachment="button.png" attr="" comment="" date="1266090398" name="button.png" path="button.png" size="2311" stream="button.png" tmpFilename="/usr/tmp/CGItemp24804" user="apalma" version="1"

Revision 122010-02-13 - AlbertoPalma

Line: 1 to 1
 
<!-- Header + table of content !-->

ATLAS Beam Backgrounds

Line: 72 to 72
  2) The ATL_BACKGROUNDS navigation panel:
  • Click on the “ATL_BACKGROUNDS” navigation panel to get information on the "Beam Halo", "ID Occupancies & Dead Time" and "Forward Detectors Hit Rates"
Changed:
<
<
  • A button on the right side, above the histograms, allows to comute between absolute and normalized values
>
>
  • A button on the right side, above the histograms, allows to comute between absolute and normalized values: button.png
 
  • The ATL_BACKGROUNDS brings up the following navigation panels:
    -- BEAM_HALO
    -- ATLAS HIT RATES
Line: 95 to 95
 
META FILEATTACHMENT attachment="atlas_bckg_hit_rates.png" attr="" comment="" date="1265487504" name="atlas_bckg_hit_rates.png" path="atlas_bckg_hit_rates.png" size="30888" stream="atlas_bckg_hit_rates.png" tmpFilename="/usr/tmp/CGItemp24903" user="apalma" version="1"
META FILEATTACHMENT attachment="atlas_bckg_id_occup.png" attr="" comment="" date="1265488285" name="atlas_bckg_id_occup.png" path="atlas_bckg_id_occup.png" size="29237" stream="atlas_bckg_id_occup.png" tmpFilename="/usr/tmp/CGItemp24774" user="apalma" version="1"
Added:
>
>
META FILEATTACHMENT attachment="button.png" attr="" comment="" date="1266084807" name="button.png" path="button.png" size="2317" stream="button.png" tmpFilename="/usr/tmp/CGItemp24714" user="apalma" version="1"

Revision 112010-02-13 - AlbertoPalma

Line: 1 to 1
 
<!-- Header + table of content !-->

ATLAS Beam Backgrounds

Line: 15 to 15
  Different monitoring tools are available to provide checks on the beam backgrounds and the quality of the data collected:
Changed:
<
<
1) Blind background displays (those referred in this Twiki page)
>
>
1) Blind background displays (those referred in this Twiki page)
 
Changed:
<
<
2) Bunch by bunch and timing beam conditions diagnostic displays (will be added latter)
>
>
2) Bunch by bunch and timing beam conditions diagnostic displays (they will become active in the near future and will be explained then)
 

DCS background displays

Changed:
<
<
The blind background displays are part of the Detector Control System (DCS). The information is shown in the form of histograms of:
>
>
The blind background displays are part of the Detector Control System (DCS). There are two levels of information in them:
 
Changed:
<
<
1) absolute values
>
>
  • absolute values
 
Changed:
<
<
2) normalized values (the ones sent to the machine)
>
>
  • normalized values (the ones sent to the machine)

Histograms are produced and presented in different panels as a function of time. These panels are organized hierarchically and they concern the following subjects and monitors:

  Halo
  • Beam Conditions Monitor (BCM)
Line: 54 to 56
 
  • Forward Monitored Drift Tubes (MDT) chambers
  • Thin Gap Chambers (TGC)
Deleted:
<
<
Histograms are produced and presented in different panels as a function of time. These panels are organized hierarchically.

Bunch by bunch and timing beam conditions diagnostic displays

This displays will become active in the near future.

 

Path to the panels

To see the beam background panels on the LBCF desk computer screens follow the instructions:

Line: 76 to 72
  2) The ATL_BACKGROUNDS navigation panel:
  • Click on the “ATL_BACKGROUNDS” navigation panel to get information on the "Beam Halo", "ID Occupancies & Dead Time" and "Forward Detectors Hit Rates"
Added:
>
>
  • A button on the right side, above the histograms, allows to comute between absolute and normalized values
 
  • The ATL_BACKGROUNDS brings up the following navigation panels:
    -- BEAM_HALO
    -- ATLAS HIT RATES

Revision 102010-02-11 - AlbertoPalma

Line: 1 to 1
 
<!-- Header + table of content !-->

ATLAS Beam Backgrounds

Line: 19 to 19
  2) Bunch by bunch and timing beam conditions diagnostic displays (will be added latter)
Added:
>
>

DCS background displays

The blind background displays are part of the Detector Control System (DCS). The information is shown in the form of histograms of:

1) absolute values

2) normalized values (the ones sent to the machine)

  Halo
Added:
>
>
  • Beam Conditions Monitor (BCM)
  • Liquid Argon calorimeters (LAr)
  • Minimum Bias Trigger Scintillator (MBTS)
  Hit rates
  • Beam Conditions Monitor (BCM)
Line: 45 to 56
  Histograms are produced and presented in different panels as a function of time. These panels are organized hierarchically.
Added:
>
>

Bunch by bunch and timing beam conditions diagnostic displays

This displays will become active in the near future.

 

Path to the panels

To see the beam background panels on the LBCF desk computer screens follow the instructions:

Line: 62 to 77
  2) The ATL_BACKGROUNDS navigation panel:
  • Click on the “ATL_BACKGROUNDS” navigation panel to get information on the "Beam Halo", "ID Occupancies & Dead Time" and "Forward Detectors Hit Rates"
  • The ATL_BACKGROUNDS brings up the following navigation panels:
Changed:
<
<
-- BEAM HALO
>
>
-- BEAM_HALO
  -- ATLAS HIT RATES
-- CALO_CURRENTS
-- MUON_CURRENTS

Revision 92010-02-08 - AlbertoPalma

Line: 1 to 1
 
<!-- Header + table of content !-->

ATLAS Beam Backgrounds

Line: 11 to 11
 

Beam background panels

Changed:
<
<
Beam backgrounds and luminosity are relevant features of the run conditions. The ATLAS detector as several monitors that help to distinguish in each bunch crossing between normal collisions and background events. Some of these detectors also contribute for the luminosity determination.
>
>
Beam backgrounds and luminosity are relevant features of the run conditions. The ATLAS detector has several monitors that help distinguish between normal collisions and background events. Some of these detectors also contribute to the luminosity determination.
  Different monitoring tools are available to provide checks on the beam backgrounds and the quality of the data collected:
Added:
>
>
1) Blind background displays (those referred in this Twiki page)

2) Bunch by bunch and timing beam conditions diagnostic displays (will be added latter)

Halo

  Hit rates
  • Beam Conditions Monitor (BCM)
  • ATLAS Beam Loss Monitors (BLM)
Line: 23 to 29
 
  • Level-1 calorimeter (L1 Calo)
  • Zero Degree Calorimeter (ZDC)
Changed:
<
<
Inner Detector Occupancies (STABLE beams only)
>
>
Inner Detector Occupancies
 
  • Silicon Pixel occupancy
  • Semiconductor Tracker (SCT) occupancy
  • Transition Radiation Tracker (TRT) occupancy
Changed:
<
<
Calorimeter Currents (STABLE beams only)
>
>
Calorimeter Currents
 
  • Tile calorimeter (Tilecal)
  • Minimum Bias Trigger Scintillator (MBTS)
  • Forward calorimeters (FCAL)
Changed:
<
<
Muon Chamber Currents (STABLE beams only)
>
>
Muon Chamber Currents
 
  • Forward Monitored Drift Tubes (MDT) chambers
  • Thin Gap Chambers (TGC)
Line: 51 to 57
  -- INSTRUMENTATION
-- ATL_BACKGROUNDS
-- Luminosity
Added:
>
>
-- Luminous region
  2) The ATL_BACKGROUNDS navigation panel:
  • Click on the “ATL_BACKGROUNDS” navigation panel to get information on the "Beam Halo", "ID Occupancies & Dead Time" and "Forward Detectors Hit Rates"

Revision 82010-02-06 - AlbertoPalma

Line: 1 to 1
 
<!-- Header + table of content !-->

ATLAS Beam Backgrounds

Line: 7 to 7
 

Introduction

Changed:
<
<
This page is intended to include information useful for Luminosity / Beam Conditions / Forward Detectors (LBCF) shifters related to the beam-background panels.
>
>
This page is intended to include information useful for Luminosity / Beam Conditions / Forward Detectors (LBCF) shifters related to the beam background monitoring tools.
 

Beam background panels

Line: 44 to 44
 To see the beam background panels on the LBCF desk computer screens follow the instructions:

1) The top level page for the LHC Finite State Machine (FSM):

Changed:
<
<
  • click on the “LBC” bottom, on the toolbar of the leftmost computer screen, and on “Beam Conditions DCS”.
  • The “ATL_FORWARD:fwUiAtlasFrame” window will pop up.
>
>
  • Click on the “LBC” bottom, on the toolbar of the leftmost computer screen, and on “Beam Conditions DCS”
  • The “ATL_FORWARD:fwUiAtlasFrame” window will pop up
  • Find the LHC box on the top of the window and click on “LHC” to get “LHC and BEAM PARAMETERS”. This brings up the LHC navigation panels:
    -- LHC INTERFACES
    -- INSTRUMENTATION
    -- ATL_BACKGROUNDS
    -- Luminosity

2) The ATL_BACKGROUNDS navigation panel:

  • Click on the “ATL_BACKGROUNDS” navigation panel to get information on the "Beam Halo", "ID Occupancies & Dead Time" and "Forward Detectors Hit Rates"
  • The ATL_BACKGROUNDS brings up the following navigation panels:
    -- BEAM HALO
    -- ATLAS HIT RATES
    -- CALO_CURRENTS
    -- MUON_CURRENTS

3) Explore each one of these new navigation panels

 

Plots

Added:
>
>
1) ATL_BACKGROUNDS
atlas_bckg_hit_rates.png
This plot shows hit rates (the sum of the two single-paddle rates), as different color trend lines, for BCM, MBTS, ATLAS BLMs and level-1 trigger information based on the calorimeters. The y axis are shown simultaneously in a Grey box and can be modified by the roller bottom of the mouse. The x axis can present different time ranges.

2) ATL_BACKGROUNDS
atlas_bckg_id_occup.png
This plot shows the occupancies for the Pixel, SCT and TRT detectors. It also shows the total dead time for the Inner Detector.

3) ATL_BACKGROUNDS

META FILEATTACHMENT attachment="atlas_bckg_hit_rates.png" attr="" comment="" date="1265487504" name="atlas_bckg_hit_rates.png" path="atlas_bckg_hit_rates.png" size="30888" stream="atlas_bckg_hit_rates.png" tmpFilename="/usr/tmp/CGItemp24903" user="apalma" version="1"
META FILEATTACHMENT attachment="atlas_bckg_id_occup.png" attr="" comment="" date="1265488285" name="atlas_bckg_id_occup.png" path="atlas_bckg_id_occup.png" size="29237" stream="atlas_bckg_id_occup.png" tmpFilename="/usr/tmp/CGItemp24774" user="apalma" version="1"

Revision 72010-02-06 - AlbertoPalma

Line: 1 to 1
 
<!-- Header + table of content !-->

ATLAS Beam Backgrounds

Line: 11 to 11
 

Beam background panels

Changed:
<
<
Beam backgrounds and luminosity are relevant features of the run conditions. The ATLAS detector as several monitors that help to distinguish in each bunch crossing between normal collisions and background events.
>
>
Beam backgrounds and luminosity are relevant features of the run conditions. The ATLAS detector as several monitors that help to distinguish in each bunch crossing between normal collisions and background events. Some of these detectors also contribute for the luminosity determination.

Different monitoring tools are available to provide checks on the beam backgrounds and the quality of the data collected:

  Hit rates
Added:
>
>
  • Beam Conditions Monitor (BCM)
  • ATLAS Beam Loss Monitors (BLM)
  • Minimum Bias Trigger Scintillator (MBTS)
  • Luminosity Cerenkov Integrating Detector (LUCID)
  • Level-1 calorimeter (L1 Calo)
  • Zero Degree Calorimeter (ZDC)
  Inner Detector Occupancies (STABLE beams only)
Changed:
<
<
  • Silicon Pixel occupancies
  • Semiconductor Tracker (SCT) occupancies
  • Transition Radiation Tracker (TRT) occupancies
>
>
  • Silicon Pixel occupancy
  • Semiconductor Tracker (SCT) occupancy
  • Transition Radiation Tracker (TRT) occupancy
  Calorimeter Currents (STABLE beams only)
Added:
>
>
  • Tile calorimeter (Tilecal)
  • Minimum Bias Trigger Scintillator (MBTS)
  • Forward calorimeters (FCAL)
  Muon Chamber Currents (STABLE beams only)
Added:
>
>
  • Forward Monitored Drift Tubes (MDT) chambers
  • Thin Gap Chambers (TGC)

Histograms are produced and presented in different panels as a function of time. These panels are organized hierarchically.

 

Path to the panels

To see the beam background panels on the LBCF desk computer screens follow the instructions:

Added:
>
>
1) The top level page for the LHC Finite State Machine (FSM):
  • click on the “LBC” bottom, on the toolbar of the leftmost computer screen, and on “Beam Conditions DCS”.
  • The “ATL_FORWARD:fwUiAtlasFrame” window will pop up.
 

Plots

Revision 62010-02-06 - AlbertoPalma

Line: 1 to 1
 
<!-- Header + table of content !-->

ATLAS Beam Backgrounds

Line: 13 to 13
  Beam backgrounds and luminosity are relevant features of the run conditions. The ATLAS detector as several monitors that help to distinguish in each bunch crossing between normal collisions and background events.
Added:
>
>
Hit rates

Inner Detector Occupancies (STABLE beams only)

  • Silicon Pixel occupancies
  • Semiconductor Tracker (SCT) occupancies
  • Transition Radiation Tracker (TRT) occupancies

Calorimeter Currents (STABLE beams only)

Muon Chamber Currents (STABLE beams only)

 

Path to the panels

To see the beam background panels on the LBCF desk computer screens follow the instructions:

Revision 52010-02-05 - AlbertoPalma

Line: 1 to 1
 
<!-- Header + table of content !-->

ATLAS Beam Backgrounds

Line: 9 to 9
  This page is intended to include information useful for Luminosity / Beam Conditions / Forward Detectors (LBCF) shifters related to the beam-background panels.
Changed:
<
<

Beam-background panels

>
>

Beam background panels

 
Changed:
<
<
The ATLAS detector as several monitors that distinguish in each bunch crossing between normal collisions and background events during normal running.
>
>
Beam backgrounds and luminosity are relevant features of the run conditions. The ATLAS detector as several monitors that help to distinguish in each bunch crossing between normal collisions and background events.
 

Path to the panels

Changed:
<
<
To see the beam-background panels on the LBCF desk computer screens follow the instructions:
>
>
To see the beam background panels on the LBCF desk computer screens follow the instructions:
 

Plots

Revision 42010-02-05 - AlbertoPalma

Line: 1 to 1
 
<!-- Header + table of content !-->

ATLAS Beam Backgrounds

Line: 7 to 7
 

Introduction

Changed:
<
<
This page is intended to include information useful for Luminosity / Beam Conditions / Forward Detectors (LBCF) shifters related to the beam background panels.
>
>
This page is intended to include information useful for Luminosity / Beam Conditions / Forward Detectors (LBCF) shifters related to the beam-background panels.
 

Beam-background panels

Line: 15 to 15
 

Path to the panels

Added:
>
>
To see the beam-background panels on the LBCF desk computer screens follow the instructions:
 

Plots

Revision 32010-02-05 - AlbertoPalma

Line: 1 to 1
 
<!-- Header + table of content !-->
Changed:
<
<

ATLAS Backgrounds

>
>

ATLAS Beam Backgrounds

 
Changed:
<
<

Online background displays

>
>

Introduction

This page is intended to include information useful for Luminosity / Beam Conditions / Forward Detectors (LBCF) shifters related to the beam background panels.

Beam-background panels

The ATLAS detector as several monitors that distinguish in each bunch crossing between normal collisions and background events during normal running.

Path to the panels

Plots

Revision 12010-02-03 - AlbertoPalma

Line: 1 to 1
Added:
>
>
<!-- Header + table of content !-->

ATLAS Backgrounds

 
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