...
Activities: Ben, Timon, Adrien, WilliamPatrick, Sanha, SD
9:45 AM Beam turned on with ~40 hits per beam on MIMOSA
...
- Continued accumulating statistics with the current 2 LBNL RD53a modules at 0 degrees
- Investigate cosmicGui setup and routing beam trigger to HSIO2 for independent Cosmic telescope runs
- Continue developing the beam vs 40Mhz clock phasing measurement
Activities: Ben, Adrien, Elisabetta, Cesar, Sanha, SD
9:21 Started Run 460 with both RD53a. Same rate as yesterday.
...
15:34 Stopped Run 471. Requested access from MCC to fix the trigger for the cosmic telescope. Found trigger 11 used previously by UCSC and connected it to the outermost scintillator trigger port on the HSIO2 board(scintillator0).Got cosmicGui running with cyclic triggers after realizing that the key was to adapting a working version of .cosmicDaq.rc. Got clarification from Martin on the HSIO2 cosmic trigger connection scheme: a) 4 LEMO ports on RTM are NIM; b) main board LEMO Ext 1,2 are TTL; c) main board Ext 7,8 take LVTTL (2.5V) are Ored with 1,2; d) TLU RJ45 takes TLU triggers. Found trigger 11 (NIM) used previously by UCSC and connected it to the outermost RTM scintillator trigger port on the HSIO2 board (scintillator0). Also connected LEMO from TLU TTL out Trigger 1 to HSIO2 main board Ext Trg 1. This needs to activate in EUDAQ config to run parasitic to main partition when the is up. Don't have level shifter in hand to adapt the HitOR trigger from cosmic telescope for now.
16:03 Started 16:03 Started Run 472 after access.
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 (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., and the trigger delay on cosmicGui is set at 228, and telescope/DUT latency set to 10 (reversed def for FEI4, low number means high latency).
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.
...
| Run | Start | End time | #events | RD53a DUT | Particle rate | Comments |
|---|---|---|---|---|---|---|
| 460 | 9:21 | 9:56 | 10K | C,D | 4.6 / 1.1 | Start Day shift with beam setup as yesterday |
| 461 | 9:56 | 10:30 | 10K | C,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. | |
| 463 | 10:32 | 11:06 | 10K | C,D | - | |
| 464 | 11:06 | 11:38 | 9.5K | C,D | Stopped a little early to avoid potential event mismatch errors, will continue to do this for the rest of the runs. | |
| 465 | 11:39 | 12:12 | 9.8K | C,D | - | |
| 466 | 12:12 | 12:46 | 10K | C,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. | |
| 467 | 12:47 | 13:18 | 9.5K | C,D | - | |
| 468 | 13:19 | 13:51 | 9.5K | C,D | - | |
| 469 | 13:52 | 14:24 | 9.8K | C,D | 3.9 / 0.68 | - |
| 470 | 14:25 | 14:58 | 9.8K | C,D | - | |
| 471 | 15:01 | 15:34 | 9.7K | C,D | - | |
| 472 | 16:03 | 16:36 | 10K | C,D | Started Run 472 after access to ESA to establish trigger for cosmic telescope, decided to let the run control autostart runs again. | |
| 473 | 16:37 | 17:10 | 10K | C,D | - | |
| 474 | 17:11 | 17:44 | 10K | C,D | - | |
| 475 | 17:45 | 18:18 | 10K | C,D | - | |
| 476 | 18:19 | 18:40 | 3K | C,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. | |
| 478 | 19:45 | 20:21 | 10K | C, D | Another full 10K run with the same beam setting after accessing due to computer shutdown issues | |
| 479 | 20:21 | 20:55 | 10K | C, D | - | |
| 480 | 20:55 | 9:01 | 1668 | C, D | Run ended due to the end of beam time |
Nov 6
Note: ESTB period is 9:00am–11:00pm today with extra 2 hours (Wednesday will be shorter 11am–9pm)
Plan of the Day:
- Switch to tilted data taking with the two LBNL RD53a
- More cosmic telescope data with separate cosmicGui partition