Page History

Schedule

Day shift: 9am–9pm /  Night shift : 9pm–9am

...

10:30pm MCC thought they are close to be done with tuning so we started to move Caladium coarse X in reduced x direction and running the Caladium only readout. Before reaching the beam spot, the secondary scatter was ~50 particles/shot but once beam spot came into the frame, that turned to be more like 2000/crossing. Beam spot was also very wide in X ( more than the 2cm MIMOSA aperture). Asked MCC to reduce rate and spot size. a few tries didn't make much impression until a move to close down SL-10 to -0.5. That brought the rate down to ~100 particles/crossing. Beam spot is filling good fraction of aperture ans looks like a good tuning setup to start with tomorrow. The Caladium XYstage X/Ycoarse RBV=115.4/3.8mm (Y is very close to min limit). Run 336 tuning beam spot picture below. 

Image RemovedImage Added

Done for tonight      

...

• Switch to tilted data taking with the two LBNL RD53a
• More cosmic telescope data with separate cosmicGui partition 
• DAQ clock phase vs beam tests 
• Depletion HV scan 

Activities   (Adrien, Timon, Ben, Maurice, Charilou, Patrick, Mark, Sanha, SD) 

9:30 Sanha called the beam control room to start the beam. There is a water leakage in the klystrons, and the repair/replacement will take 3-4 hours. Test beam data taking will be postponed until the repair/replacement is complete (probably in the early afternoon).

9:50 cosmicRun 051. Testing the current telescope configuration for any random noises. Cyclic trigger set to 100Hz. Almost no random noise is seen after 100s.

11:50 Beam is back on (earlier than expected!)

11:52 Started data taking

00 RD53a DUT stage slight rotated to get slight charge sharing in "phi". Tape measured distances derived an angle of 11.8^o. Reconstructed angle from photo gave 13^o  which are consistent with errors.  

Image Added	Image Added	Image Added
RD53a DUT position before Nov/6 (perpendicular)	RD53a DUT position before Nov/6 (zoom)	Nov/6 DUT after rotation

11:50 Beam is back on (earlier than expected!)

11:52 Started data taking

12:12:35 Channel 10 beam trigger disappeared while Ch 11 was driving the cosmic telescope at 5 Hz happily. Tried to run ch 10 trigger with a generated 10Hz from the trigger module and that also worked. Call Carsten and Mike Dunning and both had no idea how that could happen. The trigger unit was clearly receiving the accelerator signal correctly to run ch 11 while the down stream part delivering trigger to ESTB was also fine with the generated 10Hz.   

...

22:11 After graphing the ToT from runs 522-530, noticed that it was not changing as much as expected, leading us to believe that maybe remotely changing the HV might not be working. To check, we set the voltage to 0 and took data but did not see what we expected. The camera pointed at the equipment rack didn't have the HV PS in the frame so we requested an access to go down and see whether remotely chaning the HV actually works or not. We confirmed that the HV was changing but the script must have an indexing error on its for loop because whenever the HV is set, it always ends up at a value 1 off from what was set. For example if we were at 20V and set it to 15 we would end at 16 and if we were at 10 and set to 15 we would end up at 14. There is also an Errcode flashing n Keithley at each stage. After figuring out that the voltage was changing but not to where we expected, a new webcam was moved to have the HV panel in view so it could be monitored.

22:52 Beam restored and Run 534 started.

2223:03 MC called to take away beam after Run 534 was completed.

...

Nov/7 

ESTB beam **11am–9pm**     

Plan of the Day

• SLAC Rd53a device 0x0A97 (25x100 pixel 150um active thickness) replaces the current channel D 0x0A57 (50x50) early enough in the morning to allow Timon tuning it remotely 
• Setup a cleaned up TTL beam trigger from Ch-11 for cosmic telescope to see if the double timing peaks still exist.
• Main data taking runs will be steep tilted 25x100 sensors. One DUT at a time, first 0x0A54 (100um LBNL) then 0x0A97 (150um SLAC). 

Activities:  Adrien, Mark, Charilou, Cesar, SD 

10:30 Replaced 0x0A58(labelled A57 in the configs) with SLAC RD53A device 0x0A97.

11:12 Beam was up and started taking runs, but no events were being built, called Timon and he said module A54 does not like to be power cycled. So we requested access to go down and fix it. Fortunately on power cycle was sufficient to bring A54 back. 

11:47 Beam was turned back on after module started working again and Run 541 was started with just one Yarr producer in the run control for the LBL RD53A A54 module. Timon is working on tuning the SLAC device to get it up and taking data.

11:55 Lost beam for a couple of minutes but it came back up when Carsten called.

12:52 MC called to say one of the klystrons in the injector is missing triggers so the beam might be coming in and out.

12:57 Stopped run 543 to change HV back to 100V.

13:40 Timon finished remotely tuning the SLAC module A97 but when a run was started there were no hits seen by the module and there were some infrequent readout errors (received data not valid). Timon is attempting to fix the problem but for now only the LBL module A54 is being run.

Access to remove the A97 to leave A54 by itself and changed to large tilt angle ~ -60^o (had to rotate clockwise when looking from above, since mount frame would be in the beam line before sensor if rotated the other way).  Made choice of 60 degrees based on expectation of long cluster of 8x25um pixels for 100um thick sensor. More steep tilt would need to remount RD53a to the opposite side of frame to avoid frame in the beam line.  Couldn't mount 2nd sensor - missing screws to slide 2nd frame into beam line. One device at a time is better anyway to reduce the large multiple scattering at this steep angle. For this tile angle, hits will traverse pixel sideways with a path length of 25um/cos(60deg) ~29um.  Expected signal  peak for such short length is <2000e and really needs pixel threshold to be 1000e or less. Our pixel threshold is tuned for 1000e.        

Image Added	Image Added

The resulting ~4-5 pixel length of "clusters"  might be due to the artificial local XY coordinates are define against the 50x50 chip channel grid to achieve 25 micron pitch with staggered bumps ?    

Run_544 (13 deg)	Image Added	Image Added	Image Added
Run_565 (62 deg)	Image Added	Image Added	Image Added

17:50  Took a short run with cosmic telescope joining the main partition (so that trigger is driven by Ch-10 with NIM Quad discriminator cleanup). The FE-I4 data had no no double timing peak here in comparison to the standalone cosmicGui run just taken with trigger Ch-10 (TTL). This seems to indicate the standalone Ch-11 cosmic triggers was causing the double time peaks. The RTM ports were meant to be NIM so we were triggering on -ve undershoort after ripples of the main TTL trigger pulse ?    

...

21:40. We're done! Called to stop beam for entry. Going to pack up.