...
- take two runs for each position of the chip
- 150
- 140
- 130
- 120
- 115
- 110
- 105
- 100
- 95
- 90
- take a snapshot for each position, save the picture on the desktop, note the name of the picture in the table
- note the position of the motor in the table
- when reached perpendicular to the beam take the data for the end of the beam
- when the beam is off (and all angles are covered) notify Ben/Timon so we can tune the chip to a different threshold and wait for futher instructions
- before each start of the run, load the config files
- restart the DAQ system
- check the correlation plots Telescope - RD53a
18:00 Ke and SD on shift
18:20 Adjusted DUT rotation to RBV=151.24 (step -10). Rotation stage stuttered a bit but got there eventually.
18:30 Runs 187-189 had some suspiciously low rate of DUT hits, online mon crash because hitting reset during start. Finally got Run 190 going with reconfig.
18:35 Run summary info now recorded in Google Doc Run List directly.
19:30 Noticing the mean hit rate per event rather low seems to be due to beam going on and off. So the total number of events may not be a reliable number to use for the actual track statistics.
19:41 Run 191 reached 10000 events but very low entries in correlation plots so we just let the Run roll over to 192 without saving/reseting monitoring histograms.