 Tue Nov 26 13:14:40 2019, Alexander Burker, 2019-11-23f proton CT, DSSD-Tracker, 252.7, , 17, , none,
|
2019-11-23 21:46
TLU (Rack-mounted) failed: "netzwerk error" (even after a power cycle) |
|
Tue Nov 26 13:16:21 2019, Alexander Burker, 2019-11-23f proton CT, , Noise, , 24, , none,
|
2019-11-24 13:43
no TLU error was observed |
|
Tue Nov 26 13:17:11 2019, Alexander Burker, 2019-11-23f proton CT, DSSD-Tracker, 252.7, , 25, , none,
|
2019-11-24 14:05
promptly aborted due to "missing reason" (maybe Felix has some notes) |
|
Tue Nov 26 13:18:35 2019, Alexander Burker, 2019-11-23f proton CT, DSSD-Tracker, 252.7, , 26, 129767, none,
|
2019-11-24 14:06 - 14:20
Latency = 45 (found too late)
TLU (Rack-mounted) failed: "netzwerk error" |
|
Tue Nov 26 13:19:21 2019, Alexander Burker, 2019-11-23f proton CT, DSSD-Tracker, 252.7, , 28, , none,
|
2019-11-24 14:24
Latency = 43 (found too late)
TLU (Rack-mounted) failed: "netzwerk error" |
|
Tue Nov 26 13:19:49 2019, Alexander Burker, 2019-11-23f proton CT, DSSD-Tracker, 252.7, , 29, , none,
|
2019-11-24 14:26
Latency = 41 (this setting was kept)
TLU (Rack-mounted) failed: "netzwerk error" |
|
Tue Nov 26 13:30:58 2019, Alexander Burker, 2019-11-23f proton CT, DSSD-Tracker, 252.7, , 30, , none,
|
2019-11-24 14:30
Random Triggers
TLU (Rack-mounted) failed: "netzwerk error" |
|
Tue Nov 26 13:31:57 2019, Alexander Burker, 2019-11-23f proton CT, DSSD-Tracker, 252.7, , 32, , none,
|
2019-11-24 14:40
Coincidences Trigger
TLU (Rack-mounted) failed: "netzwerk error" |
|
Tue Nov 26 13:33:50 2019, Alexander Burker, 2019-11-23f proton CT, DSSD-Tracker, 252.7, , 33, , none,
|
2019-11-24 15:08
Standalone TLU
TLU (Rack-mounted) failed: "netzwerk error" |
|
Tue Nov 26 13:34:50 2019, Alexander Burker, 2019-11-23f proton CT, DSSD-Tracker, 252.7, , 34, , none,
|
2019-11-24 15:12
Standalone TLU
TLU (Rack-mounted) failed: "netzwerk error" |
|
Tue Nov 26 13:35:11 2019, Alexander Burker, 2019-11-23f proton CT, DSSD-Tracker, 252.7, , 35, , none,
|
2019-11-24 15:13
Standalone TLU
TLU (Rack-mounted) failed: "netzwerk error" |
|
Tue Nov 26 13:35:33 2019, Alexander Burker, 2019-11-23f proton CT, DSSD-Tracker, 252.7, , 37, , none,
|
2019-11-24 15:50
Standalone TLU + Tracker (Tera did not record data)
TLU (Rack-mounted) failed: "netzwerk error" |
|
Tue Nov 26 13:36:33 2019, Alexander Burker, 2019-11-23f proton CT, DSSD-Tracker, 100.4, , 40, 39546, none,
|
2019-11-24 16:42
"TLU not on network" (Alex does not know what was not on which network, maybe Felix' notes are more complete) |
|
Tue Nov 26 13:39:13 2019, Alexander Burker, 2019-11-23f proton CT, DSSD-Tracker, 252.7, , 41, 202410, none,
|
2019-11-24 16:48
"TLU not on network"
Data is good for Alignment |
|
Tue Nov 26 13:39:51 2019, Alexander Burker, 2019-11-23f proton CT, Drehtisch, 100.4, , 42, , Alu, 0
|
2019-11-24 17:21
TERA DAQ failed |
|
Tue Nov 26 13:40:21 2019, Alexander Burker, 2019-11-23f proton CT, Drehtisch, 100.4, , 43, 313433, Alu, 0
|
2019-11-24 17:21
Run was interrupted to re-load config. A regular pattern in the hit maps suggested a problem with FIR, however the data looks good and a projection
could be reconstructed |
|
Tue Nov 26 13:46:13 2019, Alexander Burker, 2019-11-23f proton CT, Drehtisch, 100.4, , 44, 687822, Alu, 0
|
2019-11-24 17:54
I've forgotten to increment run number before pressing start. Run 43 was likely renamed to oldName_2019-11-24….xml and .dat
To correctly filter the issues due to FIR, Hao suggested using a neighbor cut of 15 to 20. |
|
Tue Nov 26 13:48:56 2019, Alexander Burker, 2019-11-23f proton CT, Drehtisch, 100.4, , 45, , Alu, 90
|
2019-11-24 18:57
TERA DAQ failed |
|
Tue Nov 26 13:58:58 2019, Alexander Burker, 2019-11-23f proton CT, Drehtisch, 100.4, , 46, 1001850, Alu, 90
|
| 2019-11-24 18:59 - 20:27 |
|
Tue Nov 26 13:59:48 2019, Alexander Burker, 2019-11-23f proton CT, Drehtisch, 100.4, , 47, , Alu, 45
|
2019-11-24 20:28
TERA DAQ failed |
|