On 15/06/2023 morning, around 6:32 am, a powercut caused failure in the Compresed Air Pressure system. Faraday cup was closed by the interlock and the HV was turned off.

We turned off the accelerator, dismounted LNL9 (pictures attached) and mounted Ta1 Edi backing. We left only ACP28 pump on. We also switched off GeBo HV and its cryocooler.

All details can be found in the excel sheet attached to entry 24.

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

On 13/06/2023 afternoon we dismounted LNL6 sputtered target and mounted LNL2 (identical to LNL1, one Cr layer). We performed a scan of E_res=309 keV and left overnight under beam. In the morning 14/06/2023 we repeated the scan: the plateau has increased by 50% in height, but was much shorter. After dismounting, we notice witish dots around the beam spot.

We then mounted LNL9 (sputtered) and performed a scan. Very short plateau. We left for a long run.

Pictures of the targets attached (LNL6 after- LNL2 before and after - LNL9 before).

On 12/06/2023 we dismounted LNL4 after approximately 12 C were deposited.

We then mounted LNL6 (sputtered, in-air target). After a scan of 309 keV resonance, we left the target on for an overnight run. In the morning of 13/06/2023, the plateau was at the same level as the day before. We did another scan and left the target for few more hours under beam.

Pictures of targets attached (LNL4 after beam, LNL6 before beam) .

When opening LNL4 target jar, the valve did not sound as if air was entering it: we suspect the target was actually not properly under vacuum.

We mounted LNL4 target. However, we could not start the measurement because of bad vacuum. Cold trap was warm. We did several N2 washings to get rid of any residual humidity in the beam line.

We had to dismount the target and do several tests with the leak finder before finding out that the problem was a broken O-ring between target and target holder AND damaged chiller's tube valve on target holder.

As a consequence, the target was exposed to air for quite some time. No visible degradation. Some pictures are attached.

We finally started the scan: details in the excel sheet. Target seems to have withstood air humidity!

We performed the scan on the LNL1 23Na target (details in the excel sheets in previous entry) for the E_p=309 keV resonance. The target has a sharp well defined rising edge, but it quickly deteriorates under beam bombardement (already after 0.1 C we can see the plateau height at same energy decrease). The thickness of the target also appears much larger than what recorded in the target info.

During the night between 8th and 9th June, we left a long run. In the morning we found the Faraday Cup closed and a pressure of a few mbar in the target chamber. We noticed one of the tubes of the chiller was open on the ground. This caused the chiller to stop working around 9pm. The target started to heat up and the tantalum was bent towards the chamber.

We did not find water in the chamber, it was probably spread on the ground before the chiller stopped working. Possibly a microscopic fracture was formed in the backing, causing air to flow inside the chamber and worsening the vacuum. The turbopump was however still on and does not seem damaged.

Pictures of the target before and after beam bombardment are attached.

We have started the pumping system and reached ~10^-6 mbar vacuum. We have then filled the cold trap reaching ~10^-7 mbar.

We have started the chiller and the measurement on the Ta backing on 7/6/23. We made a quick run on top of the 19F(p,gamma) resonance at e_p=340 keV, and an overnight run on top of the 11B(p,gamma) resonance at E_p=163 keV.

On 08/06/23 we focused the beam at E_p=309 keV (23Na(p,gamma) resonance) and left a run on the Ta overlunch.

More details in the attached Excel sheet.

Attached a picture of the germanium baseline in the morning 6/6/23.

-----------------------

We change the pulser amplitude to have it in the spectrum at what seemed a good position (A=150 mV).

We put 133Ba, 60Co and 137Cs sources in the shielding and started run_2 at Mon 6 June 2023, 12:15.

The run was stopped at 16:01. (Note there will be two ROOT files in the folder: one (2_1 for DataR_run_xx.root) is the automatic backup at 15:01, when the 'tentative' calibration on CeBr90 was enabled).

GeBo FWHM at 1.33 MeV is quite bad: 6.4 keV.

-------------------------------

We searched again in 16O log for optimal DAQ parameters and found them. We thave hen used them to see any possible resolution improvement. Spectrum is saved as run_3.

CeBr90 FWHM at 1.33 MeV is 46.10 keV.

GeBo FWHM at 1.33 MeV is 5.37 keV------------>with same parameters, 16O elog reports 3.42058 keV (Feb2023): note that Ge baseline thickness now is approximately 5mV, while in 16O elog I have found 2mV as reference, or slightly more from picture attached to same entry 110 Nov22).

