AtlasPublicTopicHeader.png

Public Inner Detector BCM Plots for Collision Data

Introduction

Approved plots that can be shown by ATLAS speakers at conferences and similar events.
Please do not add figures on your own. Contact the responsible project leader in case of questions and/or suggestions.

These plots show results from the Beam Conditions Monitor - eight diamond sensors placed four each side of the ATLAS pixel detector, 1.84m away from the centre of the detector.

Links to related information

BCM results from high energy collision data in 2010

These plots were approved in November 2010.

Average number of events per bunch crossing satisfying the AND algorithm condition, color-coded for individual colliding bunches. Data for BCM horizontal modules is shown over ATLAS run 166924 for all 295 colliding bunches. For an event to satisfy the AND condition, it must contain a coincidence of hits in the two horizontal A and C side BCM modules, within the second half (12.5 ns) of the bunch interval.

final_BCM_BCVSLB_166924_AND.png
eps version of the figure

Average number of events per bunch crossing satisfying the OR algorithm condition, color-coded for individual colliding bunches. Data for BCM horizontal modules is shown over ATLAS run 166924 for all 295 colliding bunches. For an event to satisfy the OR condition, it must contain at least one hit in four horizontal BCM modules within the second half (12.5 ns) of the bunch interval.

final_BCM_BCVSLB_166924_OR.png
eps version of the figure

Average number of events per bunch crossing satisfying the AND algorithm condition versus time. For an event to satisfy the AND condition, it must contain a coincidence of hits in the A and C side BCM modules (vertical or horizontal) within the second half of the bunch interval. Event counts are averaged over all colliding bunches and scaled to one LHC turn. Data for both RODs (two independent measurements) was extracted from run 166924.

final_BCM_LVSLB_166924_AND.png
eps version of the figure

Average number of events per bunch crossing satisfying the OR algorithm condition versus time. For an event to satisfy the OR condition, it must contain a hit anywhere in BCM detector within second half of the bunch interval. Event counts are averaged over all colliding bunches and scaled to one LHC turn. Data for both RODs (two independent measurements) was extracted from run 166924.

final_BCM_LVSLB_166924_OR.png
eps version of the figure

Average number of events per bunch crossing satisfying the exclusive OR-A (XOR-A) algorithm condition versus time. For an event to satisfy the XOR-A condition, it must contain a hit on A side, and no hits on C side vertical or horizontal modules of the BCM detector within the second half of the bunch interval. Event counts are averaged over all colliding bunches and scaled to one LHC turn. Data for both RODs (two independent measurements) were extracted from run 166924.

final_BCM_LVSLB_166924_XORA.png
eps version of the figure

Average number of events per bunch crossing satisfying the exclusive OR-C (XOR-C) algorithm condition versus time. For an event to satisfy the XOR-C condition, it must contain a hit on C side, and no hits on A side in the vertical or horizontal modules of the BCM detector within the second half of the bunch interval. Event counts are averaged over all colliding bunches and scaled to one LHC turn. Data for both RODs (two independent measurements) were extracted from run 166924.

final_BCM_LVSLB_166924_XORC.png
eps version of the figure

Average number of events per bunch crossing satisfying different algorithm conditions versus time. Event counts are averaged over all colliding bunches. Data are shown for comparison of different algorithm occupancies. For clarity, only the data from horizontal modules are plotted for the run 166924.

final_BCM_LVSLB_166924_ALL.png
eps version of the figure

Average number of events per LHC turn satisfying the OR algorithm condition. Horizontal axis denotes the sequential number of possible bunch slots, and extends over all 3564 slots covering the entire LHC beam. Bunch train structure of the beam is clearly visible, as well as the relative strength between signals induced by colliding and unpaired bunches (bunch numbers 1500-1600). The latter is comparable to the amplitude of the afterglow following each colliding bunch. For clarity, only data for horizontal modules are plotted for ATLAS run 166924 (16.10.2010).

final_BCM_BCID_run166924_OR.png
eps version of the figure

Average number of events per LHC turn satisfying the AND algorithm condition. Horizontal axis denotes the sequential number of possible bunch slots, and extends over all 3564 slots covering the entire LHC beam. Bunch train structure of the beam is clearly visible, as well as the relative strength between signals induced by colliding and by unpaired bunches (bunch numbers from 1500-1600). The AND algorithm imposes a stricter selection, which suppresses the afterglow signal visible in OR algorithms. For clarity, only data for horizontal modules are plotted for ATLAS run 166924 (16.10.2010).

final_BCM_BCID_run166924_AND.png
eps version of the figure

Average number of events per LHC turn satisfying the AND algorithm condition. Horizontal axis denotes the sequential number of possible bunch slots, highlighting only a part of the entire LHC beam. Individual bunches are well distinguishable within the bunch train even for the unpaired bunches. For selective algorithms such as AND, the random background is five orders of magnitude lower than the signal. For clarity, only data for horizontal modules are plotted for ATLAS run 166924 (16.10.2010).

final_BCM_BCID_run166924_AND_zoom.png
eps version of the figure

