AIDA GELINA BRIKEN nToF CRIB ISOLDE CIRCE nTOFCapture DESPEC DTAS EDI_PSA 179Ta CARME StellarModelling DCF K40
  AIDA, Page 17 of 44  ELOG logo
New entries since:Thu Jan 1 01:00:00 1970
Entry  Sun May 28 10:25:11 2017, TD, Analysis of RIBF123R1/R23 R23.txt
 
Entry  Sun May 28 09:55:11 2017, PV, ADC offset value from pulser walkthrough run May2017/R28 R29 ADC_offset_R2829_BRIKENMay2017.xlsADC_offset_R2829_BRIKENMay2017.txtcal_histo.pngcal_histo.root
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
Entry  Sun May 28 09:20:29 2017, TD, Analysis of RIBF123R1/R21 R21.txt
 
Entry  Sun May 28 02:16:04 2017, TD, CB, Sunday 28 May 16x
10.15 DAQ continues OK 
      Current file May2017/R31_239

      Detector biases; leakage currents OK - see attachments 1 & 2
      FEE64 Temperatures OK - see attachment 3
      good events; statistics OK - see attachment 4
      No warnings/errors reported by merger since DAQ GO - see attachment 5

      *all* system wide checks OK *except* ADC calibration of nnaida1, 21 and nnaida1 clock status (status=6)

10.30 E17/F11 ambient temperature +23.8 deg C, RH 40.9%, d.p. +9.6 deg C
      Julabo FL11006 set point +20 deg C, actual +20.0 deg C, water level OK (c. 95% - refilled)

10.35 Layouts 1, 3, 4, 7 and 8 - see attachments 6-13
      Note - as expected, zero HEC events, layouts 5 & 6 not shown

10.58 DAQ stop - transient timeout nnaida1 - followed by successful stop
      File May2017/R31_248

      Delete R31

11.12 Disable data transfer
      DAQ GO - transient timeout nnaida1 - followed by successful start 
      nnaida1 system console - see attachment 14

12:00 Moved plastic veto scintillator downstream in an attempt to reduce noise
      Rates in noisy FEEs reduced by 20-30%

14:30 DAQ continues OK
      Found that pulser induces counts in some HEC (nnaida20, 14 in particular). See attachment 15. Pulser off
removes these events completely.
      These events could be mistaken for implantation events during data acquisition.
      Increasing the fast comparator threshold HEC from 2 -> 3 suppresses the events. Increasing the threshold
to 4 does not appear to have further effects.
      Even with the increased threshold some HEC (e.g. 1.0H) still see the pulser. See attachment 16 (fast
comparator threshold HEC was 0x3).
      Checked data is synchronised in file R32_33

15:29 Set the threshold back to 2. We will perform this cut off-line in the analysis. 
Entry  Sat May 27 05:38:39 2017, CB, TD, OH, Saturday 27 May 9x
13.38 DAQ continues OK 
      Current file May2017/R27_49

      Detector biases; leakage currents OK - see attachment 1
      FEE64 Temperatures OK - see attachment 2
      good events; statistics OK - see attachment 3
      No warnings/errors reported by merger since DAQ GO - see attachment 4

      *all* system wide checks OK *except* ADC calibration of nnaida1, 21 and nnaida1 clock status (=6)

10.30 E17/F11 ambient temperature +23.8 deg C, RH 40.9%, d.p. +9.6 deg C
      Julabo FL11006 set point +20 deg C, actual +20.0 deg C, water level OK (c. 75%)

13:40 Stopped DAQ running on alpha background calibration run
      Current file May2017/R49
      tyUSB7 log (nnaida1) attached

13:43 Detector bias OFF