Note that lowering the threshold at the 'optimal' values, we are cutting Ge spectrum at roughly 300 keV (which should not be a problem for 23Na+p resonance scan).

-----------------------------

We have mounted the Tantalum backing from Edinburgh (last spare, cleaned on 20/03/23 at LNGS) on the target holder and closed the beam line. We have left run_4 overnight as background run.

------------

Ge cryocooler is at 80K and 92 W.

We started the acquisition via CoMPASS with one CeBr (90)  and the HPGe. The germanium was already cooled at 80K with a power of 90W. The CeBr HV was already applied from NHQ 202M bias supply, channel A, HV = +650V.

We applied the HV to the germanium on 5/6/23, from Ortec 660 dual bias supply borrowed from gas target, channel B, HV = +4900V, Bias shutdown connected.

Attached a picture of the baseline in the evening, before leaving the lab.

-----------------------

The DAQ from solid target is connected to the new Intel NUC mini-PC, located below the VME crate. It is possible to connect remotely to such PC using the RDP protocol (IP address -> 172.17.5.149). To connect from lunaserver, lauch Remmina and select lap2-depalo. Here, the CoMPASS project is located in /home/Compass/projects/23Na_target_tests.

We have also created the folder on lunaserver in /home/luna/Shared/Data/23Na_target_tests, where we copied from /home/luna/Shared/Data/16O_prompt the scripts required for possible binary conversions.

We are using three channels for the acquisition:

• Ch. 1: scintillator CeBr 90
• Ch. 2 : GeBo + pulser
• Ch. 3: Pulser

Pulser module BNC Model 9010 with following parameters:

• Amplitude 50 mV
• Frequency 24 Hz
• Delay 1 us
• Width 1 us
• Rise Time 0.05 us
• Fall Time 5 us
• Polarity: positive
• No attenuation

We left an overnight background run (run_1).

Given very poor fit using line + power law + line, changes were made to the fitting algorithm.
- Starting paramters optimised for new typical wave shape
- Reverted to 3 lines, since signals are faster
- Subtracted wave minimum from all wave points to have a more realistic chi2 estimate
- Discarded all waves where 2nd half of signal > 1st half of signal. Should correspond to pick-up / noise

Fit: 3 lines
Free parameters: 2x boundary points between lines
Algorithm: Nelder-Mead, 20 iterations.

Attach 1: Wave amplitudes
Attach 2: Rise times
No major differences vs. power law method, but note candidate electron peak in rise time spectrum is now sharper.

Attach 3-9: Waveforms with H~90 and increasing rise times. 
Note fit shown are via Solver's GRG, not NM.
Fits in waves 1-4 give same result for GRG and NM.

Fit in wave 5: NM-> H72 t102 vs. GRG-> H80 t25
Fit in wave 6: NM-> H96 t128  vs. GRG-> H90 t23 
GRG risetimes are more realistic. This appears to be due to very short baseline pre-rise.
Will increase in next run.

Fit in wave 7 is rare pile-up event. Code cannot yet cope. Bad fit.

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

Attach 1: Wave amplitudes. 
Pulse not shown at 1000 channels.
Obvious signal from Bismuth source with visible peaks. Not all peak origins clear.

Attach 2: Risetimes.
Pick-up / microphonic noise quite evident (compare with background run with B-grade silicon)
Pulser relatively well-defined in risetimes
Electrons not well defined

Attach 3: Waveform for electron candidate fitted as risetime = 26 samples
Attach 4: Waveform for electron candidate fitted as risetime = 153 samples

Visual difference between the two unclear, aside from noise.
Looks like fitting function is failing. Will have to change algorithm to draw any conclusions.

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

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

Attach 1: Wave amplitudes. 
Peak at 300 is pulser.
Some physics events in between obvious noise and pulser.
No obvious signal from Bismuth source

Attach 2: Alpha (?) wave sample. Rise time ~ 200 samples.
In spite of no signal from source, some alphas are visible.

Pulser frequency: 2.165 Hz (462 ms)

Attach 1: Pulser events vs. total events

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

Attach 1: Rise times. 
Peak below 200 is pulser.
200 samples should correspond to alphas, according to R3 analysis. 600+ should correspond to slow signals
(electrons?)

