LHCb testbeam October 2018 measurements overview

Device MeasurementSorted ascending TLSCP bias [V] DUT bias [V] Threshold [e] Angle [degrees] Spills per step Spills total Runs Comments
3D Angle scan 200 60 800 [0, 20, 2] 10 110 [31096, 31098], [31105, 31112] No t0. See below.
  Angle scan 100 25 700 [38, 52, 2] 10 80 31387, [31390, 31398]  
  Bias and angle scan 200 20, 40, 65 800 [0, 45, 3] 4 64 [31601, 31605], [31607, 31625], [31627, 31651]  
  Bias and angle scan 200 15, [30, 90, 30] 700 [0, 80, 5] 5 255 [31311, 31315], [31317, 31330], [31332, 31345], [31347, 31362], [31364, 31382]  
  Bias and angle scan 200 [100, 300, 100] 700 [0, 80, 5] 5 255 [31532, 31540], [31542, 31556], [31558, 31568], [31570, 31585]  
W0011_I05 Bias scan 200 2.5, 5, [10, 60, 10] 800 0 20 160 [31084, 31095] No t0. See below.
  Bias scan 200 2.5, 5, [10, 60, 10] 800 0 20 160 [31194, 31197], 31200, [31202, 31205], 31207 DUT not centred, Telecscope planes have way too small cluster size in run 31207
Planar 50 Ám Bias scan 200 5, 10, 15, [20, 90, 10] 700 0 20 220 [31257, 31264], 31267, 31268, 31270, 31273, 31277, 31278  
W0020_J07 Bias scan 200 [25, 300, 25] 700 0 1 12 [31482, 31493] Ikrum = 10
Planar 200 Ám Bias scan 200 [25, 300, 25] 700 0 1 12 [31500, 31506], [31509, 31513]  
  Bias scan at grazing angle 200 5, 10, 15, [20, 60, 10] 800 88.3 20 160 [31182, 31185], 31189, [31191, 31193] In run 31182, plane 5 has wrong number of phase groups.
  Bias scan at grazing angle 200 15, [30, 90, 30] 700 89.5 20 80 31305, 31306, 31309, 31310  
  Bias scan at grazing angle 200 [50, 300, 50] 700 88.8 10 60 31522, [31527, 31531]  
  Grazing angle scan 200 60 800 85, 86, 87.5, 97.7, 92.5 5 25 31175, [31178, 31180]  
  Grazing angle scan 200 90 700 86, 88, 88.3, 88.8, 89.1, 89.5, 90.3 5 35 [31298, 31304]  
  Grazing angle scan 200 300 700 86, 87.5, 88.4, 88.8, 91.2 5 25 [31514, 31518]  
  Grazing angle scan at lower bias 200 40 800 86, 88, 88.3, 88.8, 89.1, 89.5, 90.3 5 35 [31664, 31671]  
  Long grazing angle run 200 60 800 85(?) 189 189 31174 Long run over lunch
W0039_I11 Long run 200 90 700 0 135 135 31251 Long run over lunch.
  Telescope bias scan [25, 200, 25] 65 800 0 5 40 [31652, 31656], [31661, 31663] Something wrong with W2F5 in run 31654
  Threshold scan 200 90 [500, 1000, 100], [1200, 1600, 200] 0 20 180 [31400, 31407], 31409  
  Threshold scan 100 25 [700, 1000, 100] 45 10 40 [31425, 31428]  
  Threshold scan at grazing angle 200 90 [700, 1000, 100], [1200, 1600, 200] 89.5 10 70 [31431, 31437]  
  Timing uniformity of pixel matrix 200 60 800 0 20 120 31121, 31125, 31129, [31131, 31133] No t0. See below. Measurements at all the corners.
  Timing uniformity of pixel matrix 200 90 700 0 20 100 [31439, 31443] Measurements at all the corners and the centre of the chip
  Timing uniformity of pixel matrix 200 90 700 0 5 ? 31444 Measurements at all the corners and the centre of the chip in a single run

For clarity:
[31084, 31095] means 31084, 31085, 31086, ..., 31093, 31094, 31095
[20, 60, 10] means 20, 30, 40, 50, 60

See Elog for more details:
Runs 31062 -- 31214: https://webapps.nikhef.nl/elog/Silicon/17
Runs 31215 -- 31444: https://webapps.nikhef.nl/elog/Silicon/18
Runs 31447 -- 31585: https://webapps.nikhef.nl/elog/Silicon/21
Runs 31588 -- 31675: https://webapps.nikhef.nl/elog/Silicon/22

Software t0 problem

The first three measurements of W0011_I05 were without an external t0 signal and we put in a software t0 synchronisation to fix this. The software t0, however, does not reset the spidr time. As a result, a fraction of the pixel pakcets might have a spidr time that is off by 409.6 Ás because the spidr tries to detect pixel packets that arrive too late, by comapring the pixel ToA and the spidr time, and then corrects the spidr time accordingly. It might be possible to salvage this data by using the telescope data.

TDC trigger configuration

The table below shows the three different trigger configurations that we had during the testbeam. The downstream scintillator determines the coincidene.

Trig. config. Runs DAQ 1 DAQ 2 DAQ 3 DAQ 4 DAQ 6
I* 84–133 RICH - Scintillator up-/downstream Coincidence Scintillator up-/downstream
II 174–207 RICH Scintillator downstream VELO Coincidence Scintillator upstream
III 257–671 Scintillator upstream Scintillator downstream VELO Coincidence RICH

*Runs without t0.

Device configuration

The table below shows which devices were connected to which DAQ machine

FMC DAQ 1 DAQ 2 DAQ 3 DAQ 4 DAQ 6
0 W2J6 W2C5 W2G5 W2H7 Dummy W11D4/W2E5
1 W2B5 W2D5 W2F5 W2I3 DUT
Topic revision: r18 - 2020-02-13 - KevinHeijhoff
 
This site is powered by the TWiki collaboration platform Powered by Perl This site is powered by the TWiki collaboration platformCopyright © 2008-2020 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback