Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

16:03 Started Run 472 after access. Also, after

16:03 cosmicRun 034 First data in LBNL Telescope via cosmicGui. After coming back upstairs and changing the trigger settings in the cosmicGui, we were able to read out data from the cosmic telescope . After analyzing the timing we found that the beam is split with two bc ~100 ns apart. We also see strange peaks on the timing graphs from pixels on the bottom of the modules that seem to readout twice as high as all the other pixels. It seems as if when it reads out for the second bc it gives the data for both bc rather than just the first(see cosmicRun 034). The ESTB beam trigger delay (UCSC LGAD trigger) is set at -104500, and the trigger delay on cosmicGui is set at 228.

The timing distributions of the hits in cosmicRun 034 peaks at two different bins: a small peak at bin1 and a large peak at bin5. Decreasing the cosmic trigger delay by 4 bins (to 224), we see that both the peaks move by 4 bins, suggesting that the two-peak feature is not due to the detector noise (see cosmicRun 035).  Increasing the cosmicGui trigger deadtime to a large value (100 ticks) to avoid double-triggers, we still see essentially the same behavior in cosmicRun 036. After a longer run (cosmicRun 037) and some analyses & discussions, we infer that the beam is indeed split into two bunches, roughly 100ns apart. We also suspect that certain "bad" pixels might be reading out multiple times after it gets hit by real particles (roughly every 100ps); these pixels have very high hits in only the "second bunch" of the beam (but not the first), and only these pixels read out hits well after the beam is gone (well after the second bunch peak). The behavior seems to happen across all the 6 modules.

16:36 Ended Run 472.

16:37 Started Run 473.

...

17:44 Ended Run 474.

17:45 Started Run 475Started Run 475.

18:01 Started cosmicRun 038 with beam trigger delay at -104500 and cosmicGui trigger delay at 224.

18:18 Ended Run 475.

18:19 Started Run 476.

...

19:20 ar-eudaq machine was also frozen, so it was reboot.

19:45 Successful data taking resumed for RD53A

20:17 LBNL cosmic telescope moved around slightly to better center the beam: current config X stage -3.50mm and Y-

 

Data summary:

RunStartEnd time#eventsRD53a DUTParticle rateComments
4609:219:56

10K

C,D4.6 / 1.1Start Day shift with beam setup as yesterday
4619:5610:3010KC,D After this run all connections but the monitor and log collector died and the next run was not autostarted. Saved data from run 461, terminated processes, and restarted.
46310:3211:0610KC,D -
46411:0611:389.5KC,D Stopped a little early to avoid potential event mismatch errors, will continue to do this for the rest of the runs.
46511:3912:129.8KC,D -
46612:1212:4610KC,D Accidentally ran to 10K and autostarted next run (with no issues) because we were looking at the cosmicGui and lost track of the count. Stopping a bit before 10K resumes with 467.
46712:4713:189.5KC,D -
46813:1913:519.5KC,D -
46913:5214:249.8KC,D3.9 / 0.68

-

47014:2514:589.8KC,D -
47115:0115:349.7KC,D -
47216:0316:3610KC,D Started Run 472 after access to ESA to establish trigger for cosmic telescope, decided to let the run control autostart runs again. 
47316:3717:1010KC,D -
47417:1117:4410KC,D -
47517:4518:1810KC,D -
47618:1918:403KC,D Data taking stopped abruptly for both the cosmic telescope and the two RD53A modules. Couldn't ssh into computer downstairs that starts the TLU Producer. Shut off beam and requested access.
       
t ssh into computer downstairs that starts the TLU Producer. Shut off beam and requested access.
47819:4520:2110KC, D Another full 10K run with the same beam setting after accessing due to computer shutdown issues
47920:2120:5510K

C, D

 -
48020:559:011668C, D Run ended due to the end of beam time