Wed May 24 15:58:53 2017, Patrick Coleman-Smith, Examination of Console Logs -- and a couple of reminders
|
| Quote: |
|
| Quote: |
|
I have tarred and zipped all 24 logs and shipped them back to the UK. Now I can browse through them.
Studying the "panics" :=
nnaida17 has one which is an NFS mount failure.
Do we understand why? Are there different/additional NFS mount options to be considered? Investigations ongoing :-)
nnaida20 and 22 have one each which are "Starting midas: Page fault in user mode with in_atomic() = 1 mm = c61bf200" but with different values for the mm=.
I am studying the web to understand why this may occur in a particular program. Both occur at similar places after "Starting midas".
There are reports of "Clock not locked. status = 0xc" during Setup Electronics which is a bit unusual. These occur in nnaida4, 17 and 22.
Also "Clock not locked. status = 0xd" in nnaida23,17,3,19,6,5,14,7,9. Further investigation to understand all these.
The bit allocation of the Clock Status word is:-
Bit 0 : Lock Detect bit from LMK03200 #1
Bit 1 : Lock Detect bit from LMK03200 #2
Bit 2 : Lock detect from the internal DCM for the mux clock.
Bit 3: iDelay ready signal
The LMK03200 are the two PLLs which are connected to the 50MHz input clock. The clock setup in the log directly before the error report for nnaiad17 had reported correctly setup and the ADCs had calibrated, these rely on a stable 50MHz from the LMK03200s.
I have also spotted some diagnostic information about the waveform readout that is useful.
Just a reminder..... when power cycling the equipment please leave the power off for at least 10 seconds to allow all the capacitors in the supply chain to discharge.
We do - standard procedure is to wait 20s.
Also note that the console monitor window in the Pi can be used to check that all FEE64s have "finished" the power-on sequence by using the "parse" button.
Since it doesn't use the DAQ software it won't lock-up and it will give an indication of progress.
We do check for further panics. I assume we would have to read each system log to check that the boot sequence and app load had completed?
If you do the parse before any action like RESET or SETUP the parse looks for the last line being the expected one which is :-
"Completed custom startup from /MIDAS/TclHttpd/Html/AIDA/RunControl/stats.defn.tcl"
When found the report from the parse will end with Finished OK for each FEE
|
|
|
Wed Sep 10 09:27:43 2014, Patrick, Elog appreciation
|
This is very interesting. Look forward to many happy interactions. |
Mon Sep 15 13:51:28 2014, Patrick, Odd spectra from running nnaida2 for 3 hours
|
I'm running nnaida2 with the PB-5 and an old adaptor.(1pF)
I've seen spectra like this before but previously they have shown apparent digital relationship between the troughs.
So maybe they show 3 peaks ?
If so I don't quite understand the mechanism......
I just realised that the shaping time is 0.5uS so maybe that is why ??
|
Wed Jan 14 15:29:01 2015, Patrick, Filtered switch mode PSU performance
|
Trying the AIDA format power supply with the simple filters installed.
The detector is attached and HV of 200v@3.8uA
Using one channel from each FEE64 as a guide to compare performance. Using the Integrate analysis function Peak width.
With the bench power supply and the restored setup for the ASICs.
FEE64 #11:1.4.L:311, #12:2.8.L:183, #13:1.4.L:202, #14:1.4.L:342
Change to the filtered power supply
FEE64 #11:1.4.L:345, #12:2.8.L:414, #13:1.4.L:311, #14:1.4.L:476
Add Braid between the LEMO00 connectors on the two adaptor boards using "croc" clips.
FEE64 #11:1.4.L:172, #12:2.8.L:141, #13:1.4.L:106, #14:1.4.L:161
Change the shaping time of all the ASICs from 0.5uS to 5uS
FEE64 #11:1.4.L:128, #12:2.8.L:127, #13:1.4.L:119, #14:1.4.L:199
I think this means the AIDA power supply with the simple filters is equivalent or better than the bench supply.
Good news I think.....
It needs a more extensive test ( more channels ? ) |
Thu May 5 14:44:48 2016, Patrick, Trigger selection explanations
|
Please request more information if the attached is not clear. |
Mon May 9 16:46:30 2016, Patrick, Update for FEE64 VHDL and Correlation browser windows 
|
| The attached VHDL file should be saved to /MIDAS/Aida and the FlashPgm.csh file edited to load "FEE_GF_Feb16_16.bin"
Use the Run Control Expert command to update the firmware on all the FEE64s.
Power cycle the FEE64s.
This will give a 25Mhz clock from the MACB Fast NIM output 0.
The attached .js and .tml files will change the Control browser window to allow access to a Correlation control window.
I have already installed the Correlation directory and files on aidas.
The Correlation Control window has two extra buttons. One to cause a Correlation trigger and the other to cause a reset to be sent out.
The Reset is only sent out if the Run Control is in the GO state.
To complete the change first make backup copies of the Aida.js and Aida.tml files that are currently in /MIDAS/TclHttpd/Html/AIDA
then copy the attached new versions into /MIDAS/TclHttpd/Html/AIDA.
These two files are in the attached .zip file. The Elog didn't like the .js file extension.
The Browser window reload should work but it may be required to clean your browser history to ensure the new version of the file is used. |
Wed May 11 11:24:09 2016, Patrick, Correlation Controls
|
Please note that the Force Trigger and Reset buttons in the Correlation Browser only have meaning if the FEE64
selected is the Master. |
Thu May 12 15:50:48 2016, Patrick, System Checks and firmware update 
|
| Added two checks to the System wide checks.
Modified the Firmware so the checks work properly.
One check reads the status of the FEE64 clocks and checks against expected value.
The other check reads the value from all the FEE64 Sync Error Counters, pauses for one second, then reads them again and compares with the first reading. Any change is reported as an error.
The Sync Error counter is incremented if the SYNC pulse arrives at a FEE64 when the Timestamp counter in the FEE64 is not at the correct value. |
Mon May 22 09:12:56 2017, Patrick, Consoles reporting Options not available.... defaults operational ?
|
I have noticed from the console logs reports concerning an inability to open the Options CONTENTS files for the FEE64s and hence failure to load the Options.
I have checked with similar files on nnsa here in Daresbury and they are set for permissions "-rwxrwxrwx. 1 npg npgstaff 1115 May 4 11:42 CONTENTS"
Please could you alter the permissions of all the Options files to agree with this and re-try the SETUP. |
Mon May 22 10:21:29 2017, Patrick, Console mapping to FEE64 please
|
Please attach the list of ttyUSB to FEE64 console connection .
|
Thu Dec 1 08:13:06 2016, PV,Liu, TD, Implantation profile in AIDA , after changing the ZDS setting to center at 41Al, AIDA 43_ 33 to 43  
|
Bigrips run 1127
AIDA run 43_ 33 to 43 |
Thu Dec 1 10:58:54 2016, PV, TD, Liu, Implantation profile in AIDA , after switch back to the previous ZDS setting (AIDA 43_63 to 43_71, bigrips run 1129)  
|
| |
Wed Nov 30 06:31:04 2016, PV, TD, RCF, Liu, Implantation profile in AIDA R39 2 to 9, after changing degrader at 13:30  
|
Degrader setting was:
Variable degrader:
0.5 mm W + 1 mm Al : in
0.3 mm W + 1 mm Al : out
1 mm W + 1 mm Al : in
Fix degrader:
20mm Al+ 0,2 mm Al
Large portion of the beam is passing through AIDA! We need to change the degrader |
Wed Nov 30 08:41:37 2016, PV, TD, RCF, Liu, Implantation profile in AIDA R39 37 to 46, after changing degrader at 16:23  
|
Degrader setting:
Variable degrader:
0.5 mm W + 1 mm Al : in
0.3 mm W + 1 mm Al : in
1 mm W + 1 mm Al : in
Fix degrader:
20mm Al+ 0,2 mm Al
See https://elog.ph.ed.ac.uk/AIDA/502 for comparison |
Mon Nov 28 13:12:31 2016, PV, AE, Liu, Implantation profile in AIDA with 8mm Al replacing 3 mm Pb    
|
Data for ~3 hrs: Nov 28th, 20:06 to 23:16
Bigrips run 1060 to 1062
AIDA run R30_ 2 to R30_40
Degrader setting: variable= (0.3mmW/1mmAl + 1mmW/1mmAl) + fixed= ( 8 mm Al)
IMPLANT PROFILE: Compare to previous setting (with 3mm Pb as fixed degrader) in elog entry https://elog.ph.ed.ac.uk/AIDA/487
In particular, attachment: https://elog.ph.ed.ac.uk/AIDA/161127_195411/run104x_imp_profile.png
The implantation positin for 40Mg seems to be well optimized (perhaps we can add ~0.5 mm Al to move it further downstream, but not more than that!).
IMPLANT EFFICIENCY: If we compare the number of Al and Mg ions in the ZDS PID for the three runs (~46000, see attachment 5) to the number of ions identified as implants (9389, see attachment 2), we get:
Implant efficiency ~ 20 % (=9389/46000)
P/S: attachment: hit pattern in BRIKEN with F11 plastic (beam), only for BigRIPS run 40Mg1060
|
Sun May 28 09:55:11 2017, PV, ADC offset value from pulser walkthrough run May2017/R28 R29   
|
ADC offset calculation using data from pulser walkthrough runs, see:
https://elog.ph.ed.ac.uk/AIDA/603
Attachment 1,2: excel and text file with tabulated ADC offset values.
Attachment 3,4: 2D histogram pulser amplitute vs channel number (with gain matching applied) for validating the
calculation.
Note: Channel with ADC offset=0 means ADC offset could not be calculated properly due to poor resolution/low
statistic |
Fri Jun 9 16:22:54 2017, PV, Saturday 10 June 00:00-08:00 28x
|
00:21 BigRIPS and BRIKEN stop their DAQ
AIDA run file R7_826
00:23 BRIKEN starts run 101
BigRIPS starts run 3107
AIDA on file R7_827
00:26 Offline Analysis of file RIBF128/R7_826- zero timewarps, zero MBS timewarps - see attachment 1
High Energy hit pattern spectra - see attachment 2
AIDA on file R7_828
zeroed Midas sort online spectra
00:36 *All* system wide checks OK
FEE64 Temperatures OK - see attachment 3
Good events statistics OK - see attachment 4
Merger and tape server running - see attachment 5, 6
Detector biases and leakage currents OK - see attachment 7
01:22 BigRIPS and BRIKEN stop their DAQ
AIDA run file R7_841
01:24 BRIKEN starts run 102
BigRIPS starts run 3108
AIDA on file R7_841
02:22 BigRIPS and BRIKEN stop their DAQ
AIDA run file R7_855
02:23 BRIKEN starts run 103
BigRIPS starts run 3109
AIDA on file R7_856
02:25 Offline Analysis of file RIBF128/R7_855- zero timewarps, 2 MBS timewarps - see attachment 8
High Energy hit pattern spectra - see attachment 9
AIDA on file R7_856
zeroed Midas sort online spectra
02:30 *All* system wide checks OK
FEE64 Temperatures OK - see attachment 10
Good events statistics OK - see attachment 11
Merger and tape server running - see attachment 12, 13
Detector biases and leakage currents OK - see attachment 14
03:24 BigRIPS and BRIKEN stop their DAQ
AIDA run file R7_870
03:26 BRIKEN starts run 104
BigRIPS starts run 3110
AIDA on file R7_871
03:42 fRC RF is down, beam is off
03:46 beam is back
04:18 beam is off, fRC RF is down
04:21 beam is back
04:31 BigRIPS and BRIKEN stop their DAQ
AIDA run file R7_886
04:32 BRIKEN starts run 105
BigRIPS starts run 3111
AIDA on file R7_887
04:35 Offline Analysis of file RIBF128/R7_886- zero timewarps, 1 MBS timewarps - see attachment 15
High Energy hit pattern spectra - see attachment 16
AIDA on file R7_887
zeroed Midas sort online spectra
04:39 *All* system wide checks OK
FEE64 Temperatures OK - see attachment 17
Good events statistics OK - see attachment 18
Merger and tape server running - see attachment 19, 20
Detector biases and leakage currents OK - see attachment 21
05:31 BigRIPS and BRIKEN stop their DAQ
AIDA run file R7_901
05:32 BRIKEN starts run 106
BigRIPS starts run 3112
AIDA on file R7_901
06:30 BigRIPS and BRIKEN stop their DAQ
AIDA run file R7_916
06:31 BRIKEN starts run 107
BigRIPS starts run 3113
AIDA on file R7_916
06:35 Offline Analysis of file RIBF128/R7_915- zero timewarps, 2 MBS timewarps - see attachment 22
High Energy hit pattern spectra - see attachment 23
AIDA on file R7_917
zeroed Midas sort online spectra
06:37 *All* system wide checks OK
FEE64 Temperatures OK - see attachment 24
Good events statistics OK - see attachment 25
Merger and tape server running - see attachment 26,27
Detector biases and leakage currents OK - see attachment 28
06:46 RRC power is down, it may take more than 1 hour to fix the problem
AIDA on file R7_920
06:48 BigRIPS and BRIKEN stop their DAQ
AIDA run file R7_920
06:52 BRIKEN starts run 108 (background run without beam)
AIDA on file R7_921 |
Sun Jun 11 08:23:23 2017, PV, Sunday 11 June 16:00-00:00 21x
|
16:40 beam lost - stripper foil problem
AIDA file RIBF128/R9_55
16:45 beam is back
AIDA file R9_57
17:19 BRIKEN and BigRIPS stop DAQs
AIDA on file R9_66
17:21 BigRIPS starts run 4024
BRIKEN starts run 134
AIDA on file R9_67
17:24 beam lost
AIDA on file R9_68
17:50 beam is still off
BRIKEN and BigRIPS stop DAQs
AIDA on file R9_74
17.52 Detector biases & leakage currents OK - see attachments 1
FEE64 Temperatures OK - see attachment 2
good events statistics stable (nnaida13 still ~140k) - see attachment 3
Merger and Tape server OK - see attachment 4,5
*all* system wide checks OK except ADC calibration for nnaida13
18:00 beam is back
BRIKEN starts run 135
BigRIPS starts run 4025
AIDA on file R9_76
18:05 analysis of file RIBF128/R9_77 no timewarps, 6 MBS timewarps ~1% dead time on nnaida13 - attachment 6
18:15 beam lost. RF is down.
AIDA on file R9_80
18:19 beam is back
AIDA on file R9_82
19:04 BRIKEN and BigRIPS stop DAQs
AIDA on file R9_93
19:05 BigRIPS starts run 4026
BRIKEN starts run 136
AIDA on file R9_94
19:40 analysis of file RIBF128/R9_102 no timewarps, 1 MBS timewarps - attachment 7
19:44 online high energy hit pattern - attachment 8
AIDA on file R9_104
zeroed Midas sort online histogram
19.50 Detector biases & leakage currents OK - see attachments 9
FEE64 Temperatures OK - see attachment 10
good events statistics stable - see attachment 11
Merger and Tape server OK - see attachment 12, 13
*all* system wide checks OK except ADC calibration for nnaida13
20:05 BRIKEN and BigRIPS stop DAQs
AIDA on file R9_110
20:07 BigRIPS starts run 4027
BRIKEN starts run 137
AIDA on file R9_111
20:11 Accelerator people stop the beam to fix the stripper system for about 30 min.
BRIKEN and BigRIPS stop DAQs
AIDA on file R9_112
21:12 Beam is back
AIDA on file R9_127
21:12 BigRIPS starts run 4028
BRIKEN starts run 138
AIDA on file R9_127
21:21 offline analysis RIBF128/R9_128 rates
*** DSSSD # 1 count: 469757 old count: 409726 dt: 1.01 s LEC rate: 59182.53 Hz
*** DSSSD # 2 count: 688773 old count: 600379 dt: 1.01 s LEC rate: 87144.65 Hz
*** DSSSD # 3 count: 226922 old count: 196673 dt: 1.01 s LEC rate: 29821.47 Hz
*** DSSSD # 4 count: 197996 old count: 173086 dt: 1.01 s LEC rate: 24557.93 Hz
*** DSSSD # 5 count: 75519 old count: 66217 dt: 1.01 s LEC rate: 9170.53 Hz
*** DSSSD # 6 count: 161720 old count: 141631 dt: 1.01 s LEC rate: 19805.07 Hz
*** DSSSD # 1 count: 6 old count: 6 dt: 1.01 s HEC rate: 0.00 Hz
*** DSSSD # 2 count: 212 old count: 179 dt: 1.01 s HEC rate: 32.53 Hz
*** DSSSD # 3 count: 54 old count: 49 dt: 1.01 s HEC rate: 4.93 Hz
*** DSSSD # 4 count: 20 old count: 16 dt: 1.01 s HEC rate: 3.94 Hz
*** DSSSD # 5 count: 43 old count: 37 dt: 1.01 s HEC rate: 5.92 Hz
*** DSSSD # 6 count: 117 old count: 105 dt: 1.01 s HEC rate: 11.83 Hz
zeroed Midas sort histograms
21:38 beam lost due to stripper problem
AIDA on file R9_134
21:41 analysis of file RIBF128/R9_134 no timewarps, no MBS timewarps - attachment 14
20:05 BRIKEN and BigRIPS stop DAQs
AIDA on file R9_138
22.00 Detector biases & leakage currents OK - see attachments 15
FEE64 Temperatures OK - see attachment 16
good events statistics OK (no beam now) - see attachment 17
Merger and Tape server OK - see attachment 18, 19
*all* system wide checks OK except ADC calibration for nnaida13
22:09 beam is back
BigRIPS starts run 4029
BRIKEN starts run 139
AIDA on file R9_142
22:42 online implantation profile - attachment 20
AIDA on file R9_151
zeroed Midas sort online histograms
23:10 BRIKEN and BigRIPS stop DAQs
AIDA on file R9_159
23:11 BigRIPS starts run 4030
BRIKEN starts run 140
AIDA on file R9_159
23:37 analysis of file RIBF128/R9_165 no timewarps, 2 MBS timewarps - attachment 21 |
Tue Jun 6 00:57:49 2017, PJW, TD, Tuesday 6 June 08.00-16.00 16x
|
08.57 Stop DAQ
AIDA file RIBF128/R6_24
09.00 BigRips starts run 3016
BRIKEN starts run 16
AIDA on file R6_25
09:23 biases and leakage currents recorded attachments 1 and 2
09.36 online spectra per DSSSD x versus y (HEC) - see attachment 3
per DSSSD E_p versus E_n (HEC) - see attachment 4
09.39 offline analysis RIBF128/R6_36
ADC & disc data synchronised - see attachment 5
rates
*** DSSSD # 1 count: 475974 old count: 407247 dt: 1.04 s LEC rate: 66335.14 Hz
*** DSSSD # 2 count: 695537 old count: 595776 dt: 1.04 s LEC rate: 96289.08 Hz
*** DSSSD # 3 count: 284002 old count: 245156 dt: 1.04 s LEC rate: 37494.07 Hz
*** DSSSD # 4 count: 197428 old count: 169943 dt: 1.04 s LEC rate: 26528.46 Hz
*** DSSSD # 5 count: 58436 old count: 49831 dt: 1.04 s LEC rate: 8305.53 Hz
*** DSSSD # 6 count: 130742 old count: 111691 dt: 1.04 s LEC rate: 18387.98 Hz
*** DSSSD # 1 count: 2 old count: 2 dt: 1.04 s HEC rate: 0.00 Hz
*** DSSSD # 2 count: 92 old count: 82 dt: 1.04 s HEC rate: 9.65 Hz
*** DSSSD # 3 count: 387 old count: 332 dt: 1.04 s HEC rate: 53.09 Hz
*** DSSSD # 4 count: 281 old count: 251 dt: 1.04 s HEC rate: 28.96 Hz
*** DSSSD # 5 count: 37 old count: 31 dt: 1.04 s HEC rate: 5.79 Hz
*** DSSSD # 6 count: 36 old count: 33 dt: 1.04 s HEC rate: 2.90 Hz
all SortSas spectra and online histograms zero'd
09.48 analysis RIBF128/R6_35 deadtime <0.5%, zero ts timewarps, 2 MBS timewarps - see attachment 6
10.00 FEE64 temperatures OK - see attachment 7
good events stats - see attachment 8
merger - no error/warning messages - see attachment 9
nnaida13 waveforms ASICS 1-4 100*20us = 2ms range - see attachments 10-13
10.00 Stop DAQ
AIDA file RIBF128/R6_42
10.01 BigRips starts run 3017
BRIKEN starts run 17
AIDA on file R6_43
10.09 *all* system wide checks OK
11:00 stop daq
aida file r6_59
11.01 BigRips starts run 3018
BRIKEN starts run 18
AIDA on file R6_60
11:59 stop daq
aida file R6_76
12:01 Bigrips starts run 3019
BRIKEN starts run 19
aida on file R6_77
12:59 stop daq
aida file R6_94
13:01 Bigrips starts run 3020
BRIKEN starts run 20
aida on file R6_95
13.51 biases and leakage currents recorded attachments 15 & 16
14:00 stop daq
aida file R6_112
14:03 Bigrips starts run 3021
BRIKEN starts run 21
aida on file R6_113
14:57 beam stopped
15:00 stop daq
aida file R6_130
15:01 beam back
15:02 Bigrips starts run 3022
BRIKEN starts run 22
aida on file R6_130 |
Mon Feb 22 15:19:52 2016, PJCS, T9 System changed to version 8
|
I have changed the T9 system to be using Version 8.
Tests using the detector and pulser seem to be ok.
Transmission to the Merge and Merging operating ok
Shaping time 8uS and threshold 64.
Note:-
The Leading Edge Discriminator has changed in Version 8 and is a true implementation of a Leading Edge Discriminator. With hysteresis which requires the input signal to go below the threshold before allowing another trigger.
The Delay setting on the LED web page is removed.
The LED web page is aware of the version being used ( shown at the top of the page ) as the Threshold for the LED is an ADC value ( 0 to 16383 ) rather than a difference from the current baseline.
For a positive waveform where the baseline is expected to be about 8192 a value of 9000 will potentially give a trigger.
For a negative waveform where the baseline is expected to be about 8192 a value of 7000 will potentially give a trigger.
Example window attached.
I would value feedback.
|