Attach 2: Wave amplitudes (pulser not shown).
150-200 channels should be correspond very roughly to 5-6 MeV

Attach 3: An alpha candidate signal. H 163 t 198
Attach 4: A slow physics signal (electron?) candidate. H 100 t 651

Attach 5: Noise with low Chi2. Reported as H2 t 406. Note fit is GRG nonlinear - cannot reproduce dataReader
Nelder-Mead Simplex fit in Excel (working on it).
Attach 6: Noise with high Chi2 value. Reported as H40 t150. As above.

Attach 7: 2D heatmap

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)

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

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.

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

According to Carl U. the DPP-PSA software is not meant to be used with negative pulses, and some of the
functions that are currently not working may be recovered fixing this issue.

Changed Pulse Polarity in V1730PSD control panel Positive -> Negative 
No changes. Note trigger is currently supplied by external CFD
QLong histograms are still not counting

Set DC offset to 64000. The negative part of the pulse is cut off. Wave histogram shows nothing below zero.
Inversion doe snot appear to be working.


Changed BNC-4 Pulser polarity Negative -> Positive and changed polarity of time signal going to CFD. CFD
triggers OK.
No changes. QLong histograms not counting.

Enabled self-triggering on Ch0 and removed CFD input. DAQ no longer triggers. Put CFD back in.

Changed DC offset of Ch0 to 64010 to remove DC offset. Pulse now looks as attach 1.
Disconnected CFD output -> DAQ does not trigger. Reconnected CFD.
QLong histograms still not counting.

Attempted to change options in V1730PSD control panel one by one to see difference
Enabled Charge Pedestal -> No difference. Disabled
Changed Charge Sensitivity 5 fC -> 5.12 pC. No difference. Back to 5 fC
Changed Discrimination Mode CFD -> LED & removed CFD input. No triggers. Reverted

Changed Baseline Mean 16 -> 1024. Wave changes as per attach 1. QLong histogram starts counting at low channel.
See attach 2.
Changed DC offset 64010 -> 60000. Peak in QLong histogram moves to ~1050 channels. See attach 2.
Changed DC offset back to 64010.
Changed Baseline Mean 1024 -> 64. No changes in either wave shape or QLong peak position.
Changed Baseline Mean 64 -> 256. No changes as above.
Changed Baseline Mean 256->16. Wave is back as per attach 1, QLong no longer counting.

Found VME crate yesterday reporting AC power failure. Workstation unresponsive.

Power cycled everything and restarted -> all OK.

Long-term stability of the setup appears to be still poor.

Left DAQ running with pulser signal to attempt to reproduce error leading loss of communication with VME crate.
Write to disk DISABLED.

Tried using settings attached to enable internal CFD.
Restored / DAQ Go. No waveforms.
MIDAS lost connection with the VME crate. Stopped DAQ. Workstation froze few seconds later.
Rebooted, restored settings CarlTest150519 - all OK

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.

Wrote simple program to convert from waves to amplitude/energy histogram.
Program uses semi-gaussian filtering with RC=RC, simple pole zero correction and baseline restoration.

Compile with g++ WavesToHisto.cpp -o WavesToHisto.x
Usage: ./WavesToHisto.x Sorted_run_file > histogram.dat

P9 3-alpha source
Hamamatsu Photodiode - bias = 15V
Cooknell preamplifier
Analogue triggering chain

2048 total samples
256 samples pre-trigger window

Start 11:50 am
Lost contact with VME modules at ~ 18:00 - no more data written to file

Attempted to stop DAQ - failed.
Had to power cycle VME crate to restore contact. 

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

Sort program written by Oscar, adapted from the RIKEN AIDA sort.
EDIT 26 Jun 2019 by CB - C++11 dependencies removed for SL6 compatibility
EDIT 28 Jun 2019 by CB - added histogram program mode

1. Untar/unzip
2. Compile with  g++ dataReaderMain.cpp -o dataReader
3. Usage       ./dataReader MODE pathToFile/File

where MODE is wave to output the waveforms, and histo to output a basic wave amplitude histogram with
semi-gaussian filtering applied on the waves
The output will be printed on standard output. 
Use ./dataReader MODE path/ToFile/File > pathToOutput/Output.dat
to save to file.

In wave mode the first few lines are the header. Waveforms are printed bin-by-bin with a newline after every
bin. A blank
line is placed between waveforms.

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