14.16 DAQ starts
      File May2017/R28

      Pulser walkthrough

      BNC PB-4
      Amplitude 90,000-10,000 @ 10,000 step
      x5 attenuator IN
      t_r 100ns tau_d 50us
      - polarity
      frequency 250Hz range
      delay MIN, tail pulse, INT ref

      ASIC settings 2017Mar27-16.12.39 *except*
      slow comparator 0x0a
      LEC/MEC fast comparator 0x20

      See attachment 6

14.25 DAQ stop OK

14.27 DAQ starts
      File May2017/R29

      Pulser walkthrough

      BNC PB-4
      Amplitude 12,000-2,000 @ 2,000 step

      ASIC settings 2017Mar27-16.12.39 *except*
      slow comparator 0x0a
      LEC/MEC fast comparator 0x20

      See attachment 7

14.34 DAQ stop OK

14.38 DAQ starts
      File May2017/R30

      Background, pulser OFF

      ASIC settings 2017Mar27-16.12.39 *except*
      slow comparator 0x0a
      LEC/MEC fast comparator 0x20

15.16 DAQ stop OK
      May2017/R30_8

16:17 DAQ starts okay 
      current run May2017/R31_0
      leakage current and temperature fine
      see attachment 8 and 9


  
Entry  Fri May 26 05:19:40 2017, TD, Offline analysis RIBF123R1/R23_44 to R23_70 
Observe same noise structures to https://elog.ph.ed.ac.uk/AIDA/600

Extended noisy periods ~few Hz compose of fine structure with period ~350us
Entry  Fri May 26 02:20:42 2017, CB, OH, NN, Friday 26 May 15x
10.20 DAQ continues OK 
      Current file May2017/R27_22

      Detector biases; leakage currents OK - see attachment 1
      FEE64 Temperatures OK - see attachment 2
      good events; statistics OK - see attachment 3
      No warnings/errors reported by merger since DAQ GO - see attachment 4

      *all* system wide checks OK *except* ADC calibration of nnaida1, 21 and nnaida1 clock status (=6)

10.30 E17/F11 ambient temperature +24.2 deg C, RH 39.7%, d.p. +9.7 deg C
      Julabo FL11006 set point +20 deg C, actual +20.0 deg C, water level OK (c. 75%)

      Left DAQ running on alpha background calibration run
      
      ttyUSB7 log (nnaida1) attached
      GUI got stuck while attempting to drag-and-drop ttyUSB7 to ELOG to upload. Terminal still working and
confirmed Merger working OK.
      Killed nautilus process to get GUI unstuck. Uploaded ttyUS7 via Browse -> Upload button on ELOG instead.

15.51 DAQ continues OK 
      Current file May2017/R27_28

      Detector biases; leakage currents OK - see attachment 6
      FEE64 Temperatures OK - see attachment 7
      good events; statistics OK - see attachment 8
      No warnings/errors reported by merger since DAQ GO - see attachment 9

      *all* system wide checks OK *except* ADC calibration of nnaida1, 21 and nnaida1 clock status (=6)

15.53 E17/F11 ambient temperature +24.1 deg C, RH 40.1%, d.p. +9.8 deg C
      Julabo FL11006 set point +20 deg C, actual +20.0 deg C, water level OK (c. 75%)

      Left DAQ running on alpha background calibration run
      
      ttyUSB7 log (nnaida1) attached

19.20 DAQ continues OK 
      Current file May2017/R27_31

      Detector biases; leakage currents OK - see attachment 11 & 12
      FEE64 Temperatures OK - see attachment 13
      good events; statistics OK - see attachment 14
      No warnings/errors reported by merger since DAQ GO - see attachment 15

      *all* system wide checks OK *except* ADC calibration of nnaida1, 21 and nnaida1 clock status (status=6)

19.30 E17/F11 ambient temperature +24.2 deg C, RH 38.5%, d.p. +9.2 deg C
Entry  Thu May 25 03:03:38 2017, TD, Offline analysis of R23_91 to R23_115 13x
Offline analysis of RIBF123R1_91 to R23_115

See https://elog.ph.ed.ac.uk/AIDA/583 & https://elog.ph.ed.ac.uk/AIDA/594

No evidence of ~1s oscillations but we do observe ~360us  oscillations in HEC-HEC, LEC-LEC and HEC-LEC times

Attachment 1 - per DSSSD HEC-HEC time 2.56us/channel - 387-246=141=361us

Attachments 2-4 - per DSSSD LEC-LEC time 2.56us/channel - 858-721=138=353us

Attachments 5-7 - per DSSSD HEC-LEC time 2.56us/channel - 699-567=132=338us

Note also 'random' spikes in s2200 DSSSD#1 HEC-LEC time. This may suggest an increase
in noise or fluctuations in noise level. 

Attachment 8 - per DSSSD m_p versus m_n - note additional feature in DSSSD#1 & #2 

Attachments 9-10 - per DSSSD HEC-LEC time 163.84us/channel - no ~1s oscillations
Entry  Thu May 25 02:11:04 2017, CB, TD, Thursday 25 May 10x
10.10 DAQ continues OK 
      Current file May2017/R26_17

      Detector biases; leakage currents OK - see attachment 1
      FEE64 Temperatures OK - see attachment 2
      good events; statistics OK - see attachment 3
      No warnings/errors reported by merger since DAQ GO - see attachment 4

      *all* system wide checks OK *except* ADC calibration of nnaida1, 21 and nnaida1 clock status (=6)
      

10.17 E17/F11 ambient temperature +24.2 deg C, RH 42.8%, d.p. +10.7 deg C
      Julabo FL11006 set point +20 deg C, actual +20.0 deg C, water level OK (c. 70%)

      Lights on B2 partially off - Alvaro TD reports this may imply beam tests being carried out. He also
reports spike of gamma counts in BRIKEN clover around 10:00.

10.18 DAQ stops OK
      Current file May2017/R26_17

      Zeroed histograms. Background alpha calibration long run ongoing.

      ASIC settings 2017Mar27-16.12.39 *except*
      slow comparator 0x64
      LEC/MEC fast comparator 0x20

      BNC PB-4 settings 
      Amplitude 90,000
      x5 attenuator IN
      t_r 50ns, tau_d 50us
      polarity -
      rate 250Hz range
      delay MIN, tail pulse

10.25 DAQ stars OK
      Current file may2017/R27

      ttyUSB7 (nnaida1) attached

10.50 Measured AIDA ac mains voltage with DMM. Voltage 100.4V rms L-N
      FL11006 chiller refilled (2 litres added) 

17.05 DAQ continues OK 
      Current file May2017/R26_17

      Detector biases; leakage currents OK - see attachment 6,7
      FEE64 Temperatures OK - see attachment 8
      good events; statistics OK - see attachment 9
      No warnings/errors reported by merger since DAQ GO - see attachment 10

      *all* system wide checks OK *except* ADC calibration of nnaida1, 21 and nnaida1 clock status (=6)

17.07 E17/F11 ambient temperature +24.1 deg C, RH 39.8%, d.p. +9.5 deg C
      Julabo FL11006 set point +20 deg C, actual +20.0 deg C, water level OK (c. 95%)

      Left DAQ running on alpha background calibration run


      
Entry  Wed May 24 13:39:12 2017, Patrick Coleman-Smith, Examination of Console Logs -- and a couple of reminders 

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.

       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.

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.

    Reply  Wed May 24 14:51:06 2017, Patrick Coleman-Smith, Examination of Console Logs -- and a couple of reminders 

 

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? 

       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?

 

       Reply  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

 

 

Entry  Wed May 24 06:33:19 2017, TD, Analysis of RIBF123R1/R23_44, R23_91 & R25_142 R23_44R23_91R25_142R25_12
Álvaro Tolosa Delgado reports observation of c. 1s 'oscillations' in implant-decay time spectra - see below

Hello

The worst cases (oscillations in decay-curve) are:

-->R23_91_115

--> R25_142_149

Other bad cases:

--> R23_44_70

Cheers!

Check sample of data files - see attachments 1-3 - no obvious data structure issues but higher deadtime for
nnaida17 for R23_* files

Control check using file R25_12 - see attachment 4 
Entry  Wed May 24 06:12:48 2017, TD, Lead bricks removed from BRIKEN aperture for source tests - AIDA NOT SHIELDED FROM BEAM 
To install the 252Cf fission source to test the 3He neutron counters, Pb bricks which
had blocked the BRIKEN aperture have now been removed.
Entry  Wed May 24 03:20:35 2017, CB, TD, Wednesday 24 May 8x
11.00 Merger found stopped at 03:27 - current file R24_7
      Restarted Merge. Stopped Run control. Run control stopped, got error message - see attachment 1
      nnaida 1-16 show error, nnaida 17-24 show stopped - see attachment 2
      No new panics in Raspberry Pi console monitor
      
13.10 Found FEE64 #1-16 power off - fuse failed in section #1 of USB-controlled ac mains relay - this fuse was
replaced yesterday

13.15 Closed file May2017/R24
      Closed DAQ, Merger & Tapeserver browsers & terminated terminal servers

13.22 Replaced 250V/16A/fast fuse *and* carrier in section #1 of USB-controlled ac mains relay - when fuse fails
there is some solder leaks from base of fuse into carrier 

13.25 Switch on relays # 1-8 at ~10s intervals
      Count 24 authenticated mount requests 13.26.02 to 13.27.30 - see attachment 5

13.31 E17/F11 ambient temperature +24.4 deg C, RH 40.0%, d.p. +9.9 deg C
      Julabo FL11006 set point +20 deg C, actual +20.0 deg C, water level OK (c. 65%)
      Detector biases & leakage currents OK - see attachments 3 & 4

13.39 Checked Pi-monitor - no further panics detected in FEE64 system logs

13.54 Turned on DAQ.
      FEE temperatures OK - see attach 6
      System wide checks ok *except* nnaida1 clock status (status 6) and nnaida1,7,8,9,13,21,24
      Manually recalibrated all *except* nnaida21

      ASIC settings 2017Mar27-16.12.39 *except*
      slow comparator 0x64
      LEC/MEC fast comparator 0x20

      BNC PB-4 settings 
      Amplitude 90,000
      x5 attenuator IN
      t_r 50ns, tau_d 50us
      polarity -
      rate 250Hz range
      delay MIN, tail pulse

      Current file R26

      ttyUSB0 attached - 7

14.04 good events statistics - see attachment 8
Entry  Tue May 23 03:01:52 2017, CB, TD, NN, OH, Tuesday 23 May 19x
11.02 DAQ continues OK 
      Current file May2017/R22_192

      ASIC settings 2017Mar27-16.12.39 *except*
      slow comparator 0x0a
      LEC/MEC fast comparator 0xff

      Detector biases; leakage currents OK - see attachment 1
      FEE64 Temperatures OK - see attachment 2
      good events; statistics OK - see attachment 3
      No warnings/errors reported by merger since DAQ GO - see attachment 4

      *all* system wide checks OK *except* ADC calibration of nnaida7, 9, 13, 22

11.05 E17/F11 ambient temperature +23.9 deg C, RH 41.3%, d.p. +10.5 deg C
      Julabo FL11006 set point +20 deg C, actual +20.0 deg C, water level OK (c. 75%)
      Voltage on BRIKEN 3He tubes now ON

11.07 DAQ stops OK
      Current file May2017/R22_193
      Deleted R22*

      Loaded new firmware to test ADC calibration clock issues - attachment 6
      Firmware loaded - attachment 7
      Restarted Firefox - temperatures still look fine - see attachment 7
      System wide checks - nnaida1 clock failed, other clocks OK - attachment 8
                           ADC calibration failed for nnaida1, 3, 21 - attachment 9
                           Other system wide checks OK
      Statistics - few SYNC pulses received by nnaida 9 and 12. See attachement 10


      ASIC settings 2017Mar27-16.12.39 *except*
      slow comparator 0x0a
      LEC/MEC fast comparator 0xff

      BNC PB-4 settings 
      Amplitude 90,000
      x5 attenuator IN
      t_r 50ns, tau_d 50us
      polarity -
      rate 250Hz range
      delay MIN, tail pulse

13.10 DAQ started
      File May2017/R23
      Run Control GO - Tape server GO - Merger Unpause - Merger data rate 0, but Tapeserver sees events and
Merger links are green - see attachment 11
      Start ASIC data readout - Merger sees data rate of ~800 000 items/s (OK!)
      FPGA clock monitor page (http://localhost:8015/AIDA/MONLOCK/MONLOCK.tml) screenshot attached (12)

      Ras Pi system console logs for USB0 attached - see attachment 13

18.00 Merger found stopped. We were unable to stop the DAQ. Powered off FEEs. Power on, only eight were supplied
power. 
      Blown fuse in USB bias controller - replaced.
      Power ON the FEEs. All 24 FEEs mounted.
       
      Current file May2017/R23_27 - stopped at 15:27

18.31 nnaida20 rebooted on its own
      
      
18.37 E17/F11 ambient temperature +23.7 deg C, RH 39.8%, d.p. +9.5 deg C
      Julabo FL11006 set point +20 deg C, actual +20.0 deg C, water level OK (c. 70%)

18.41 Restarted DAQ 
      
      Detector biases; leakage currents OK - see attachment 14
      System wide checks - OK *except* several modules failed ADC calibration - see attachment 15
      FPGA clock monitor screenshot attached (16)

18.51 Stopped DAQ. Flashed previous firmware on FEEs (FEE_GF_Feb16_24.bin)
      Power cycled. All 24 modules mounted OK.
      nnaida22 rebooted on its own
      Time out Setting up the DAQ on nnaida2 and others. Power cycled again.
      nnaida17 rebooted on its own.
      Time out Setting up the DAQ on nnaida1. Power cycled again.
      
19.56 DAQ finally started.
      Current run R24

      ASIC settings 2017Mar27-16.12.39 *except*
      slow comparator 0x64
      LEC/MEC fast comparator 0x20

      *all* system wide checks OK *except* some ADC calibrations and clock on nnaida1
      Temperatures OK
      Statistics OK
      
      Logs for nnaida 17,20,22 attached

      
Entry  Mon May 22 10:29:11 2017, TD, FEE64 system console to Raspberry pi /dev/ttyUSB mapping 
ttyUSB0 =>  last host=nnaida24, => last addr=10.1.2.24, ; #panics => 0 ; Not Finished 
ttyUSB1 =>  last host=nnaida23, => last addr=10.1.2.23, ; #panics => 0 ; Not Finished 
ttyUSB10 =>  last host=nnaida18, => last addr=10.1.1.18, ; #panics => 0 ; Not Finished 
ttyUSB11 =>  last host=nnaida17, => last addr=10.1.1.17, ; #panics => 0 ; Not Finished 
ttyUSB12 =>  last host=nnaida4, => last addr=10.1.2.4, ; #panics => 0 ; Not Finished 
ttyUSB13 =>  last host=nnaida3, => last addr=10.1.2.3, ; #panics => 0 ; Not Finished 
ttyUSB14 =>  last host=nnaida12, => last addr=10.1.2.12, ; #panics => 0 ; Not Finished 
ttyUSB15 =>  last host=nnaida11, => last addr=10.1.2.11, ; #panics => 0 ; Not Finished 
ttyUSB16 =>  last host=nnaida20, => last addr=10.1.2.20, ; #panics => 0 ; Not Finished 
ttyUSB17 =>  last host=nnaida19, => last addr=10.1.2.19, ; #panics => 0 ; Not Finished 
ttyUSB18 =>  last host=nnaida6, => last addr=10.1.1.6, ; #panics => 0 ; Not Finished 
ttyUSB19 =>  last host=nnaida5, => last addr=10.1.1.5, ; #panics => 0 ; Not Finished 
ttyUSB2 =>  last host=nnaida16, => last addr=10.1.2.16, ; #panics => 0 ; Not Finished 
ttyUSB20 =>  last host=nnaida14, => last addr=10.1.1.14, ; #panics => 0 ; Not Finished 
ttyUSB21 =>  last host=nnaida13, => last addr=10.1.1.13, ; #panics => 0 ; Not Finished 
ttyUSB22 =>  last host=nnaida22, => last addr=10.1.1.22, ; #panics => 0 ; Not Finished 
ttyUSB23 =>  last host=nnaida21, => last addr=10.1.1.21, ; #panics => 0 ; Not Finished 
ttyUSB3 =>  last host=nnaida15, => last addr=10.1.2.15, ; #panics => 0 ; Not Finished 
ttyUSB4 =>  last host=nnaida8, => last addr=10.1.2.8, ; #panics => 0 ; Not Finished 
ttyUSB5 =>  last host=nnaida7, => last addr=10.1.2.7, ; #panics => 0 ; Not Finished 
ttyUSB6 =>  last host=nnaida2, => last addr=10.1.1.2, ; #panics => 0 ; Not Finished 
ttyUSB7 =>  last host=nnaida1, => last addr=10.1.1.1, ; #panics => 0 ; Not Finished 
ttyUSB8 =>  last host=nnaida10, => last addr=10.1.1.10, ; #panics => 0 ; Not Finished 
ttyUSB9 =>  last host=nnaida9, => last addr=10.1.1.9, ; #panics => 0 ; Not Finished 
Entry  Mon May 22 10:21:29 2017, Patrick, Console mapping to FEE64 please 

Please attach the list of ttyUSB to FEE64 console connection .

 

Entry  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.

Entry  Mon May 22 02:34:51 2017, CB, TD, Monday 22 May 16x
10.35 DAQ continues OK 
      Current file May2017/R19_253

      ASIC settings 2017Mar27-16.12.39 *except*
      slow comparator 0x0a
      LEC/MEC fast comparator 0xff

      Detector biases; leakage currents OK - see attachment 1
      FEE64 Temperatures OK - see attachment 2
      good events; statistics OK - see attachment 3
      No warnings/errors reported by merger since DAQ GO - see attachment 4

      *all* system wide checks OK *except* ADC calibration of nnaida7

10.38 E17/F11 ambient temperature +24.7 deg C, RH 40.7%, d.p. +10.7 deg C
      Julabo FL11006 set point +20 deg C, actual +20.0 deg C, water level OK (c. 75%)

10.39 DAQ stops OK
      Current file May2017/R19_253
      Deleted R19*

      ASIC settings 2017Mar27-16.12.39 *except*
      slow comparator 0x0a
      LEC/MEC fast comparator 0xff

      BNC PB-4 settings 
      Amplitude 90,000
      x5 attenuator IN
      t_r 50ns, tau_d 50us
      polarity -
      rate 250Hz range
      delay MIN, tail pulse

      Check ASIC Control x2
      Zero all spectra

10.47 DAQ starts
      File May2017/R20
      Ras Pi system console logs for USB0 attached - see attachment 5
      Analysed R20_0. All appears to be working fine. Highest dead time ~0.3%  - see attachment 6
      Off-line analysis of R20_0 confirms ADC data and discriminator are synchronised - see attachments 7,8,9

16.55 DAQ continues OK 
      Current file May2017/R20_71

      ASIC settings 2017Mar27-16.12.39 *except*
      slow comparator 0x0a
      LEC/MEC fast comparator 0xff

      Detector biases; leakage currents OK - see attachment 10
      FEE64 Temperatures OK - see attachment 12
      good events; statistics OK - see attachment 13
      No warnings/errors reported by merger since DAQ GO - see attachment 14

      *all* system wide checks OK *except* ADC calibration of nnaida7

17.02 E17/F11 ambient temperature +24.0 deg C, RH 40.3%, d.p. +9.7 deg C
      Julabo FL11006 set point +20 deg C, actual +20.0 deg C, water level OK (c. 75%)

17.03 DAQ stops OK
      Current file May2017/R20_73
      Deleted R20*

      ASIC settings 2017Mar27-16.12.39 *except*
      slow comparator 0x0a
      LEC/MEC fast comparator 0xff

      BNC PB-4 settings 
      Amplitude 90,000
      x5 attenuator IN
      t_r 50ns, tau_d 50us
      polarity -
      rate 250Hz range
      delay MIN, tail pulse

      Check ASIC Control x2
      Zero all spectra

17.08 DAQ starts
      File May2017/R21
      Raspberry Pi system console logs for USB0 attached - see attachment 15

17.50 Changed permissions of options files /MIDAS/DB/EXPERIMENTS/Options/nnaida<n>/CONTENTS 
      from mode 644 to mode 777

18.09 DAQ stops OK
      Current file May2017/R21_11
      Deleted R21*

      ASIC settings 2017Mar27-16.12.39 *except*
      slow comparator 0x0a
      LEC/MEC fast comparator 0xff

      BNC PB-4 settings 
      Amplitude 90,000
      x5 attenuator IN
      t_r 50ns, tau_d 50us
      polarity -
      rate 250Hz range
      delay MIN, tail pulse

      DAQ RESET
      DAQ SETUP

      *all* system wide checks OK *except* nnaida7, 9, 13 and 22 ADC calibration failed

      Check ASIC Control x2

17.08 DAQ starts
      File May2017/R22
      Raspberry Pi system console logs for USB0 attached - see attachment 16
    Reply  Mon May 22 08:43:10 2017, CB, TD, Patrick, Monday 22 May 
> 10.35 DAQ continues OK 
>       Current file May2017/R19_253
> 
>       ASIC settings 2017Mar27-16.12.39 *except*
>       slow comparator 0x0a
>       LEC/MEC fast comparator 0xff
> 
>       Detector biases; leakage currents OK - see attachment 1
>       FEE64 Temperatures OK - see attachment 2
>       good events; statistics OK - see attachment 3
>       No warnings/errors reported by merger since DAQ GO - see attachment 4
> 
>       *all* system wide checks OK *except* ADC calibration of nnaida7
> 
> 10.38 E17/F11 ambient temperature +24.7 deg C, RH 40.7%, d.p. +10.7 deg C
>       Julabo FL11006 set point +20 deg C, actual +20.0 deg C, water level OK (c. 75%)
> 
> 10.39 DAQ stops OK
>       Current file May2017/R19_253
>       Deleted R19*
> 
>       ASIC settings 2017Mar27-16.12.39 *except*
>       slow comparator 0x0a
>       LEC/MEC fast comparator 0xff
> 
>       BNC PB-4 settings 
>       Amplitude 90,000
>       x5 attenuator IN
>       t_r 50ns, tau_d 50us
>       polarity -
>       rate 250Hz range
>       delay MIN, tail pulse
> 
>       Check ASIC Control x2
>       Zero all spectra
> 
> 10.47 DAQ starts
>       File May2017/R20
>       Ras Pi system console logs for USB0 attached - see attachment 5
>       Analysed R20_0. All appears to be working fine. Highest dead time ~0.3%  - see attachment 6
>       Off-line analysis of R20_0 confirms ADC data and discriminator are synchronised - see attachments 7,8,9

Concerning nnaida7 and the failure of calibration..... have you tried to calibrate it using the FADC Align  & Control ?
If it still fails then there is a question about the quality of the clock signal being received by this module.
I will log through and look at the console log for any anomolies but please try and calibrate.
Let me know if you wish me to take remote control.
       Reply  Mon May 22 08:53:42 2017, CB, TD, Patrick, Monday 22 May 
> Concerning nnaida7 and the failure of calibration..... have you tried to calibrate it using the FADC Align  & Control ?
> If it still fails then there is a question about the quality of the clock signal being received by this module.
> I will log through and look at the console log for any anomolies but please try and calibrate.
> Let me know if you wish me to take remote control.

Yes - there have been multiple attempts to re-calibrate nnaida7 ADCs

Note *all* ADCs were calibrated before the most recent FEE64 power cycle.

It is not unusual for ~1-3 FEE64s to fail ADC calibration tests following
a power cycle - there is no obvious pattern to which ADCs fail or which (if
any) will be successfully re-calibrated.
Entry  Mon May 22 08:29:26 2017, TD, Offline analysis R25_12 to R25_22 21x
Offline analysis of AIDA data files R25_12 to R25_22 using MIDASsort

Note

- no calibration (raw ADC data only)
- no thresholds 
- no clustering
- events delimited by > 2us time difference between successive ADC data words 
- HEC = high energy channel = 20GeV FSR range for high energy implants
- LEC = low energy channel = 20MeV FSR range for decays (and pulser)

Attachment 1-4
--------------
s2000-s2005 per DSSSD LEC m_lec_p versus m_lec_n

            following spectra require 0 < m_lec_p < 8 and 0 < m_lec_n < 8
            all combinations of x & y plotted

s2010-s2015 per DSSSD LEC x versus y
s2020-s2025 per DSSSD LEC E_p versus E_n        (20keV/ch nominal)
s2030-s2035 per DSSSD LEC-LEC time              (2.56us/channel)

Attachment 5-8
---------------
s2000-s2005 per DSSSD LEC m_hec_p versus m_hec_n

            following spectra require 0 < m_hec_p < 8 and 0 < m_hec_n < 8
            all combinations of x & y plotted

s2010-s2015 per DSSSD HEC x versus y           
s2020-s2025 per DSSSD HEC E_p versus E_n       (20MeV/channel nominal)
s2030-s2035 per DSSSD HEC-HEC time             (2.56us/channel)

Attachment 9-11
---------------
s2200-s2205 per pixel, per DSSSD HEC-LEC time  (2.56us/channel)

Attachment 12-14
----------------
s2210-s2215 per pixel, per DSSSD HEC-LEC time  (163.840us/channel)

Attachments 15-17
-----------------
s2300-s2305 per DSSSD HEC Energy versus HEC-LEC time (20MeV/channel, 163.840us/channel)
s2400-s2405 per DSSSD LEC Energy versus HEC-LEC time (20keV/channel, 163.840us/channel)
s2500-s2505 per DSSSD x & y strips versus HEC-LEC time (163.840us/channel)

Attachment 18
-------------
Projection s2503 y-strips 0-60 -> HEC-LEC time 163.804us/channel
Entry  Sun May 21 10:58:01 2017, TD, Julabo FL11006 recirculating chiller refilled 15.png
18.55 Julabo FL11006 recirculating chiller refilled to "H" marker of the filling level indicator.

      See http://www2.ph.ed.ac.uk/~td/AIDA/Information/Julabo%20FL11006.pdf
      
      To refill from 60% L-H to 100% L-H required c. 4 litres of water.
      Following refill there is a trickle of water from the overflow connector which is being 
      collected by hose and bucket - this flow should cease when the fluid level falls below
      the overflow level.
      
19.20 FEE64 temperatures OK - see attachment 1
ELOG V3.1.4-unknown