BCM data collected during the van der Meer scan on 1.10.2010. The vertical axis quantifies the number of events satisfying the OR algorithm condition normalized to single LHC turn. Only the six colliding bunches are summed into the values shown. Data for both RODs (two independent measurements) is shown as a function of beam separation.

final_BCM_VDM_X_OR_PHY.png
eps version of the figure

BCM data collected during the Van der Meer scan on 1.10.2010. The vertical axis quantifies the number of events satisfying OR algorithm condition normalized to single LHC turn. All, except colliding bunches, are summed into the values shown. Data for both RODs (two independent measurements) is shown as a function of beam separation. The signal is two orders below the contribution of colliding bunches, but still exhibiting scan-typical beam separation dependence due to afterglow effects.

final_BCM_VDM_X_ORNOPHY.png
eps version of the figure

BCM data collected during the Van der Meer scan on 1.10.2010. The vertical axis quantifies the number of events satisfying the AND algorithm condition normalized to single LHC turn. Only the colliding bunches are summed into the values shown. Data for both RODs (two independent measurements) is shown as a function of beam separation.

final_BCM_VDM_X_AND_PHY.png
eps version of the figure

BCM data collected during the Van der Meer scan on 1.10.2010. The vertical axis quantifies the number of events satisfying the AND algorithm condition normalized to single LHC turn. All, except colliding bunches, are summed into the values shown. Data for both RODs (two independent measurements) is shown as a function of beam separation.

final_BCM_VDM_X_ANDNOPHY.png
eps version of the figure

Distribution of events against difference of arrival times of hits on A and C side of BCM detector for run 152779. From difference of arrival times to both sides it is possible to distinguish collision and background coming from LHC beam 1 and beam 2.

higain_deltat_r152779.png
eps version of the figure

Signal seen at the LHC dump by ATLAS BCM on 26.3.2010 at 13:41 (Geneva local time). LHC was doing collimator studies at 3.5TeV. Plot shows development of signal in low threshold channels in about 90ms prior and 10ms after the post mortem event.

higain_beam_dump_26032010_1.png
eps version of the figure

Signal seen at the LHC dump by ATLAS BCM on 26.3.2010 at 13:41 (Geneva local time). LHC was doing collimator studies at 3.5TeV. Plot shows development of signal in high threshold channels in about 90ms prior and 10ms after the post mortem event.

logain_beam_dump_26032010_1.png
eps version of the figure

Signal seen at the LHC dump by ATLAS BCM. LHC was doing collimator studies at 3.5TeV. Coincidence seen on one ROD. From the relative timing of the channels it is obvious that it was due to beam 2 going from C side to A side of ATLAS. Plot shown is an example of automatically generated gif picture after PM analysis.

rawBC_BCM.png
eps version of the figure

BCM results from December 2009 collision data

These plots were approved on 16 February 2010, using 2009 data with 900 GeV centre-of-mass energy.

BCM Time-Of-Flight (TOF) collision and beam background events as function of the Bunch Crossing Identifier (BCID) showing the LHC fill structure for run 142193. Beam background and collision events are visible for bunch crossings with the IDs 1,101 and 2774. Bunch crossings 424 & 2209 have only beam background events from Beam 1 and bunch crossings 1315 & 1880 only beam background events from Beam 2, respectively. These bunch crossings are presumably creating collisions in ALICE and LHCb.

Deltat_vs_BCID_final.png
eps version of the figure

Time evolution of beam background and collision events for run 142193 measured as a BCM Time-Of-Flight (TOF) distribution between the two detector stations located at z = 1.84m. The time is binned in units of Event Counter Reset (ECR), which are 5s signals. The ECR itself is reset approximately every 21 minutes. Since the run was almost 6 hours long, the plot shows a superposition of ~18 ECR sweeps. A higher beam background period for Beam1 is visible between ECR values 210 and 230.

Deltat_vs_Time_final.png
eps version of the figure

BCM Time-Of-Flight (TOF) distribution for run 142193 between the two BCM detector stations located at z = 1.84m. Δt values of 12.5 ns represent beam background events from LHC Beam 1 whereas Δt values of -12.5 ns represent LHC Beam 2 background events, respectively. Collision events have Δt values of 0 ns. A Gaussian fit of the collision peak in the tC - tA TOF distribution yields a width of 972 ps; this is consistent with a single side time resolution of 687 ps.

Hits_vs_Deltat_final.png
eps version of the figure


Responsible: PippaWells
Last reviewed by: Never reviewed

