| |
ID |
Date |
Author |
Subject |
|
|
257
|
Wed Apr 21 11:27:55 2021 |
OH | Wed 21st April 12:00-16:00 |
12:30 MBS has crashed
This time AIDA is still running fine.
Stats ok - attachment 1
Temperature - attachment 2
Bias and leakage currents - attachment 3
All system wide checks ok *except*
Base Current Difference
aida12 fault 0x0 : 0x19 : 25
FPGA Timestamp error counter test result: Passed 11, Failed 1
If any of these counts are reported as in error
The ASIC readout system has detected a timeslip.
That is the timestamp read from the time FIFO is not younger than the last
Now also note errors on aida7 and aida03 in the merger TS errors
(0 represents the sum across all FEE)
0 1355800 0x0014b018
1 0 0x00000000
2 0 0x00000000
3 33 0x00000021
4 0 0x00000000
5 0 0x00000000
6 0 0x00000000
7 10 0x0000000a
8 0 0x00000000
9 0 0x00000000
10 0 0x00000000
11 1355757 0x0014afed
15:30 CA takes over
Stats ok - attachment 4
Temperature - attachment 5
Bias and leakage currents - attachment 6
all system wide checks ok *except*
Base Current Difference
aida12 fault 0x0 : 0x19 : 27
FPGA Timestamp error counter test result: Passed 11, Failed 1
If any of these counts are reported as in error
The ASIC readout system has detected a timeslip.
That is the timestamp read from the time FIFO is not younger than the last
15:42 db check and ucesb ok |
|
|
287
|
Thu Apr 29 16:56:42 2021 |
OH | Config changes for 16FEE |
New set of ASIC settings produced 2021Apr29-13-16-00
- Note no longer odd/even for polarity of signal
New set of Options file for FEEs - Points to the new ASIC settings
New layouts for histograms grouped by side of the detector. Heavily weighted to the front side in terms of number of his
/MIDAS/Linux/startup/NewMerger Updated line from "./master64 -i 12 -l 16 -p 11001 &" to "./master64 -i 16 -l 16 -p 11001 &"
/MIDAS/DB/EXPERIMENTS/MERGE/Options/aidas-gsi/CONTENTS updated the number of links to 16.
System wide checks passed *except aida03 ADC calibration*
System left running to no storage. |
|
|
295
|
Tue May 4 21:26:43 2021 |
OH | Alpha run |
22:26 Tape server set up to write to directory May21
DAQ stopped
Slow comparator set to 0x64 for all FEE64 and an ASIC check performed
Pulser turned off
DAQ started
~300k in merger - 38kB per second to file
Statistics good (all FEE show 0 bar FEE4 at 3k) - attachment 1
All system wide checks ok apart from FPGA check
Base Current Difference
aida13 fault 0x0 : 0x62 : 98
FPGA Timestamp error counter test result: Passed 15, Failed 1
If any of these counts are reported as in error
The ASIC readout system has detected a timeslip.
That is the timestamp read from the time FIFO is not younger than the last
Histograms zeroed.
DSSD1 at 130V
DSSD2 at 100V
08:47 Found DAQ running at c. 3M data items/s / 13MB/s
Switched Tape Server to no storage mode
[npg@aidas-gsi ~]$ ls -lrth /TapeData/May21
total 113G
-rw-rw-r--. 1 npg npg 64K May 4 22:24 R1_0
-rw-rw-r--. 1 npg npg 64K May 4 22:24 R1_1
-rw-rw-r--. 1 npg npg 64K May 4 22:24 R1_2
-rw-rw-r--. 1 npg npg 64K May 4 22:24 R1_3
-rw-rw-r--. 1 npg npg 64K May 4 22:24 R1_4
-rw-rw-r--. 1 npg npg 64K May 4 22:24 R1_5
-rw-rw-r--. 1 npg npg 64K May 4 22:24 R1_6
-rw-rw-r--. 1 npg npg 64K May 4 22:24 R1_7
-rw-rw-r--. 1 npg npg 64K May 4 22:24 R1_8
-rw-rw-r--. 1 npg npg 64K May 4 22:24 R1_9
-rw-rw-r--. 1 npg npg 1.3G May 5 06:15 R1_10
-rw-rw-r--. 1 npg npg 2.0G May 5 06:17 R1_11
-rw-rw-r--. 1 npg npg 2.0G May 5 06:20 R1_12
-rw-rw-r--. 1 npg npg 2.0G May 5 06:23 R1_13
-rw-rw-r--. 1 npg npg 2.0G May 5 06:25 R1_14
-rw-rw-r--. 1 npg npg 2.0G May 5 06:28 R1_15
-rw-rw-r--. 1 npg npg 2.0G May 5 06:30 R1_16
-rw-rw-r--. 1 npg npg 2.0G May 5 06:33 R1_17
-rw-rw-r--. 1 npg npg 2.0G May 5 06:36 R1_18
-rw-rw-r--. 1 npg npg 2.0G May 5 06:38 R1_19
-rw-rw-r--. 1 npg npg 2.0G May 5 06:41 R1_20
-rw-rw-r--. 1 npg npg 2.0G May 5 06:43 R1_21
-rw-rw-r--. 1 npg npg 2.0G May 5 06:46 R1_22
-rw-rw-r--. 1 npg npg 2.0G May 5 06:49 R1_23
-rw-rw-r--. 1 npg npg 2.0G May 5 06:51 R1_24
-rw-rw-r--. 1 npg npg 2.0G May 5 06:54 R1_25
-rw-rw-r--. 1 npg npg 2.0G May 5 06:57 R1_26
-rw-rw-r--. 1 npg npg 2.0G May 5 06:59 R1_27
-rw-rw-r--. 1 npg npg 2.0G May 5 07:02 R1_28
-rw-rw-r--. 1 npg npg 2.0G May 5 07:04 R1_29
-rw-rw-r--. 1 npg npg 2.0G May 5 07:07 R1_30
-rw-rw-r--. 1 npg npg 2.0G May 5 07:10 R1_31
-rw-rw-r--. 1 npg npg 2.0G May 5 07:12 R1_32
-rw-rw-r--. 1 npg npg 2.0G May 5 07:15 R1_33
-rw-rw-r--. 1 npg npg 2.0G May 5 07:18 R1_34
-rw-rw-r--. 1 npg npg 2.0G May 5 07:20 R1_35
-rw-rw-r--. 1 npg npg 2.0G May 5 07:23 R1_36
-rw-rw-r--. 1 npg npg 2.0G May 5 07:25 R1_37
-rw-rw-r--. 1 npg npg 2.0G May 5 07:28 R1_38
-rw-rw-r--. 1 npg npg 2.0G May 5 07:31 R1_39
-rw-rw-r--. 1 npg npg 2.0G May 5 07:33 R1_40
-rw-rw-r--. 1 npg npg 2.0G May 5 07:36 R1_41
-rw-rw-r--. 1 npg npg 2.0G May 5 07:39 R1_42
-rw-rw-r--. 1 npg npg 2.0G May 5 07:41 R1_43
-rw-rw-r--. 1 npg npg 2.0G May 5 07:44 R1_44
-rw-rw-r--. 1 npg npg 2.0G May 5 07:46 R1_45
-rw-rw-r--. 1 npg npg 2.0G May 5 07:49 R1_46
-rw-rw-r--. 1 npg npg 2.0G May 5 07:52 R1_47
-rw-rw-r--. 1 npg npg 2.0G May 5 07:54 R1_48
-rw-rw-r--. 1 npg npg 2.0G May 5 07:57 R1_49
-rw-rw-r--. 1 npg npg 2.0G May 5 08:00 R1_50
-rw-rw-r--. 1 npg npg 2.0G May 5 08:02 R1_51
-rw-rw-r--. 1 npg npg 2.0G May 5 08:05 R1_52
-rw-rw-r--. 1 npg npg 2.0G May 5 08:07 R1_53
-rw-rw-r--. 1 npg npg 2.0G May 5 08:10 R1_54
-rw-rw-r--. 1 npg npg 2.0G May 5 08:13 R1_55
-rw-rw-r--. 1 npg npg 2.0G May 5 08:15 R1_56
-rw-rw-r--. 1 npg npg 2.0G May 5 08:18 R1_57
-rw-rw-r--. 1 npg npg 2.0G May 5 08:20 R1_58
-rw-rw-r--. 1 npg npg 2.0G May 5 08:23 R1_59
-rw-rw-r--. 1 npg npg 2.0G May 5 08:26 R1_60
-rw-rw-r--. 1 npg npg 2.0G May 5 08:28 R1_61
-rw-rw-r--. 1 npg npg 2.0G May 5 08:31 R1_62
-rw-rw-r--. 1 npg npg 2.0G May 5 08:34 R1_63
-rw-rw-r--. 1 npg npg 2.0G May 5 08:36 R1_64
-rw-rw-r--. 1 npg npg 2.0G May 5 08:39 R1_65
-rw-rw-r--. 1 npg npg 2.0G May 5 08:41 R1_66
-rw-rw-r--. 1 npg npg 1.6G May 5 08:44 R1_67
[npg@aidas-gsi ~]$
Rate increased c. 06.15
multiple ASICs in multiple FEE64s hot HEC channels
ASIC check load restores rates to those at beginning of May21/R1
Switched Tape Server to storage mode - file May21/R1_67
08.53 All system wide checks OK *except*
Base Current Difference
aida07 fault 0x0 : 0x1 : 1
aida08 fault 0x0 : 0x1 : 1
aida13 fault 0x62 : 0x9380 : 37662
FPGA Timestamp error counter test result: Passed 13, Failed 3
If any of these counts are reported as in error
The ASIC readout system has detected a timeslip.
That is the timestamp read from the time FIFO is not younger than the last
Most recent merger errors
MERGE Data Link (2497): bad timestamp 7 3 0xd1fc813c 0x073033d6 0x00001083773033d6 0x167c1083773033d6 0x167c108377304b46
MERGE Data Link (2497): bad timestamp 7 3 0xd1ce7ff9 0x07303ba6 0x0000108377303ba6 0x167c108377303ba6 0x167c108377304b46
MERGE Data Link (2497): bad timestamp 7 3 0xd1dd806e 0x07303ba6 0x0000108377303ba6 0x167c108377303ba6 0x167c108377304b46
MERGE Data Link (2497): bad timestamp 7 3 0xd1ed7fc1 0x07303ba6 0x0000108377303ba6 0x167c108377303ba6 0x167c108377304b46
MERGE Data Link (2497): bad timestamp 7 3 0xd1fd803c 0x07303ba6 0x0000108377303ba6 0x167c108377303ba6 0x167c108377304b46
MERGE Data Link (2497): bad timestamp 7 3 0xd1cf8066 0x07304376 0x0000108377304376 0x167c108377304376 0x167c108377304b46
MERGE Data Link (2497): bad timestamp 7 3 0xd1de8110 0x07304376 0x0000108377304376 0x167c108377304376 0x167c108377304b46
MERGE Data Link (2497): bad timestamp 7 3 0xd1ee8086 0x07304376 0x0000108377304376 0x167c108377304376 0x167c108377304b46
MERGE Data Link (2497): bad timestamp 7 3 0xd1fe7ff7 0x07304376 0x0000108377304376 0x167c108377304376 0x167c108377304b46
MERGE Data Link (2497): bad timestamp 7 3 0xd1c38041 0x0e60a6d6 0x000010832e60a6d6 0x167c10832e60a6d6 0x167c108377304b46
09.04 FEE64 temps OK - attachment 2
ADC data item stats - attachment 3
1.8.L spectra - attachments 4 & 5
1.8.W spectra - attachments 6 & 7
Grafana DSSSD bias & Leakage current most recent 24h - attachment 8
DSSSD bias & leakage current - attacment 9
11:32 R1 stopped to realign boards and check situation in S4 |
|
|
297
|
Wed May 5 20:10:16 2021 |
OH | Wednesday 5 May Alpha run |
21:10 After all of the works in S4 today the noise in the system was considerably worse
It was decided that before starting a new alpha run a powercycle would be performed.
The powercycle has had no effect on the rates. They are still terrible.
The difference between yesterday and today is:
- Adaptor cards for FEE9 and 13 were re-aligned as they were previously misaligned
- bPlast has been plugged in and biased
All system wide checks ok
Statistics threshold at 0xa - attachment 1
Rate spectra (FEE5 does have events in all channels just noise is dominated by a few) - attachment 2
Waveforms - attachments 3 and 4
Pulser turned off and threshold raised to 0x64
Statistics - attachment 5
21:19 Alpha run started to May21/R4*
08:51 DAQ continues OK - file May21/R4_23
FEE64 temps OK - attachment 8
ADC data items OK - attachment 9
1.8.W spectra - attachments 6 & 7
no change cf. yesterday pm
Grafana - most recent 12h DSSSD bias & leakage current - attachment 10
DSSSD biases & leakage currents - attachment 11
Tape Server/Merger - attachment 12
09:44 R4 stopped |
|
|
305
|
Tue May 11 07:21:24 2021 |
OH | Tuesday 11 May |
08:20 System wide checks all ok except
Base Current Difference
aida01 fault 0xc10c : 0xc10e : 2
aida02 fault 0xbe2a : 0xbe2c : 2
aida03 fault 0xf665 : 0xf667 : 2
aida04 fault 0xeabd : 0xeabf : 2
aida05 fault 0x36c8 : 0x36ca : 2
aida06 fault 0x2ea2 : 0x2ea4 : 2
aida07 fault 0x9186 : 0x9188 : 2
aida08 fault 0x5443 : 0x5445 : 2
White Rabbit error counter test result: Passed 8, Failed 8
Understand the status reports as follows:-
Status bit 3 : White Rabbit decoder detected an error in the received data
Status bit 2 : Firmware registered WR error, no reload of Timestamp
Status bit 0 : White Rabbit decoder reports uncertain of Timestamp information from WR
and
Base Current Difference
aida01 fault 0xc10c : 0xc10e : 2
aida02 fault 0xbe2a : 0xbe2c : 2
aida03 fault 0xf665 : 0xf667 : 2
aida04 fault 0xeabd : 0xeabf : 2
aida05 fault 0x36c8 : 0x36ca : 2
aida06 fault 0x2ea2 : 0x2ea4 : 2
aida07 fault 0x9186 : 0x9188 : 2
aida08 fault 0x5443 : 0x5445 : 2
White Rabbit error counter test result: Passed 8, Failed 8
Understand the status reports as follows:-
Status bit 3 : White Rabbit decoder detected an error in the received data
Status bit 2 : Firmware registered WR error, no reload of Timestamp
Status bit 0 : White Rabbit decoder reports uncertain of Timestamp information from WR
Statistics still high - attachment 1
Temperatures ok - attachment 2
Bias and leakage currents ok - attachment 3 |
|
|
315
|
Thu May 13 23:58:05 2021 |
OH | Friday 14th May 00:00 - 08:00 |
00:00 OH Takes over.
PULSER SETTINGS
---------------------------
Pulse is ON
Positive Tail Pulse
Trigger Source is Internal Clock
Trigger Threshold is 3.5
Amplitude : 2.0 Volts
Rep Rate : 2.0 hZ
Delay : 250.0 ns
Fall Time : 1 ms
Attenuation : 1
Display is : Volts
Equivalent keV is : 200.0
Ramp Start at 0.01 Volts
Ramp Stop at 9.99 Volts
Ramp Start at 1.0 keV
Ramp Stop at 999.0 keV
Ramp Time is 60 seconds
# Ramp Cycles is 1
OK
0x210
p+n Thresholds 0xa (100keV)
n+n Threshold 0x20 (320keV)
01:00 System wide checks
Clock status ok
ADC calibration fail as expected (Waveforms off)
WR Errors
Base Current Difference
aida01 fault 0xf932 : 0xf933 : 1
aida02 fault 0x62ec : 0x62ed : 1
aida03 fault 0x8679 : 0x867a : 1
aida04 fault 0xf0e4 : 0xf0e5 : 1
aida05 fault 0x9db8 : 0x9dbf : 7
aida06 fault 0x7f18 : 0x7f19 : 1
aida07 fault 0xdd2c : 0xdd2d : 1
aida08 fault 0x1557 : 0x1558 : 1
White Rabbit error counter test result: Passed 8, Failed 8
Understand the status reports as follows:-
Status bit 3 : White Rabbit decoder detected an error in the received data
Status bit 2 : Firmware registered WR error, no reload of Timestamp
Status bit 0 : White Rabbit decoder reports uncertain of Timestamp information from WR
FPGA Errors
Base Current Difference
aida05 fault 0x0 : 0x2 : 2
FPGA Timestamp error counter test result: Passed 15, Failed 1
If any of these counts are reported as in error
The ASIC readout system has detected a timeslip.
That is the timestamp read from the time FIFO is not younger than the last
Statistics ok - attachment 1
Temp ok - attachment 2
Bias and leakage current ok - attachment 3
01:42 Comparing the CS of AIDA3 and 4
Stats have been running for a while (Believe since 5am)
Looking at the counter ratio - attachment 4
We still have a deadtime of around 14% in FEE4 (Assuming FEE3 has no dead time)
01:56 Noticed /media/ThirdDrive was at 97% full
Let DESPEC locals know I would like to use the next run stop to change the directory.
They said they could do it now so they stopped their run.
Changed the symbolic link to /media/1e2....
Now writing to R4_
03:26 MBS DAQ Stopped as beam stopped
03:33 Beam back now and DAQ running again
04:44 System wide checks as before
Statistics ok - attachment 5
Temperatures ok - attachment - 7
Bias and leakage currents ok - attachment 6
05:53 MBS stops run as beam drops
06:00 MBS started a new run as beam is back
07:37 System wide checks clock ok and FPGA as before
WR additional difference on FEE5
Base Current Difference
aida01 fault 0xf932 : 0xf933 : 1
aida02 fault 0x62ec : 0x62ed : 1
aida03 fault 0x8679 : 0x867a : 1
aida04 fault 0xf0e4 : 0xf0e5 : 1
aida05 fault 0x9db8 : 0x9dc0 : 8
aida06 fault 0x7f18 : 0x7f19 : 1
aida07 fault 0xdd2c : 0xdd2d : 1
aida08 fault 0x1557 : 0x1558 : 1
White Rabbit error counter test result: Passed 8, Failed 8
Understand the status reports as follows:-
Status bit 3 : White Rabbit decoder detected an error in the received data
Status bit 2 : Firmware registered WR error, no reload of Timestamp
Status bit 0 : White Rabbit decoder reports uncertain of Timestamp information from WR
Statistics ok - attachment 8
Temp ok - attachment 9
Bias and leakage ok - attachment 10
|
|
|
327
|
Wed May 19 06:59:33 2021 |
OH | Wednesday 19th May 08:00 - 16:00 |
08:00 OH Takes over for CA
Thresholds 0xc for p+n and 0x19 for n+n ASICs 1-3 and 0x64 for n+nASIC4
PULSER SETTINGS
---------------------------
Pulse is ON
Positive Tail Pulse
Trigger Source is Internal Clock
Trigger Threshold is 3.5
Amplitude : 2.0 Volts
Rep Rate : 2.0 hZ
Delay : 250.0 ns
Fall Time : 1 ms
Attenuation : 1
Display is : Volts
Equivalent keV is : 200.0
Ramp Start at 0.01 Volts
Ramp Stop at 9.99 Volts
Ramp Start at 1.0 keV
Ramp Stop at 999.0 keV
Ramp Time is 60 seconds
# Ramp Cycles is 1
Max average dead time in R14_586 3.2% which is 9.6% on spill
Stable from yesterday
10:02 System wide checks. All ok expect WR
Base Current Difference
aida05 fault 0x500 : 0x554 : 84
White Rabbit error counter test result: Passed 15, Failed 1
Understand the status reports as follows:-
Status bit 3 : White Rabbit decoder detected an error in the received data
Status bit 2 : Firmware registered WR error, no reload of Timestamp
Status bit 0 : White Rabbit decoder reports uncertain of Timestamp information from WR
Statistics - Attachment 1
Temp - attachment 2
Bias and leakage currents ok - Attachment 3
11:17 A new run was started as the microspill has been changed. I believe to optimise FRS deadtime.
11:45 They are still working on it
12:05 Beam off for a bit while they optimise spill
12:15 System wide checks ok expect WR
Base Current Difference
aida05 fault 0x500 : 0x567 : 103
White Rabbit error counter test result: Passed 15, Failed 1
Understand the status reports as follows:-
Status bit 3 : White Rabbit decoder detected an error in the received data
Status bit 2 : Firmware registered WR error, no reload of Timestamp
Status bit 0 : White Rabbit decoder reports uncertain of Timestamp information from WR
Statistics - Attachment 4
Temp - Attachment 5
Bias - Attachment 6
13:11 Magda has said that the changes to the spill structure only gained them a few percent in dead time
Further changes could be done, but would take at least two hours
13:19 Dead time following the current spill changes
R14_648 R14_649 R14_650 R14_651 Sum DT (S) Avergage DT (%) On Spill DT (%)
FEE 244.823 252.168 247.155 240.421 984.567
0 0.063 0.025 0.105 0.096 0.289 0.029353005 0.088059015
1 3.981 4.907 4.17 2.484 15.542 1.578561947 4.73568584
2 0.01 0 0.121 0.779 0.91 0.092426417 0.277279251
3 3.625 2.972 2.766 3.335 12.698 1.289704002 3.869112006
4 0.088 0.1 0.12 0.136 0.444 0.045095966 0.135287898
5 9.392 5.798 9.835 8.01 33.035 3.355282068 10.0658462
6 0.153 0.075 0.01 0.517 0.755 0.076683456 0.230050367
7 7.4 7.565 7.703 6.415 29.083 2.953887343 8.86166203
8 0.221 0.606 1.321 0.539 2.687 0.272911849 0.818735546
9 0 0 0 0 0 0 0
10 1.381 0.368 1.196 1.091 4.036 0.409926394 1.229779182
11 0.066 0.025 0.039 0.017 0.147 0.014930421 0.044791264
12 0.166 0.041 0.062 0.024 0.293 0.029759275 0.089277825
13 0 0 0 0 0 0 0
14 0.71 0 0.005 0.074 0.789 0.08013675 0.240410251
15 0.239 0.17 0.208 0.286 0.903 0.091715444 0.275146333
16 0 0 0 0 0 0 0
14:03 System wide checks ok - WR same difference as before
Statistics - attachment 7
Temperatures - attachment 8
Bias and leakage currents - attachment 9 |
|
|
337
|
Thu May 20 14:56:33 2021 |
OH | Thursday 20th May 16:00 - 24:00 |
16:00 p+n threshold 0xc (120keV)
n+n threshold DSSD2 0x20 (250keV) ASICS 1-3, 0x64 ASIC4
n+n threshold DSSD2 0x19 (250keV) ASICS 1-3, 0x64 ASIC4
Dead time has increased from yesterday. From the elog this appears to coincide with their changing of the spill structure.
17:30 Grafana informs us we have hit 10uA on DSSD2. This is fine with the size of the detector
18:12 Gregor noticed that at 18:02 the rate in AIDA increased. This could be related to the autofill starting around now.
The deadtimes in FEE6 and 8 have risen to around 6.25%.
Looking at this mornings and yesterday evenings fill times this behavior isn't observed
18:30 The rates still seem to be increased so is unlikely to be due to the filling which finished at least 10 minutes ago
18:49 Have tried raising the thresholds to 0x1a for the y side strips of DSSD2
This has brought the deadtime of AIDA06 down to 5.53% (This seems to have just been a statistical fluctuation and the rate went back up again in the next file)
18:12 Raised threshold to 0x1b for ASIC1-3 of FEE6 and 8
18:15 System wide checks ok except WR as usual
Base Current Difference
aida05 fault 0x500 : 0x56d : 109
White Rabbit error counter test result: Passed 15, Failed 1
Understand the status reports as follows:-
Status bit 3 : White Rabbit decoder detected an error in the received data
Status bit 2 : Firmware registered WR error, no reload of Timestamp
Status bit 0 : White Rabbit decoder reports uncertain of Timestamp information from WR
Statistics increased at 18:02 still working on - attachment 2
FEE temp - attachment 3
Bias and leakage current - attachment 4
20:51 System wide checks ok - WR same as before
Statistics still high - attachment 5
Temperatures ok - attachment 6
Bias and leakage currents ok - attachment 7
22:52 Statistics still high - attachment 8
Temp ok - attachment 9
Bias and leakage current ok - attachment 10
System wide checks ok - WR difference still 109 |
|
|
380
|
Fri Sep 3 13:39:42 2021 |
OH | Additional noise tests performed at GSI |
Contents of an email from NH to OH and TD about tests performed on an additional bias supply:
This email was sent to you by someone outside the University.
You should only click on links or attachments if you are certain that the email is genuine and the content is safe.
so I looked at the other supply in the lab (in a NIM crate there, cable direct to DSO)
Still see the same noise wave - also it looked a lot worse at 50V but that may be a worse NIM crate or something else - the current also wasn't 0 (calibration?)
More unusually the signals remain even if the NIM crate is off (DSO_Lab_NoP) and when the SHV is removed from the HV completely (DSO_Lab_NoCable) |
|
|
381
|
Mon Oct 18 13:01:04 2021 |
OH | Proxy config |
Proxy for firefox and anydesk |
|
|
382
|
Mon Oct 18 13:03:23 2021 |
OH | DHCPd.conf backup |
|
|
|
383
|
Mon Oct 18 14:20:32 2021 |
OH | Top bar launchers |
launcher1
TclHttpd @8015 for AIDA
/MIDAS/Linux/startup/HTTPD
launcher2
TclHttpd @8115 for AIDA
/MIDAS/Linux/startup/HTTPD@8115
launcher3
TapeServer
/MIDAS/Linux/startup/TapeServer
launcher4
New Merger for AIDA
/MIDAS/Linux/startup/NewMerger
Launcher5
MBS Relay
/MIDAS/Linux/startup/datarelaymbs |
|
|
384
|
Tue Oct 19 16:17:49 2021 |
OH | AIDA-gsi server to centos 7 |
Following advice of CU have updated the server to centos 7.
To do this a new 500GB SSD was purchased and installed in the enclosure and a clean install of centos7 was installed to this.
An npg account was setup with the same password as previously. Likewise the su password is the same
The existing 500GB HDD can then be mounted using the disk tool in Applications/Utilities/Disks (Requires administrator rights)
The MIDAS_Releases directory was tarballed and coppied across to its respective place on the new install.
A symlink from /MIDAS to this location was created
dhcpd.conf was copied across. dhcp needed to be installed on the machine as well.
/etc/hosts was also required to get the hostnames for the rpis working
oh, GREAT, LayOut, Patrick and analyser directories were also tarballed and moved across
.desktop files have been created for all of the shell scripts used to start the servers.
A gnome extension Frippery panel favourites has also been installed which allows the shortcuts to be stored in the top panel similar to sl6
Early tests appear to be working.
Will test with the FEEs later this week.
Currently the machine is booted into centos but will be booting into sl6 tomorrow to run some tests. |
|
|
386
|
Thu Oct 21 09:08:41 2021 |
OH | MIDAS start up messages |
|
|
|
387
|
Thu Oct 21 09:33:08 2021 |
OH | Noise tests - 21st Oct 2021 |
Pulser was left on overnight with the bias filters on
First plot is FEE14 not FEE8
Double peaking is observed in both polarities of FEE. |
|
|
388
|
Thu Oct 21 16:18:51 2021 |
OH | FEE and Adaptor board groundings |
During investigations into the noise today by NH and OH a couple of findings were made on the grounding of the FEEs and Adaptor boards.
- The adaptor boards have no connection to the FEE ground over the ERNI connector
- Currently we are providing one via a ground cable between the FEE Al cooling and the Lemo ground on the adaptor board
- The Al cooling plate is not electrically isolated from the copper plate on the ASIC and both are connected to the electrical ground on the FEE
- Verified with 0 resistance between plate and HDMI ground shield
- The FEE is electrically isolated from the frame but when cabling is connected they show 0 resistance
- With electrics disconnected but water still connected they show 200kOhm
- With the bias core going to FEE14 and the braid going to FEE8 better performance in FEE14 is obtained by disconnecting FEE8 adaptor board from the ground
- The cost of this is the rate of FEE8 goes up to 300k
- It is essential to have the adaptor board ground on the FEE ground but unsure why having both adaptor boards connected to their respective grounds makes one worse
- The resistance between all FEEs is not zero. Some show a 5Ohm and some show a 35Ohm resistance between each other
|
|
|
391
|
Fri Oct 29 10:49:01 2021 |
OH | Noise tests - 28th October -29th October |
Plan for the day was to connect a mechanical ground to the FEEs connected to DSSD0 1, 2, 3, 4, 9, 10, 11 and 12
This was done by connecting thick copper cable to the mechanical ground wires on the AIDA frame (These ground wires are connected to the platform ground which is earthed properly we are told)
Two thick copper wires were run each one for the top and right side and one for the bottom and left side.
Each cable was connected to the FEEs with a star of smaller cables going to the adapter boards.
Before connection the potential difference between the FEE ground and the mechanical ground was 16mV.
After connection the potential difference was 3-4mV.
It was checked that both the NIM ground and the PSU ground pins were on the same ground as the mechanical ground. It was just the FEE modules on a different ground.
Photos of connection at end of attachments.
It was found later in the afternoon that the 3mV drop comes as a result of the resistance of the bolt used to connect all the thinner wires to the thicker copper braid.
Very good rates observed in all p+n strips but high rates in n+n.
The large oscillations observed in waveforms yesterday are gone though. High frequency component remains
Statistics - attachment 1
Rates spectra - attachment 2
Zoomed in rates spectra - attachment 3
p+n aida11 1.8.W - attachment 4
n+n aida02 1.8.W - attachmeFEE Width
9 60.25
1 64.18
10 55.76
11 64.81
3 56.21
12 48.54nt 5
We then reconfigured the PSU so that the FEEs for a given detector were all on the same PSU
Rates are observed to drop across all p+n fees
Statistics - attachment 6
Rates spectra - attachment 7
Rates spectra y max 10 - Attachment 8
p+n aida 12 1.8.W - attachment 9
n+n aida 02 1.8.W - attachment 10
Pulser was then connected to all p+n channels but left off
Rates - attachment 11
Rates spectra - attachment 12
Rates spectra ymax10 - attachment 13
Pulser was then switched on
Rates spectra - attachment 14
Statistics - attachment 15
Pulser peaks p+n - attachment 16
Pulser widths
FEE Width
9 60.25
1 64.18
10 55.76
11 64.81
3 56.21
12 48.54
n=n pulser was then added to both 2 and 4
Pulser peaks n+n - attachment 17
Pulser peaks p+n - attachment 18
FEE Width
9 62.88
1 65.30
10 55.18
11 64.47
3 51.77
12 50.22
2 196.00
4 271.57
29 October
Test adding LK2,3,4 to n+n
n+n all LK1,2,3,4
p+n all lk 2,3,4
Makes p+n side worse - attachment 22
Remove LK3 from n+n
n+n 1,2,4
p+n all LK2,3,4
A slight improvement on previous
attachment 23
Remove LK2 and 4 from n+n
Remove LK3 from all p+n except 1 and 3 which are the two non isolated cables
attachment 24 |
|
|
398
|
Wed Mar 2 09:08:44 2022 |
OH | DAQ Status 2nd March 2022 |
DAQ was found yesterday with none of the FEEs reporting any good events on any FEE - attachment 1
Temperature menu is still responsive and all FEEs report a temperature
Looking at the white rabbit timestamps aida09 has a gibberish timestamp - attachment 2
Merger shows no data arriving as expected - Attachment 3
Merger data buffers for each FEE - attachment 4
Merger time errors - attachment 5
DAQ has not yet been restarted in case Patrick wanted to look. |
|
|
399
|
Wed Mar 2 10:05:13 2022 |
OH | DAQ Status 2nd March 2022 |
> DAQ was found yesterday with none of the FEEs reporting any good events on any FEE - attachment 1
> Temperature menu is still responsive and all FEEs report a temperature
> Looking at the white rabbit timestamps aida09 has a gibberish timestamp - attachment 2
> Merger shows no data arriving as expected - Attachment 3
> Merger data buffers for each FEE - attachment 4
> Merger time errors - attachment 5
>
> DAQ has not yet been restarted in case Patrick wanted to look.
Looking at the first attachment..... aida09 has rebooted. So it is not setup at all.
This has caused the NewMerger to hang .... which surprises me .... as I thought it was designed to spot a bad FEE and continue with the rest.
Yes I will have a look today as I'm in Daresbury.
More later ...... |
|
|
417
|
Mon May 2 09:52:20 2022 |
OH | Shifter checklist 2022 |
Every 30 minutes:
- Reload statistics (Web browser tab screen 1, workspace 3)
- Are all FEEs still showing a rate?
- If one shows 0 after multiple reloads Call Oscar or Tom.
- IGNORE FOR TIME BEING Options database monitor (Top middle terminal screen 2, workspace 3)
- Has the message changed since the last check?
- If so copy the message and place in elog
- Do the ucesb scalers make sense? (Web browser, screen 2, workspace 5)
- If one DSSD is reporting kHz of implants when the others are much less it is likely an ASIC getting stuck.
- Perform and ASIC check (ASIC control tab, web browser, screen 1, workspace 3)
- Ensure "Act on all FEE" and "Act on all asic" selected
- Click on drop down menu in the bottom of the screen and select check ASIC control
- It will take a minute or so be patient (MIDAS can only respond to one command at once so don't try to do anything else)
- A pop up will appear check that all options say ok
- Has the implant rate gone to a more normal amount?
- If not feel free to call
Every two hours:
- Take a screenshot of the statistics page (Web browser tab screen 1, workspace 3)
- Compare to the previous screenshot to check if anything has drastically changed
- Take a screenshot of the temperatures (Web browser tab screen 1, workspace 3)
- Do they all appear stable?
- Take a screenshot of the bias and leakage currents - (Top left terminal, screen 2, workspace 3)
- Perform the five system wide checks (Web browser tab screen 1, workspace 3)
- Ignore the system wide checks for ADC calibration (ADCs are turned off so they will all fail)
- Check memory information also fails.
- Make a note in the elog of which tests are successful
- If failed copy the text from the white box into the elog and make a note of it
- Enter the screenshots into the elog
- Update the leakage current spreadsheet (Web browser, screen 2, workspace 5) |