...
8:30 Given the success of the RD53A readout, we will take data through the night to gather more statistics at more stable beam conditions and lower particle rate to allow easy debuting of potential issues and more assured offline reconstruction .
10:30 They turned on the beam, and we asked them to decrease the number of e-s / beam, so we now have about 8 clusters / plane. The beam spot remained roughly the same place and size but perhaps somewhat wider. The 8 clusters/event rate is good for both RD53 reconstruction and HGTD data at the same time.
The DUT Y is all covered, but we only (in the initial configuration) have coverage from pixel 100 - 300 in X.
Run Number | Start time | End time | Number of Events | Window coordinates (DUT) | Comments |
---|---|---|---|---|---|
90 | 02/06/18 11pm | 02/06/18 11:25 pm | 8655 | x=100~300 | |
91 | 02/06/18 11:27 pm | ||||
92 | 02/06/18 11:27 pm | 03/06/18 00:27 am | 19007 | We hadn't saved the histogram at the end of run 91, so the run histogram just has twice as much data. But the beam conditions were stable between these two runs. | |
93 | 03/06/18 00:30 am | 03/06/18 01:03 am | 9021 | ||
94 | 03/06/18 01:05 am | 03/06/18 01:36 am | 9284 | ||
95 | 03/06/18 01:39 am | 03/06/18 02:07 am | 9013 | ||
96 | moving the RD53: up 1cm (Motor 3: Y fine : > 1cm) | ||||
97 | 03/06/18 02:24 am | 03/06/18 02:54 am | 9113 | ||
98 | 03/06/18 02:57 am | 03/06/18 | 6845 | Changed shift to Ke and Jannicke Stopped early because we were looking at Sensor 0 for measuring the number of events, will be using number of events from Sensor 2 from now on - it does not have hot pixels! | |
99 | 03/06/18 3:14 am | 03/06/18 3:40am | 9210 | ||
100 | 03/06/18 3:40am | 03/06/18 4:06am | 9406 | ||
101 | 03/06/18 4:06am | 03/06/18 4:34am | 9425 | ||
102 | 03/06/18 4:34am | 03/06/18 5:04 | 9173 | ||
103 | 03/06/18 5:04am | 03/06/18 5:31am | 9150 | Moved RD53 (Motor 3 Y:fine < 2 cm) RBV from step at 10.00mm now. Aiming for coverage of 0-100 in X | |
104 | 03/06/18 5:31am | 03/06/18 | 9245 | Moved RD53 (Motor 3 Y:fine > 2 mm) RBV from step at 12.00mm now, adjustment was made to get slightly better coverage in the 50-100 range. Looks good now! | |
105 | 03/06/18 | 6:12 | Run stopped early - noticed histograms stopped filling ERROR IN DUT DATA PRODUCER vent: tag(0) l1id(14 bcid(11398) hits (0) ERROR IN TLU PRODUCER: Error sending data: While copying this error message pressed control C in TLU Producer restarted ./STARTRUN reran ./TLUProducer.exe -r 172.27.100.8:44000 reconfigured EUDAQ in EUDAQ RD using ni_coins_YARR because it seems like it was the most recently updated starting run 933 Histograms not popping up; killing all jobs and restarting went through steps 1-3 Step 3 shows errors in finding libraries (not sure if critcal) TestDataCollector NiProducer for linux Online Monitor
...Done! START OF DAQ COMPLETE [tfuser@ar-eudaq eudaq-1.7]$ ./OnlineMon.exe: /usr/lib64/libstdc++.so.6: version `CXXABI_1.3.8' not found (required by ./OnlineMon.exe) ./OnlineMon.exe: /usr/lib64/libstdc++.so.6: version `GLIBCXX_3.4.20' not found (required by ./OnlineMon.exe)
NEEDED TO SOURCE SETUP_EUDAQ.SH NEED TO PUT THIS IN TWIKI!!!!!
Step 4 Cannot connect to pixel@172.27.104.52 ssh_exchange_identification: Connection closed by remote host We can ping 172.27.104.52 but cannot log into it? Why?
./TLUProducer.exe -r 172.27.100.8:44000 bin/YarrProducer -h configs/controller/specCfgExtTrigger.json -c configs/connectivity/example_rd53a_setup.json -s configs/scans/rd53a/std_exttrigger.json -r 172.27.100.8
Called Su Dong: suggested we look at size of files
df -k
Filesystem 1K-blocks Used Available Use% Mounted on /dev/sda1 20030100 18989568 16392 100% /
moved data files to /home/tfuser/data_20180603/ Now down to 81% full
Filesystem 1K-blocks Used Available Use% Mounted on /dev/sda1 20030100 15243540 3762420 81% /
|