...
0:55 Trigger 11 starting panel delay setting is -104500. Our RD53A DAQ widnow window is 32 beam crossings = 800nsand a configured latency of 64. Stepping towards large delays (more -ve numbers) by 500ns steps. Didn't find it in this direction. Went the other way. Found it at trigger delay = -102010 which will put most data at tick=8.
1:30 45 Fine tuned RD53A DUT position Y+4mm, X+6mm to center the spot onto RD53a module. Saved histogram for Run 652. Cannot see MIMOSA vs RD53a correlation yet.
1:50 Started Run 653 with beamspot centered as high stat local RD53a hit analysis sample.
| Run | Start | End | Event | Particle rate | Tilt | Comments |
|---|---|---|---|---|---|---|
| 653 | 1:50 | 2:05 | 4852 | 40 | 0 | Ended to try new version of producer |
| 683 | 3:22 | 3:55 | 9906 | 40 | 0 | (eventNumber offset -1, new version of YarrProd still can not sync with MIMOSA) |
| 684 | 4:00 | 4:34 | 9908 | 40 | 0 | ((eventNumber offset 0, new version of YarrProd still can not sync with MIMOSA) |
| 686 | 4:49 | 40 | 60 | (x increase 5 mm) |