Topic attachments
I Attachment History Action Size Date Who Comment
PNGpng final_BCM_BCID_run166924_AND.png r1 manage 50.0 K 2010-11-23 - 14:41 UnknownUser  
Unknown file formateps final_BCM_BCID_run166924_AND_zoom.eps r1 manage 11.6 K 2010-11-23 - 14:42 UnknownUser  
PNGpng final_BCM_BCID_run166924_AND_zoom.png r1 manage 45.0 K 2010-11-23 - 14:41 UnknownUser  
Unknown file formateps final_BCM_BCID_run166924_OR.eps r1 manage 29.7 K 2010-11-23 - 14:40 UnknownUser  
PNGpng final_BCM_BCID_run166924_OR.png r1 manage 52.8 K 2010-11-23 - 14:40 UnknownUser  
Unknown file formateps final_BCM_BCVSLB_166924_AND.eps r1 manage 467.1 K 2010-11-23 - 14:13 UnknownUser  
PNGpng final_BCM_BCVSLB_166924_AND.png r1 manage 220.8 K 2010-11-23 - 14:12 UnknownUser  
Unknown file formateps final_BCM_BCVSLB_166924_OR.eps r1 manage 471.3 K 2010-11-23 - 14:13 UnknownUser  
PNGpng final_BCM_BCVSLB_166924_OR.png r1 manage 181.8 K 2010-11-23 - 14:13 UnknownUser  
Unknown file formateps final_BCM_LVSLB_166924_ALL.eps r1 manage 15.4 K 2010-11-23 - 14:25 UnknownUser  
PNGpng final_BCM_LVSLB_166924_ALL.png r1 manage 68.5 K 2010-11-23 - 14:25 UnknownUser  
Unknown file formateps final_BCM_LVSLB_166924_AND.eps r1 manage 12.0 K 2010-11-23 - 14:21 UnknownUser  
PNGpng final_BCM_LVSLB_166924_AND.png r1 manage 61.1 K 2010-11-23 - 14:21 UnknownUser  
Unknown file formateps final_BCM_LVSLB_166924_OR.eps r1 manage 11.6 K 2010-11-23 - 14:22 UnknownUser  
PNGpng final_BCM_LVSLB_166924_OR.png r1 manage 55.5 K 2010-11-23 - 14:22 UnknownUser  
Unknown file formateps final_BCM_LVSLB_166924_XORA.eps r1 manage 11.8 K 2010-11-23 - 14:24 UnknownUser  
PNGpng final_BCM_LVSLB_166924_XORA.png r1 manage 56.8 K 2010-11-23 - 14:23 UnknownUser  
Unknown file formateps final_BCM_LVSLB_166924_XORC.eps r1 manage 11.8 K 2010-11-23 - 14:24 UnknownUser  
PNGpng final_BCM_LVSLB_166924_XORC.png r1 manage 56.2 K 2010-11-23 - 14:24 UnknownUser  
Unknown file formateps final_BCM_VDM_X_ANDNOPHY.eps r1 manage 11.3 K 2010-11-23 - 14:51 UnknownUser  
PNGpng final_BCM_VDM_X_ANDNOPHY.png r1 manage 46.3 K 2010-11-23 - 14:51 UnknownUser  
Unknown file formateps final_BCM_VDM_X_AND_PHY.eps r1 manage 9.8 K 2010-11-23 - 14:50 UnknownUser  
PNGpng final_BCM_VDM_X_AND_PHY.png r1 manage 45.0 K 2010-11-23 - 14:50 UnknownUser  
Unknown file formateps final_BCM_VDM_X_ORNOPHY.eps r1 manage 11.9 K 2010-11-23 - 14:49 UnknownUser  
PNGpng final_BCM_VDM_X_ORNOPHY.png r1 manage 49.0 K 2010-11-23 - 14:49 UnknownUser  
Unknown file formateps final_BCM_VDM_X_OR_PHY.eps r1 manage 8.6 K 2010-11-23 - 14:49 UnknownUser  
PNGpng final_BCM_VDM_X_OR_PHY.png r1 manage 42.8 K 2010-11-23 - 14:48 UnknownUser  
Unknown file formateps higain_beam_dump_26032010_1.eps r1 manage 97.8 K 2010-11-23 - 15:10 UnknownUser  
PNGpng higain_beam_dump_26032010_1.png r1 manage 37.2 K 2010-11-23 - 15:10 UnknownUser  
Unknown file formateps higain_deltat_r152779.eps r1 manage 283.1 K 2010-11-23 - 15:03 UnknownUser  
PNGpng higain_deltat_r152779.png r1 manage 56.4 K 2010-11-23 - 15:03 UnknownUser  
Unknown file formateps logain_beam_dump_26032010_1.eps r1 manage 97.8 K 2010-11-23 - 15:10 UnknownUser  
PNGpng logain_beam_dump_26032010_1.png r1 manage 36.6 K 2010-11-23 - 15:09 UnknownUser  
Unknown file formateps rawBC_BCM.eps r1 manage 60.0 K 2010-11-23 - 15:10 UnknownUser  
PNGpng rawBC_BCM.png r1 manage 50.7 K 2010-11-23 - 15:10 UnknownUser  
Edit | Attach | Watch | Print version | History: r5 < r4 < r3 < r2 < r1 | Backlinks | Raw View | WYSIWYG | More topic actions
Topic revision: r5 - 2010-12-06 - unknown
 
    • Cern Search Icon Cern Search
    • TWiki Search Icon TWiki Search
    • Google Search Icon Google Search

    Atlas All webs login

This site is powered by the TWiki collaboration platform Powered by PerlCopyright & 2008-2018 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback