(Updated to 10/01/2020)

If recovering from a crash, turn off the VME crate and the workstation.

1. Turn ON the workstation, and wait for Linux to finish booting. 
Check internet connection to laplan works. If it does not work, open Firefox and log in using UoE credentials.

2. Open a terminal and execute
ping -i 60 8.8.8.8
to prevent the laplan connection from being disabled after a period of inactivity

3. Turn on VME crate. Check lights on CAEN modules are off

4. Start HTTPD service (green right arrow on top bar). Check it is able to find its configuration files, i.e.

Custom startup from /MIDAS/config/TclHttpd/c082002.laplan.net.ed.ac.uk/startup.tcl

works OK. 
If connection to laplan has been lost, the machine name on the network will change and HTTPD will give an error. 
To solve this, cd to /MIDAS/config/TclHttpdf and mv the directory called c0XXXXX.laplan.net.ed.ac.uk to
c0YYYYYY.laplan.net.ed.ac.uk where c0YYYYY is the current name of the workstation on the network
(The name of the workstation is written after npg@ in any terminal)

Check HTTPD ends with 
Completed custom startup from /MIDAS/TclHttpd/Html/CAEN/RunControl/stats.defn.tcl

For more information on messages, see 
http://npg.dl.ac.uk/MIDAS/MIDAS_Release/MIDASNewGen_CAEN_Installation_06Feb18.txt

5. Start EXEC service (blue right arrow on top bar, *not* the down arrow)

Check it ends with

CAEN Data Acquisition now all ready to start
SIGBUS, SIGSEGV and SIGPIPE traps setup

For more information on messages, see 
http://npg.dl.ac.uk/MIDAS/MIDAS_Release/MIDASNewGen_CAEN_Installation_06Feb18.txt

6. Open Firefox and browse to localhost:8015. The page should look like attach 1

7. Press ISOL experiment control, -> Hardware control -> VME Module configuration -> Restore
The page should look like attach 2. If Restore does not work, insert values as per attach 2
Press Activate configuration. You should receive a message saying Activation is successful, and the lights on
the CAEN modules should turn on.

Any other message indicates a communication issue with the CAEN modules. Close Firefox, terminate EXEC and
HTTPD, turn off the VME crate and restart from step 3
Failing that, turn off the workstation as well, and restart from step 1.
The CAEN communication tool in /MIDAS/CAEN/Test can help diagnose the problem. See

http://npg.dl.ac.uk/MIDAS/MIDAS_Release/MIDASNewGen_CAEN_Installation_06Feb18.txt

8. Open VME Save/Restore
Select Data Base Key 1725PosSigWorking and press Restore Settings. You should get a message confirming the restore
was OK.
Dismiss this tab

9. Close the VME Module configuration tab and open Experiment control -> Save/Restore Options
Press Restore options. The configuration should look like attach 3 & 4
Dismiss this tab

10. Select CAEN V1730PSD and press Restore Settings for all Modules. You should get a message confirming the
restore was OK. There are many settings here - some of the most important ones are shown in attach 6.
Select Module Register -> Acquisition Window and set it to 8192
Press Save Settings, Restore settings.

11. Open Experiment Control -> Data Acquisition and Run Control
Press Reset. Wait for the operation to finish.
Press Setup. Wait for the operation to finish.

HTTPD terminal should look like attach 5

Check events per buffer is > 1 AND V1730PSD buffer size used XXXX words out of max 18000, where XXXX < 18000.
Failing either, reduce Acquisition Window.

12. Tick Histogramming On in the Run Control tab. You can now press GO to start without saving to disk.
Check histograms are being generated is received in Histogram Browser and data is being received in Statistics.
Follow 13 on to save to disk.

13. Execute the Tape Server service (blue arrow pointing down in the top bar).
Checks typical output in http://npg.dl.ac.uk/MIDAS/MIDAS_Release/MIDASNewGen_CAEN_Installation_06Feb18.txt

14. Tick Data Transfer On and Data Storage Control Enabled in the Run Control tab.

15. Select Data Storage Control in the Run Control tab. Select a volume name. Data will be saved in
/TapeData/VolumeName
*Do not* use VolumeNames longer than 8 characters.
Press GO in Data Storage Control to open the file. Check the file has been created by ls -lh /TapeData/VolumeName
File size should be zero

16. Press GO in Run Control to start acquiring data. 
Check the data is being written to disk by ls -lh /TapeData/VolumeName - the run should be increasing in size.

17. Stop the DAQ by pressing STOP in TapeService (aka Data Storage Control), and then pressing STOP in Run Control.
The run number should automatically increase in Run Control  (File name R(N+1)). If it does not, increase it
manually in Data Storage Control.
MIDAS will not overwrite runs, and will warn if the run number already exists, but may append new data to an old
run if the run stop procedure is not performed properly.

Analysed first ~500 MB of R2_0 using sorting program

https://elog.ph.ed.ac.uk/EDI_PSA/2

and analysis program

https://elog.ph.ed.ac.uk/EDI_PSA/5

The energy histogram shows three relatively clear peaks, from the triple alpha source - see attached. 
This confirms the DAQ is working properly.

Tested performance of DAQ with following equipment

Hamamatsu photodiode (S3590-09)
    - Powered by Farnell power supply (E30/1). Bias 14V / leakage current < 10uA.
Cooknell preamplifier
    - Powered by Farnell power supply (L30BT) @ 24V.

Self-triggering of the CAEN modules is not yet working. Currently triggering using analogue electronic chain.

Preamp signal is split. One half is sent to Ortec 747 TFA ( coarse gain = 1x / fine gain = 2 / int = 50ns / diff =
500ns / non-inv input) -> Octal CFD CF8000 ( threshold ?? ) -> LeCroy 688AL level adapter (for NIM to TTL
conversion) -> CAEN v1730 external trigger IN
Other half is delayed by 250ns line and sent to CAEN V1730 channel 0

Data saved in DiodeTes/
R1 -> Forgot bias to the diode
R2 -> Bias on. Overnight run
R3 -> Bias on. Short run to commission analysis program

Used and new 23Na targets are in a box in LAB7, next to the other targets

Fit: 3 lines
Free parameters: 2x boundary points between lines
Algorithm: Nelder-Mead, 10 iterations. (Centroid defined incorrectly from entire simplex instead of best two
vertices)

Attach 1 - height (difference between intercepts)
Attach 2 - rise times (x-diff between boundary points). Note peak at tr=100 is spurious.
Attach 3 - alpha signal. Fit from Excel Solver (GRG nonlinear)
Attach 4 - Signal incorrectly identified as H20 tr100 signal. 
Fit displayed is correct, from Excel Solver (GRN nonlinear) tr seems 200 samples instead of 100 reported.
Attach 5 - Slow signal, poorly fitted by fitting functions
Attach 6 - Comparison between signals at H=110
Attach 7 - Heat map

Fit: line + power law + line
Free parameters: 2x boundary points between lines
Algorithm: Nelder-Mead, *20* iterations.

Attach 1: rise times for H>20. Main peak is now double.
Attach 2: heights. Second rise time peak corresponds to four peaks at alpha energies. physical origin unclear.
Overfitting?
Attach 3: comparison between waves of two rise time peaks

Fit: line + power law + line
Free parameters: 2x boundary points between lines
Algorithm: Nelder-Mead, 10 iterations. (centroid correct)

Attach 1 - height (difference between intercepts)

Attach 2-8 - Signals with H~110, different t values (see filenames). 
Note t=370 and t=870 show discontinuities in the middle of the rising front. Pick-up?

Attach 9 - Comparison of the above. Note t=370-570 look visually similar in spite of very different fit results. 
Pulser *not* shown

Attach 10 - Heat map

Attach 11 - rise times (x-diff between boundary points), for H>20 (no noise)

R1: 
Same as previous configuration? 
Negative signals.
No pulser
2048 window / 1000 pre-gate trigger
20 threshold / 44098 DC offset
3-alpha source

R2: 
Detector rotated. 
Negative signals
No pulser
2048 window / 1000 pre-gate trigger
20 threshold / 44098 DC offset
3-alpha source




R3: 
Detector rotated back. 
Positive signals.
2.5 Hz Pulser
1024 window / 700? pre-gate trigger
50 threshold / 48098 DC offset
3-alpha source


R4: 
Detector as before
Positive signals.
2.5 Hz Pulser
512 window / 600 pre-gate trigger
50 threshold / 48098 DC offset
3-alpha source

R5: 
Detector as before
Positive signals.
2.5 Hz Pulser
1024 window / 650 pre-gate trigger
50 threshold / 48098 DC offset
3-alpha source

R6:
As above. No alpha source.
Data acquisition stopped very early into the run. Lost contact with digitiser?


Upon re-establishing contact, signal digitisation looks extremely coarse in y.
Previously observed behaviour. Reasons unclear.
Calibrate ADC on V1730PSD panel seems to have fixed this. 
However, baseline/offset/threshold clearly changed based on data rate and signal.
Lowered threshold.

R7: 
Detector as before
Positive signals.
2.5 Hz Pulser
1024 window / 650 pre-gate trigger
40 threshold / 48098 DC offset
No source.
Data acquisition stopped very early into the run. Lost contact with digitiser again?

Did not reboot either PC or VME crate. Rebooted MIDAS only. Re-established contact. All looks good

R8:
As R7
Data acquisition stopped a few hours into the run. Same as before!

Did not reboot either PC or VME crate. Rebooted MIDAS only. Re-established contact. All looks good

R9:
As R7,R8
DAQ stopped again. Rebooted. OK. Issue needs to be understood.

R10
As above
DAQ did *not* crash!

R11
As above.

R12
As above, 208Bi source placed in chamber.
No obvious signal. Run stopped

R13
Pulser settings changed during optimisation.
Source location changed during optimisation.

---

Attempted to increase DC offset (->55098) and lower baseline (2400) to increase gain and make use of full
dynamic range.
Systems briefly triggers, contact with VME lost. Will need to reboot locally.

Using a 1x1 Hamamatsu photodiode (uncoated)
+75V bias supplied via RAL108 and standard photodiode mount. Imon ~0 
Note negative bias would be supplied with standard lemo cable + standard mount. 
Positive bias supplied via modified lemo cable to read *positive* pulses after RAL108 preamp

->CHANGED dynamic range to 0.5 Vpp (from 2 Vpp)

R14
Positive signals
2.5 Hz Pulser
1024 window / 600 pre-gate trigger
70 threshold / 2300 baseline
55098 DC offset
208Bi source


DAQ stopped acquiring for unknown reasons at 22:30.
Enough data to analyse.

Swapped Bi source for 3-alpha. Had to move diode around.
Pick-up / microphonic noise much worse now. Baseline too unstable to trigger.
Giving bias results in 1 uA / 25 V current (vs. ~0 before).
No alphas can be seen.
Further investigation needed.

After plugging/uplugging wire from diode leakage current no longer grows to 1 uA / 25 V when giving bias.
Behaviour appears inconsistent. Heat shrink applied to makeshift connector to improve situation. Now running
without leakage current at 75 V.

Note 208Bi source was found to be leaky and removed.

R15
Positive signals
2.5 Hz Pulser
1024 window / 650 pre-gate trigger
70 threshold / 2300 baseline
55098 DC offset
3-alpha source

Runs acquired in Jan-Feb 2020

Detector bias -50V
Bias applied to one strip only of B-grade silicon W1
Triple alpha source P9
500 samples pre-trigger
8096 total samples

- Internal triggering from CAEN v1730B digitiser
R1,2,3 - Cooknell preamps, positive waveforms
R4 - Skipped
R5,6 - RAL108 preamps, positive waveforms

- External trigger provided from Ortec TFA + CFD + Lecroy Level Adaptor
- 500 sample pre-trigger, but note trigger position in time now resents of dealay between signal and TFA+CFD trigger chain
R7,8 - RAL108 preamp, negative waveforms

- CFD threshold potentiometer cleaned. Threshold likely changed
- Reduced samples to 4096
R9 - RAL108 preamp, negative waveforms

- TFA failed & replaced. New gain settings Fine MAX (12.5x), Coarse 2x
- Samples stil at 4096
- Pre trigger window increased to 1000
R10 - RAL108 preamp, negative waveforms
R11 - RAL108 preamp, negative waveforms with Cs-137 gamma source
R12 - RAL108 preamp, negative waveforms at -25V bias
R13 - RAL108 preamp, negative waveforms at -75V bias  
R14 - RAL108 preamp, negative waveforms with neutron source
R15 - RAL108 preamp, negative waveforms, background run