...
Done for tonight
Nov/3:
Plan of the day:
9am-9pm Day shift will continue with 5Hz beam running with XPP as primary expt. We expect to start ~9am for access to continue towards full setup for RD53A and cosmic telescope then run until 9pm.
Activities: Timon, Ben, Su Dong, Zijun, Ke, Sanha
...
13:00 Carsten called. Lead Glass counters (Scope ESA brown trace) was left at 900V and 10mV/div scope display last night in anticipation of primary beam. He raised the HV (to 2K?) and scope back 50mv/div. Signal size 50-100 mV for the ~50 particles per shot. He moved the counter slightly to verify signal went away so it looked like crudely beam doesn't have duffused tail.
14:00 Full set of 3000e threshold tunes obtained for the LBNL cosmic telescope modules and they are temporarily stored at /home/beam/daq/rce/moduleconfigs/fei4bexample/ directory on esadutdaq1 for the RCE DAQ calibrations with the 6 modules give a temp name 94-22-0x (x=0-5) until their real IDs are known.
15:00 Created the EUDET configuration LBNL_cosmic_telescope.conf to include all 6 planes of cosmic telescope as DUT. After a few errors we learned that FEID, SensorID also need to have distinctive values to make EUDAQ really happy.
19:00 A long access to figure out RD53A setup. Early setup for 0x0A57 (cable D) stopped working while 0x0A53 (cable C) always had trouble. This looked like an issue with the new PCIe card for 0x0A53 might not have the fully compatible firmware. Recovered D while tomorrow is schedule to debug out C.
19:30 Added a LEMO between the first module of cosmic telescope HitOR and HSIO2 LEMO bank chan #1 (2nd socket from back edge) hoping to run the telescope in HitOR triggered mode. This is not strictly correct electrically as HitOR is 1.2V LVCMOS while HSIO2 LEMO port expects TTL. Trying our luck here.
Select data worth looking at:
~3:00 PM Run 346. A long run with the LBNL cosmic telescope and full MIMOSA. Su Dong, Zijun, and Sanha found out from this run that the second FEI4B module of the LBNL cosmic telescope wasn't outputting anything. This module was almost completely masked out during the fasttune process. Sanha tried re-calibrating and re-tuning the module for a while, but could not fix it. (Su Dong and Zijun checked for any hardware issues later in the afternoon/evening, but couldn't fix it either.)Zijun spotted a lose HV connector on this module but that didn't solve the problem. Data cable swapped with the 3rd module (block CAT6e) still didn't make much impression. More attempts to calibrate didn't get around the problem such that bypassing the crosstalk stage only delay the masking out to the noise test stage. Another issues was that many modules got a funny vertical strips of bad pixels on the top right corner from calibration in a similar manner. Timon asked us to check possible RCE readout errors, but this might be more likely due to the possible tangle of the 6 modules sharing the same fei4bexample 'module' folder ?
~3:50 PM Run 350. Timon got a first successful run with one RD53A module. This was with device 0x0A57 on cable D and cable B to TLU DUT #3 (mask +0x8).
from 7:45 PM to 8:25 PM Run 400. A long run with one RD53A module (0x0A57) and full MIMOSA (full 10k events). The trigger latency parameter for YARR adjusted slightly to put the L1ID closer to the center of DAQ buffer. The beam did not cover the entire RD53A sensor area, so Ke and Sanha tried tuning the fine position to move the module around.
from 8:50 PM to 9:00 PM Run 407. A short run (due to beam shutdown) with somewhat better aligned RD53A position. The short-side (horizontal direction) is well-covered by the beam. On the long-side (vertical), the beam still seems to be 100~150 pixels off the center; the module has to be moved 5~7.5mm down (up...?). Note that the beam shape is extremely asymmetric in the vertical-direction. Current RBV config: X coarse 115.41mm, Y coarse 3.83mm, Y fine 7.69mm, X fine -56.53mm, Rotation 213.51mm
21:00 Beam off
Nov/4
9am-9pm beam for ESTB
Plan of the day:
- Debug the RD53A 0x0A53 (C) setup
- Special timing tests
- Cosmic telescope self-trigger mode ? Recovering 2nd module ?
- Systematic RD53a data taking runs
- Cosmic telescope data runs to map out all device areas