Measured IV curve for BB18 DSSD with new CAEN HV supply. Settings as in previous elog entry:

Detector bias CAEN N1419 Programmable HV Power Supply
  - FAGND isolated from AGND (AGND = NIM chassis ground)
  - floating HV supply, <5mV pp noise specification
  - configured + polarity, i.e. core to nnaida11 & nnaida12 MSL type BB18 n+n ohmic strips
                                braid to nnaida12 & nnaida13 MSL type BB18 p+n junction strips



Data (see attachment):
V [V]	I [uA]
3	1.34
6	1.62
9	1.81
12	1.97
15	2.1
18	2.21
21	2.31
24	2.39
27	2.46
30	2.52
35	2.61
40	2.68
45	2.73
50	2.77
55	2.8
60	2.82
70	2.86
80	2.91
90	2.94
100	2.97
110	3
120	3.06
130	3.12
140	3.18
150	3.26
160	3.34
170	3.43
180	3.53
190	3.62

Jan 22, 2015

R61: 207Bi source spectra accumulated during one afternoon. Same settings as in R49 (alpha background run, 
elog entry 23) 

  + pulser: 0.5V, split and one of the signals inverted, and f=100 Hz.
  + threshold for slow comparators:
	- Eth(nnaida11)= 0x16
	- Eth(nnaida12)= 0x20
	- Eth(nnaida13)= 0x40
	- Eth(nnaida14)= 0x16

R62-R65: short runs with different amplitude for pulser (source still in):

 + R62: pulser @ 0.75 V
 + R63: pulser @ 1.00 V
 + R64: pulser @ 0.30 V
 + R65: pulser @ 0.18 V

R61 provides another point @ 0.5. V.


Raw data files saved in external drive (/media/data/TapeData/Test100/), and in UoEdinburgh disk space 
(/Disk/ds-sopa-personal/aestrade/data/AIDA/):

-rw------- 1 aestrade root 1177685085 Jan 21 16:55 R61_0.gz
-rw------- 1 aestrade root 1175087265 Jan 21 16:57 R61_1.gz
-rw------- 1 aestrade root 1176655505 Jan 21 17:00 R61_2.gz
-rw------- 1 aestrade root 1173848081 Jan 21 17:02 R61_3.gz
-rw------- 1 aestrade root 1180888194 Jan 21 17:05 R61_4.gz
-rw------- 1 aestrade root  168022642 Jan 21 17:05 R61_5.gz
-rw------- 1 aestrade root   77074827 Jan 22 13:12 R62_0.gz
-rw------- 1 aestrade root   45584289 Jan 22 13:12 R63_0.gz
-rw------- 1 aestrade root   42043231 Jan 22 13:12 R64_0.gz
-rw------- 1 aestrade root   41005241 Jan 22 13:12 R65_0.gz

A first look at the data from the 207Bi source (run described in previous elog entry, ID 27)

The main conclusions are (see description of spectra further bellow):

- NNAIDA11 and NNAIDA13 were running stable, even though NNAIDA11 had one channel with very high rate. 
NNAIDA12 and 14 were running unstably with frequent instances of Pause/Resume. A possible explanation is 
their higher data rates (due to a bad channel and noise, respectively).

- I think using only a window in time will not be sufficient to identify electron signals in the data. 
This is a particular issue for the data of NNAIDA14, where there is a high noise and a energy threshold, 
or some more ingenious condition, is likely required.


Plots were generated with the script in /Home/aestrade/AIDA/analysis/loopAIDAsort.cpp

Only a fraction of the 207Bi data was processed (corresponding to file R62_2). 


+ Distribution of time-stamps

R61part_ts_dist_adc_hit.png: The spectra show the difference between the 
time-stamp of a given ADC hit (ts_i) and the time-stamp of subsequent ADC 
hits (ts_i+n):

	Delta ts(i+n,i) = ts_(i+n) - ts(i)

So the first plot, for Delta ts(i+1,i), is the difference between each ADC 
hit and the next ADC hit. The second plot is the ts difference between each 
ADC hit and the second to next ADC hit, and so on... 

The data mixes the spectra for all FEE cards and all ADC channels. One can 
still see a clear structure with a peak at low values of Delta ts, and then 
a second distribution up to Delta ts= 30*n usec. These is the time it takes 
to loop through all 16 channels of the ADC (2 usec/channel), so is likely 
the distribution generated by one channel is firing at a very high rate.

I'll make similar plots with conditions to mask out noisy channels and/or 
pulser events to look for a value of the coincidence time-window to use to 
reconstruct events.

+ Rates

R61part_rates.png: the spectra shows various rates (in Hz) as a function of 
run time and of channel. The plots on the top are the rate of ADC hits (for 
low energy range) of each FEE module, and one showing the rate of ADC hits 
for the high energy range in all modules combined. The bottom row shows rate 
per channel, and the rate of Information type hits.

some conclusions: NNAIDA11 and 13 show a flat rate, and as will be seen from other plots are very stable 
during the run. NNAIDA11 has a larger rate than 13, but the difference is mostly due to a very high-rate 
channel; the rate in most channels is consistent with a 100 Hz pulser for both.

NNAIDA12 and 14 show the largest rate that can peak at 35kHz, and looks quite unstable. These modules also 
have a choppy run of the DAQ (many Pause/Resume). NNAIDA11 actually has similar rate to NNAIDA12 and 14, 
but is still stable.

Both NNAIDA11 and 12 have one channel wiht very high rate compared to the 
rest (rather than unusually noisy channel, could it be one that is always 
above the threshold of the slow discriminator?).


+ ADC Rate with fine granularity

R61part_t1_hits_ts_adc.png: These spectra show the ADC hits (low range) vs time but with a higher binning 
of the data (1 ms/bin). The one channel with a very high rate in NNAIDA11 and 12 is seen in red. Also that 
the data readout from NNAIDA12 and 14 is frequently halted by Pause/Resume signals. 

R61part_t1_hits_ts_adc_zoom.png: The second file hast the same spectra but zoomed in a narrow time window, 
and one can see the hits from the pulser 10 ms appart (as vertial lines with hits in all channels for 2D 
spectra). In between the pulser signals, as hits in individual channels, are hits from the source or from 
noise. For NNAIDA14 this white noise was very high, so at the binning of 1ms/bin this spectra there are 
many channels with hits in each time bin. I think it will be difficult to identify electron events from 
such spectra using only a time window as requirement for coincidence. 


+ Info Codes Rates

R61part_t1_hits_ts_info.png : The spectra show the rates of information words. The first plots are again 
for a narrow section of the run (same as previous spectra). One can see the frequent sequence of 
Pause/Resume for NNAIDA12 and 14. Also note discriminator data and ADC(high range) hits only come for 
NNAIDA12 (we used very high value for discriminator threshold).

R61part_ts_info_fee.png: The figure shows the distribution of the different information codes for each FEE 
module, but now for the full lenght of the run.



++ Sorted Root TTree fiels ++

All raw files of run R61 were processed with the 'beta' version of the Root 
sort code for event reconstruction (/homes/npg/AIDAsort/ in DL PC), but only 
up to the 'Calibration' step (no event reconstructino). 
R61_207Bi_2_sort.root used for above plots. 

Root tree saved here:

/Disk/ds-sopa-personal/aestrade/rootfiles/AIDA/R61_207Bi_0_calib.root
/Disk/ds-sopa-personal/aestrade/rootfiles/AIDA/R61_207Bi_0_sort.root
/Disk/ds-sopa-personal/aestrade/rootfiles/AIDA/R61_207Bi_1_calib.root
/Disk/ds-sopa-personal/aestrade/rootfiles/AIDA/R61_207Bi_1_sort.root
/Disk/ds-sopa-personal/aestrade/rootfiles/AIDA/R61_207Bi_2_calib.root
/Disk/ds-sopa-personal/aestrade/rootfiles/AIDA/R61_207Bi_2_sort.root
/Disk/ds-sopa-personal/aestrade/rootfiles/AIDA/R61_207Bi_3_calib.root
/Disk/ds-sopa-personal/aestrade/rootfiles/AIDA/R61_207Bi_3_sort.root
/Disk/ds-sopa-personal/aestrade/rootfiles/AIDA/R61_207Bi_4_calib.root
/Disk/ds-sopa-personal/aestrade/rootfiles/AIDA/R61_207Bi_4_sort.root
/Disk/ds-sopa-personal/aestrade/rootfiles/AIDA/R61_207Bi_5_calib.root
/Disk/ds-sopa-personal/aestrade/rootfiles/AIDA/R61_207Bi_5_sort.root


A bug on the Root sort code was identified from this output: the code waits 
for a SYNC100 pulse from *each* FEE card to update their corresponding 
most-significant bits (MSB) for the timestamp, while one has to use *any* 
SYNC100 pulse to update the MSB of all FEE modules. As a consecuence, a 
(very small) fraction of the processed hits have the wrong time-stamp (off 
by bit 28).

We want to reduce the configuration of the setup to 4 FEE cards (8 NNAIDA modules), so we only have to isolate 4 of them from the cooling crate for a noise test. Following instructions in April2015 test logbook.

Copied directory /MIDAS@aidas to /MIDAS@aidas.121215

In /MIDAS@aidas/config/TclHttpd/aidas1@8015 edit file:
-rw-rw-r--. 1 npg npgstaff 2281 May  3  2015 startup.tcl

Now scripts does 'lappend ACQSERVERS nnaida$i' from i=1 to 8

Set discriminator mask for DSSD2 through DSSD6 (see attachments). Fast comparator threshold set to 9 for all DSSDs.

New source run for beta-gamma correlation, now with all DSSDs included in EURICA trigger.

Trigger is OR of coincidence front:back of all DSSDs.

AIDA run: R17*
EURICA run: BiCocal_run0015.lmd

Saved new ASIC settings: 2016May31-23.32.46

Experiment elog: http://ribf-exp.riken.jp/elog/EURICA+U-campaign+2016/13

Here is the mapping of the trigger output of MAC-B modules to FEE64 modules

3.1   NNAIDA5   veto-X2
3.2   NNAIDA14  D4-X2
3.3   NNAIDA13  D5-X2
3.4   NNAIDA6   D6-X2

4.1   NNAIDA28   -
4.2   NNAIDA27  D1-Y1
4.3   NNAIDA20  D2-Y1
4.4   NNAIDA19  D3-Y1

5.1   NNAIDA12  D4-Y1
5.2   NNAIDA11  D5-Y1
5.3   NNAIDA3   veto-Y1
5.4   NNAIDA4   D6-Y1

6.1   NNAIDA25  D1-X1
6.2   NNAIDA17  D3-X1
6.3   NNAIDA18  D2-X1
6.4   NNAIDA26   -

8.1   NNAIDA29   -
8.2   NNAIDA30  D1-X2
8.3   NNAIDA22  D2-X2
8.4   NNAIDA21  D3-X2

9.1   NNAIDA15  D4-Y2
9.2   NNAIDA16  D5-Y2
9.3   NNAIDA7   D6-Y2
9.4   NNAIDA8   veto-Y2

10.1   NNAIDA1   veto-X1
10.2   NNAIDA9   D5-X1
10.3   NNAIDA10  D4-X1
10.4   NNAIDA2   D6-X1

11.1   NNAIDA23  D2-Y2
11.2   NNAIDA32  D1-Y2
11.3   NNAIDA31   -
11.4   NNAIDA24  D3-Y2


MACB modules are labeled, from left to right, according to their position in the NIM crate.

D1 is the most upstream DSSD, and veto the most downstream one.

Please find attached the best diagram of the beta trigger logic circuit for EURICA campaign 2016

*2:30 pm*: changed power source of USB-controlled power supply for FEEs. Now one of the power cables is connected
to the 'B' power supply of F11, and the second to the 'C' power supply (these are in the unit on top of WASBI
crates). The reason for change is that before both were connected to 'C', and drained current was very close to
limit  of 10 A (and power cord getting noticeable hot). We'll check resolution after this switch.

Detectors 1, 2, 3, and 4 biased to 100V, detectors 5, 6, and veto biased to 70V.

n-side is more noisy than p-side, but resolution comparable to previous configuration:

NNAIDA#   FWHM [ch]
    1     91
    2     61
    3     84
    4     -
    5    160
    6     -
    7     79
    8     84
    9     71
   10     76
   11    101
   12     81
   13     69
   14     78
   15    199
   16    107
   17     82
   18     62
   19     -
   20     89
   21    168
   22     70
   23     80
   24     73
   25     81
   26     13
   27    109
   28     13
   29     15
   30    126
   31     13
   32    100



*5 pm*: Set-up correlation scalers for AIDA<->EURICA<->BigRIPS (detail diagram coming soon, now only in paper
logbook). 


*6:30 pm*: Started EURICA DAQ with Pieter and Gabor.

A folder is created to record data of June campaign: /raid/11/mbs/2016_ucampaign/

Tested correlation of AIDA and EURICA with a pulser run, triggering EURICA and AIDA correlation scaler with 250
Hz. The corresponding files are

/raid/11/mbs/2016_ucampaign/test0003.lmd
/TapeData/may2016/R12_0.gz

Phong did a quick analysis and the pattern of correlation scalers in both files is similar (attached figures). It
is also consistent with the number of reset requests we sent during the data taking (three requests closely spaced
in the middle of run, and two more in the end of the run).

Continued work on beta-trigger for EURICA. However the system seems to have different noise condition than before, which 
we think appeared after we changed power source for FEE's PSU (https://elog.ph.ed.ac.uk/AIDA/220). This is high frequency 
noise of low amplitude, with a period of 10 usec.

The effect on the resolution measured with the pulser is not too large - thus our conclusion in elog entry 220 that noise 
conditions had not changed much - but the noise does create a large trigger rate that would not allow us to set a low 
trigger threshold (for MAC-B outputs from fast discriminators). The rate of singles from front or back, as well as coincidence of 
front-back strips, increased by more than a factor of ten compared to previous conditions (e.g. ~200 coincidences for one ASIC 
enables in each side of DSSD1, and fast threshold of 10).

Saved some data in this conditions, with a threshold of 16 for the fast discriminators (enabled in one ASIC for 8 of the 
FEEs). When fast discriminator lowering threshold to 9, the system got upset and lost synchronization. Tomorrow we'll 
attempt to revert to previous configuration of PSUs.

R16*gz:

DSSD HV: +100 for all.
Leakage current (uA): 4.2, 4.9, 3.7, 3.9, 4.2, 3.8, 10.7 (from Det#1 to veto)

Enabled fast discriminators in ASIC2 of DSSD1 and DSSD5 (NNAIDA#: 25, 30, 27, 32, 9, 13, 11, 16)

DSSD#1 is next to 207Bi source

The program for online monitoring the correlation of the DAQ systems (AIDA-EURICA-BigRIPS) through a common scaler is SyncCheck (J. 
Agramunt). 

The code runs in the d05 server, receiving data transferred to a DataSink from each of the individual DAQs. The data transfer is 
done with the DataRelayFilter code for AIDA (AE), and the euricatssender and ribftssender (Baba-san) codes for EURICA and RIBFdaq, 
respectively.  

The attached screenshots show how to setup these programs. Follow these steps:

1) Log in to d05 as user 'aida'. Start an instance of the DataSink code with option -i 3 (3 data stream, which will use ports 10305 
to 10307). The code is saved in /home/aida/DataPackage/DataSink/Linux64

2) In the d05 server start the following codes: euricatssender (in /home/aida/ribfts/euricatssender/ directory), and ribftssender 
(in /home/aida/ribfts/ribftssender/ directory). If you give the codes dummy command line option (e.g. -X) the value of transferred 
timestamps will be printed to screen as diagnostics.

3) In the AIDA computer (aidas1), start the DataRelayFilter program (will work from any directory). As command line arguments 
provide the IP address of d05, and the TCP port and id of the data stream for the DataSink program: DataRelayFilter -n 10.32.0.12 -
p 10307 -I 2

Only the master FEE will produce correlation scalar items (?). The code has as default NNAIDA5 for the module where to search for the Corr Scaler
items; if this has to be changed use command line option -m X (where X is NNAIDAX number for new master FEE)

4) Back in the d05 server start the SyncCheck program, in the directory /home/aida/SyncCheck/. You can give as an argument the ID 
of the Master data stream for the synchronization check, through "-M ID" (should be done if one of the three data streams is down). 
For example "SynCheck -M 2" will use AIDA as the master timestamp.

5) Perform a manual correlation reset request to synchronize the value of the correlation scaler in all three DAQs. This is done with the 
button 'Force Correlation Reset' of the AIDA "Correlation Status & Control" webpage (attachment 2), which can be accessed from the MIDAS web-
based control of AIDA.

The SyncCheck code will display a few spectra for onine monitoring of DAQ correlation (attachment 3, shown only with AIDA and EURICA running). 
A peak will appear showing the offset in the correlation scaler between the different DAQs. The counts in the peak should increase 
continuously, and its position should not change. If it doesn't, try sending a Correlation Reset signal (step 5). If this does not fix the 
monitor, report a correlation error! 

Further information on the scheme for data synchronization is here: 
https://elog.ph.ed.ac.uk/BRIKEN/6
https://elog.ph.ed.ac.uk/BRIKEN/5

file AIDA10_20: stopped on June 10, 14:59
file AIDA10_40: stopped on June 10, 16:16

Time different between pulser peaks, in microseconds (ts/100), for the four groups shown in the attached plots:

AIDA10_20: 2593, 2628, 2593
AIDA10_40: 2618, 2600, 2618

Measurement consistent with a time difference of 2600 usec (there is an error of 32 usec as we're using the data
from the slow comparator)

The two runs also show the same pattern of which FEEs have the same timestamp for the pulser event


Attachment 3, for run AIDA34, corresponds to a case after we had managed to resynchronize all FEEs

R9_24 3mm Pb + 0.3mm W (+1mm Al) + 1.0mm W (+1mm Al)

 *** data items:  261088000 (  99232.91 Hz)
 *** ADC events:   41690396 (  15845.46 Hz)
 *** time warps:          0 (      0.00 Hz)
 *** DSSSD # 1 count:   5823816 old count:   5806214 dt:    343.81 s  LEC rate:  16939.06 Hz
 *** DSSSD # 2 count:   5673289 old count:   5657311 dt:    343.81 s  LEC rate:  16501.24 Hz
 *** DSSSD # 3 count:   2708029 old count:   2701714 dt:    343.81 s  LEC rate:   7876.53 Hz
 *** DSSSD # 4 count:   2583742 old count:   2576481 dt:    343.81 s  LEC rate:   7515.03 Hz
 *** DSSSD # 5 count:   1480052 old count:   1475781 dt:    343.81 s  LEC rate:   4304.85 Hz
 *** DSSSD # 6 count:   3956442 old count:   3945032 dt:    343.81 s  LEC rate:  11507.64 Hz
 *** DSSSD # 1 count:       128 old count:       128 dt:    343.81 s  HEC rate:      0.37 Hz
 *** DSSSD # 2 count:       115 old count:       115 dt:    343.81 s  HEC rate:      0.33 Hz
 *** DSSSD # 3 count:        91 old count:        90 dt:    343.81 s  HEC rate:      0.26 Hz
 *** DSSSD # 4 count:        41 old count:        40 dt:    343.81 s  HEC rate:      0.12 Hz
 *** DSSSD # 5 count:        13 old count:        13 dt:    343.81 s  HEC rate:      0.04 Hz
 *** DSSSD # 6 count:        12 old count:        12 dt:    343.81 s  HEC rate:      0.03 Hz

 *** ENTRY finish ends

S O R T    S T O P P E D ..... Sat Nov 26 17:34:41 2016
 

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

      *all* system wide checks OK (zero fails)

17.30 analysis of file RIBF128/R7_1065 - dead time < 0.5%, no timewarps, 3 MBS timewarps - see attachment 6

17.35 online analysis - ADC & disc data synchronised - see attachment 7

      all SortSas spectra & histograms zero'd, waveforms set x-range = 1000ch = 2ms

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

      ASIC settings 2017Mar27-16.12.39

      BigRIPS 149Xe setting, degrader 2mm Al (at F7), 1.3mm Al fixed + 2mm Al variable (at F11)

18.38 Start DAQ
      AIDA file RIBF128/R7_1083
      BRIKEN file 111
      BigRIPS file 4001

      F11 rate ~100Hz, ~50 neutrons/s

18.56 Stop DAQ
      AIDA file RIBF128/R7_1088

18.38 Start DAQ
      AIDA file RIBF128/R7_1088
      BRIKEN file 112
      BigRIPS file 4002

19.03 per DSSSD x versus y (HEC) - see attachment 8
      per DSSSD E_p versus E_n (HEC) 20MeV/ch nominal - see attachment 9
  
      Rates from offline analysis RIBF128/R7_1089

 *** DSSSD # 1 count:    258088 old count:    206122 dt:      1.03 s  LEC rate:  50652.59 Hz
 *** DSSSD # 2 count:    377054 old count:    301162 dt:      1.03 s  LEC rate:  73973.87 Hz
 *** DSSSD # 3 count:    113574 old count:     89972 dt:      1.03 s  LEC rate:  23005.47 Hz
 *** DSSSD # 4 count:    104475 old count:     83626 dt:      1.03 s  LEC rate:  20322.05 Hz
 *** DSSSD # 5 count:     34511 old count:     27812 dt:      1.03 s  LEC rate:   6529.69 Hz
 *** DSSSD # 6 count:     78446 old count:     62771 dt:      1.03 s  LEC rate:  15278.82 Hz
 *** DSSSD # 1 count:         2 old count:         2 dt:      1.03 s  HEC rate:      0.00 Hz
 *** DSSSD # 2 count:        95 old count:        76 dt:      1.03 s  HEC rate:     18.52 Hz
 *** DSSSD # 3 count:        30 old count:        24 dt:      1.03 s  HEC rate:      5.85 Hz
 *** DSSSD # 4 count:        12 old count:         8 dt:      1.03 s  HEC rate:      3.90 Hz
 *** DSSSD # 5 count:        27 old count:        24 dt:      1.03 s  HEC rate:      2.92 Hz
 *** DSSSD # 6 count:        81 old count:        67 dt:      1.03 s  HEC rate:     13.65 Hz

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

      *all* system wide checks OK (zero fails)

19.30 analysis of file RIBF128/R7_1095 - dead time 1%, no timewarps, 1 MBS timewarps - see attachment 15

20.00 Stop DAQ
      AIDA file RIBF128/R7_1104

18.38 Start DAQ
      AIDA file RIBF128/R7_1104
      BRIKEN file 113
      BigRIPS file 4003

      BigRIPS slit change and n background check

20.27 Stop DAQ
      AIDA file RIBF128/R7_1111

20.28 Start DAQ
      AIDA file RIBF128/R7_1111
      BRIKEN file 114
      BigRIPS file 4004

      BigRIPS F1 slits changed

20.28 all SortSas spectra zero'd


21.15 Start DAQ
      AIDA file RIBF128/R7_1123
      BRIKEN file 115
      BigRIPS file 4005

21.32 RF down

22.15 Stop DAQ
      AIDA file RIBF128/R7_1138

20.28 Start DAQ
      AIDA file RIBF128/R7_1138
      BRIKEN file 116
      BigRIPS file 4006

22.37 Detector biases & leakage currents OK - see attachments 16 & 17
      FEE64 Temperatures OK - see attachment 18
      good events statistics stable & OK - see attachment 19
      No warnings/errors reported by merger since DAQ GO - see attachment 20

      *all* system wide checks OK (zero fails)

22.42 analysis of file RIBF128/R7_1095 - dead time ~1%, no timewarps, 2 MBS timewarps - see attachment 21

22.48 online analysus
      per DSSSD x versus y (HEC) - see attachment 22
      per DSSSD E_p versus E_n (HEC) 20MeV/ch nominal - see attachment 23
      ADC & disc data synchronised - see attachment 24

      offline analysis RIBF128/R7_1146 rates

 *** DSSSD # 1 count:    389187 old count:    340234 dt:      1.02 s  LEC rate:  47972.00 Hz
 *** DSSSD # 2 count:    562493 old count:    494318 dt:      1.02 s  LEC rate:  66808.79 Hz
 *** DSSSD # 3 count:    168279 old count:    147281 dt:      1.02 s  LEC rate:  20577.21 Hz
 *** DSSSD # 4 count:    156439 old count:    136327 dt:      1.02 s  LEC rate:  19708.96 Hz
 *** DSSSD # 5 count:     52041 old count:     45539 dt:      1.02 s  LEC rate:   6371.70 Hz
 *** DSSSD # 6 count:    121463 old count:    106320 dt:      1.02 s  LEC rate:  14839.54 Hz
 *** DSSSD # 1 count:         1 old count:         1 dt:      1.02 s  HEC rate:      0.00 Hz
 *** DSSSD # 2 count:        66 old count:        57 dt:      1.02 s  HEC rate:      8.82 Hz
 *** DSSSD # 3 count:        41 old count:        35 dt:      1.02 s  HEC rate:      5.88 Hz
 *** DSSSD # 4 count:         1 old count:         1 dt:      1.02 s  HEC rate:      0.00 Hz
 *** DSSSD # 5 count:        11 old count:        11 dt:      1.02 s  HEC rate:      0.00 Hz
 *** DSSSD # 6 count:        82 old count:        66 dt:      1.02 s  HEC rate:     15.68 Hz


23.15 Stop DAQ
      AIDA file RIBF128/R7_1153

23.15 Start DAQ
      AIDA file RIBF128/R7_1153
      BRIKEN file 117
      BigRIPS file 4007

23.38 beam lost - RF restart
      AIDA file RIBF128/R7_1158

Implantation profile in AIDA

    BigRIPS file 1028 (Attachment run1028.png):  Degrader setting: 3 mm Pb(fix) + 0.8 mm W(variable) + 2 mm Al(variable)

    BigRIPS file 1033 (Attachment run1033.png):  Degrader setting: 3 mm Pb(fix) + 0.8 mm W(variable) + 2 mm Al(variable) + 1 mm Al(fix)

    BigRIPS file 1012 is in https://elog.ph.ed.ac.uk/AIDA/478 Degrader setting: 3 mm Pb(fix) + 1.3 mm W(variable) + 2 mm Al(variable)

    Observation: Some Mg isotopes (38, 40) is implanted in last DSSD or out the DSSD stacks. We may need to add more degrader!

Equivalent thickness of W, Pb and Al degraders

   The measured implantation profiles agree with LISE estiamtes for the equivalent change in implantation depth for W, Pb and Al. These were estimated with LISE by comparing change of range in Si for 1mm   degrader of each material (see attachments). Note that W produces a larger change in range than Pb (higher density; according to LISE database).

     1 mm Al: 1.15 mm in Si

     1 mm W: 5.40 mm in Si

     1 mm Pb: 3.05 mm in Si

The current configuration (run Mg401033) gives:

    3 mm Pb + 0.8 mm W + 3 mm Al  = 16.9 mm Si

Probably our best alternative (unless we can go in and rearrange fixed degraders) is:

   3 mm Pb + 1.3 mm W + 3 mm Al = 19.6 mm Si: move implantation depth 2.7 mm upstream

Here is a spreadsheet where you can play with the numbers and create test your own solution to the puzzle: https://docs.google.com/spreadsheets/d/1QJp8t98sT3pExAQb3xtHtAvk4TUDVO6alhbLIaNtx8A/edit?usp=sharing

 !!! We did change degrader for the 3mmPb+1.3mmW+3mmAl setting at 22.16 (from AIDA run 26_0); see elog entry https://elog.ph.ed.ac.uk/AIDA/483

04.51 Start run AIDA18.  Beam is back from the operators.
      Scalers are shown as attachment 1
      Leak currents seem okay (all < 5 uA), shown as attachments 2 and 3.
      Discrim levels have a bit of fluctuation depending on the module -- attachment 4
      nnaida24 has some pauses (attachment 5)

09.35 AIDA20* - AIDA24* test runs with no beam, i.e. noise, betas and low rate pulser
      to investigate FEE64 synchronisation 

      AIDA20* nnaida19 data link to Merge program enabled
      AIDA21* - nnaida19 removed from DAQ configuration file (startup.tcl) and server/web browser restarted

12.35 Detector bias & leakage current, FEE temperatures - OK - see attachments 5-7

The main experiment changed to a carbon reaction target at F8 (similar thickness of CH2 previously used), and retuned the ZDS. First BigRIPS run after retuning is 40Mg_1093 (at 2:29 am, Nov 30th)

The background at F11 has increased. The neutron backgroun incresead by a factor of ~10. The rates of visual scalers also increased; for example Si Top/Bottom from about 50 Hz to 300 Hz (see attachment 1).

One possible explanation are higher light particle rate at F11. By comparing the PID for C target (attachment 2) with that of CH2 target setting (e.g. https://elog.ph.ed.ac.uk/AIDA/492), it looks like the new conditions have a higher transmission for A/Q=3 fragments (3H et al). Also, in the new setting the Si isotopes are also transmitted to F11.

The implantation depth is still good; same as we had for C target at F8 (compare 40Al distribution in attachment 3 with what we had before).

Sat. 12/12/15

Working with a 8-FEE setup (as in https://elog.ph.ed.ac.uk/AIDA/133). We could open a file with the 
TapeServer. Merger also seems to be working (cursor spinning, and merge statistics ~ok). However the 
TapeServer doesn’t write anything to disk (just empty an file).

A few observations; I only took ‘systematic’ notes after we had reduced the number of FEEs to 8, but it's 
likely we were also facing the same problems before with a full system:

+ When enabling data transfer from NNAIDA modules (in Run Control page), it switches to the right mode for 
all FEEs except for NNAIDA5. NNAIDA5 is the master FEE. The merger also doesn’t show any stats for NNAIDA5 
(but stats look ok for all other FEEs). The spectra for NNAIDA5 look ok, so the FEE is generating data.

+ A few times we observe the following behavior: DAQ running without trouble. We start Merger+TapeServer, 
and when attempting some actions in RunControl (start-stop, or reset), we loose the ability to communicate 
with a number of FEEs. These FEEs can not perform a ReSYNC, and the only way to get them back to life is 
going through a power cycle. It seems like the TaperServer or Merger is somehow upsetting the FEEs or the 
DAQ. We can still ‘ping’ all FEEs, even after the ‘connect failed’ message. 

Attached are a few screenshots, and the text in the terminals for Merger and TapeServer. The following is 
the error returned by one FEE when we can’t ReSync them:


STATE for nnaida3 returned with an error
connect failed 
NONE
connect failed 
    while executing
"::http::geturl http://nnaida3:8015/DataAcquisitionControlServer -headers {} -type text/xml -timeout 20000 
-query {<?xml version="1.0" encoding="UTF-8"..."
    ("eval" body line 1)
    invoked from within
"eval [list ::http::geturl $url] $args"
    (procedure "::http::geturl_followRedirects" line 4)
    invoked from within
"::http::geturl_followRedirects http://nnaida3:8015/DataAcquisitionControlServer -headers {} -type 
text/xml -timeout 20000 -query {<?xml version="1.0" ..."
    ("eval" body line 1)
    invoked from within
"eval ::http::geturl_followRedirects [list $url]  -headers [list $local_headers]  -type text/xml  -timeout 
$timeout  -query [list $request]  $local_pro..."
    (procedure "::SOAP::Transport::http::xfer" line 61)
    invoked from within
"$transport $procVarName $url $req"
    (procedure "::SOAP::invoke" line 18)
    invoked from within
"::SOAP::invoke ::SOAP::_DataAcquisitionControlClient__GetState"
    ("eval" body line 1)
    invoked from within
"eval ::SOAP::invoke ::SOAP::_DataAcquisitionControlClient__GetState $args"
    (procedure "DataAcquisitionControlClient__GetState" line 1)
    invoked from within
"DataAcquisitionControlClient__GetState"
GET OPTION for nnaida3 returned with an error
connect failed 
NONE
connect failed 
    while executing
"::http::geturl http://nnaida3:8015/DataAcquisitionControlServer -headers {} -type text/xml -timeout 60000 
-query {<?xml version="1.0" encoding="UTF-8"..."
    ("eval" body line 1)
    invoked from within
"eval [list ::http::geturl $url] $args"
    (procedure "::http::geturl_followRedirects" line 4)
    invoked from within
"::http::geturl_followRedirects http://nnaida3:8015/DataAcquisitionControlServer -headers {} -type 
text/xml -timeout 60000 -query {<?xml version="1.0" ..."
    ("eval" body line 1)
    invoked from within
"eval ::http::geturl_followRedirects [list $url]  -headers [list $local_headers]  -type text/xml  -timeout 
$timeout  -query [list $request]  $local_pro..."
    (procedure "::SOAP::Transport::http::xfer" line 61)
    invoked from within
"$transport $procVarName $url $req"
    (procedure "::SOAP::invoke" line 18)
    invoked from within
"::SOAP::invoke ::SOAP::_DataAcquisitionControlClient__GetOption NetVar=NetVar.DACQ.Chistenable"
    ("eval" body line 1)
    invoked from within
"eval ::SOAP::invoke ::SOAP::_DataAcquisitionControlClient__GetOption $args"
    (procedure "DataAcquisitionControlClient__GetOption" line 1)
    invoked from within
"DataAcquisitionControlClient__GetOption "$AcqGetOption""

The attached plots show the time-stamp data in the EURICA files with PID information (EventInfo.timestamp). The
timestamp value should correspond to the correlation scaler included as info_code==8 in AIDA. 

The plots show time-stamp vs entry number in the TTree of the Root file, with the events in groups of about 10
*.root files counted consecutively. To map entry-number to data file use informatino of number of entries per
file in the lines bellow (output of analysis script). NOTE: label for plots in right colume is wrong, trigger
type=3 (pulser) in stead of 2.

The final three plots (pulser_dts_go4_3022*.png) show the time difference between two sequential data points of a
given trigger type (fBit==2 or 3). The value that would correspond to the external scaler (fBit==3) has a peak at
about delta(ts)= 1.7 sec, but also a lot of events with a distribution centered around a smaller value of
delta(ts)~ 10 msec! One can also see the deadtime at about 300 usec at a smaller scale. The units for the
time-stamp are 1-ns.

A plot of a similar distribution for the data in AIDA shows that the peak of the correlation scaler has, in this
case, a very narrow distribution, with a frequency of ~43.5e6 x 40 ns (would agree with Go4 data from EURICA).

When scanning the files the analysis script (attached) skips a given number of entries (~100) to speed up the
analysis.


Number of entries in PID tree= 2592193 for file /Disk/ds-sopa-group/np/RIKEN/May2015/PID_data/go4_3002.root
(accumulated= 2592193)
Number of entries in PID tree= 2570084 for file /Disk/ds-sopa-group/np/RIKEN/May2015/PID_data/go4_3003.root
(accumulated= 5162277)
Number of entries in PID tree= 676355 for file /Disk/ds-sopa-group/np/RIKEN/May2015/PID_data/go4_3004.root
(accumulated= 5838632)
Number of entries in PID tree= 2582203 for file /Disk/ds-sopa-group/np/RIKEN/May2015/PID_data/go4_3005.root
(accumulated= 8420835)
Number of entries in PID tree= 2602541 for file /Disk/ds-sopa-group/np/RIKEN/May2015/PID_data/go4_3006.root
(accumulated= 11023376)
Number of entries in PID tree= 2602681 for file /Disk/ds-sopa-group/np/RIKEN/May2015/PID_data/go4_3007.root
(accumulated= 13626057)
Number of entries in PID tree= 2605726 for file /Disk/ds-sopa-group/np/RIKEN/May2015/PID_data/go4_3008.root
(accumulated= 16231783)
Number of entries in PID tree= 2606264 for file /Disk/ds-sopa-group/np/RIKEN/May2015/PID_data/go4_3009.root
(accumulated= 18838047)
Number of entries in PID tree= 2603841 for file /Disk/ds-sopa-group/np/RIKEN/May2015/PID_data/go4_3010.root
(accumulated= 21441888)
Number of entries in PID tree= 2599770 for file /Disk/ds-sopa-group/np/RIKEN/May2015/PID_data/go4_3011.root
(accumulated= 24041658)

Number of entries in PID tree= 2601002 for file /Disk/ds-sopa-group/np/RIKEN/May2015/PID_data/go4_3012.root
(accumulated= 2601002)
Number of entries in PID tree= 2598946 for file /Disk/ds-sopa-group/np/RIKEN/May2015/PID_data/go4_3013.root
(accumulated= 5199948)
Number of entries in PID tree= 2596582 for file /Disk/ds-sopa-group/np/RIKEN/May2015/PID_data/go4_3014.root
(accumulated= 7796530)
Number of entries in PID tree= 2596506 for file /Disk/ds-sopa-group/np/RIKEN/May2015/PID_data/go4_3015.root
(accumulated= 10393036)
Number of entries in PID tree= 2588772 for file /Disk/ds-sopa-group/np/RIKEN/May2015/PID_data/go4_3016.root
(accumulated= 12981808)
Number of entries in PID tree= 2583160 for file /Disk/ds-sopa-group/np/RIKEN/May2015/PID_data/go4_3017.root
(accumulated= 15564968)
Number of entries in PID tree= 2589905 for file /Disk/ds-sopa-group/np/RIKEN/May2015/PID_data/go4_3018.root
(accumulated= 18154873)
Number of entries in PID tree= 2581979 for file /Disk/ds-sopa-group/np/RIKEN/May2015/PID_data/go4_3019.root
(accumulated= 20736852)
Number of entries in PID tree= 2582410 for file /Disk/ds-sopa-group/np/RIKEN/May2015/PID_data/go4_3020.root
(accumulated= 23319262)
Number of entries in PID tree= 2582181 for file /Disk/ds-sopa-group/np/RIKEN/May2015/PID_data/go4_3021.root
(accumulated= 25901443)

Number of entries in PID tree= 2580798 for file /Disk/ds-sopa-group/np/RIKEN/May2015/PID_data/go4_3022.root
(accumulated= 2580798)
Number of entries in PID tree= 2580669 for file /Disk/ds-sopa-group/np/RIKEN/May2015/PID_data/go4_3023.root
(accumulated= 5161467)
Number of entries in PID tree= 2583346 for file /Disk/ds-sopa-group/np/RIKEN/May2015/PID_data/go4_3024.root
(accumulated= 7744813)
Number of entries in PID tree= 2645673 for file /Disk/ds-sopa-group/np/RIKEN/May2015/PID_data/go4_3025.root
(accumulated= 10390486)
Number of entries in PID tree= 1984963 for file /Disk/ds-sopa-group/np/RIKEN/May2015/PID_data/go4_3026.root
(accumulated= 12375449)
Number of entries in PID tree= 2629453 for file /Disk/ds-sopa-group/np/RIKEN/May2015/PID_data/go4_3027.root
(accumulated= 15004902)
Number of entries in PID tree= 2636095 for file /Disk/ds-sopa-group/np/RIKEN/May2015/PID_data/go4_3028.root
(accumulated= 17640997)
Number of entries in PID tree= 2639067 for file /Disk/ds-sopa-group/np/RIKEN/May2015/PID_data/go4_3029.root
(accumulated= 20280064)
Number of entries in PID tree= 2643485 for file /Disk/ds-sopa-group/np/RIKEN/May2015/PID_data/go4_3030.root
(accumulated= 22923549)
Number of entries in PID tree= 2644457 for file /Disk/ds-sopa-group/np/RIKEN/May2015/PID_data/go4_3031.root
(accumulated= 25568006)

Number of entries in PID tree= 2643522 for file /Disk/ds-sopa-group/np/RIKEN/May2015/PID_data/go4_3032.root
(accumulated= 2643522)
Number of entries in PID tree= 2641053 for file /Disk/ds-sopa-group/np/RIKEN/May2015/PID_data/go4_3033.root
(accumulated= 5284575)
Number of entries in PID tree= 2637280 for file /Disk/ds-sopa-group/np/RIKEN/May2015/PID_data/go4_3034.root
(accumulated= 7921855)
Number of entries in PID tree= 2627822 for file /Disk/ds-sopa-group/np/RIKEN/May2015/PID_data/go4_3035.root
(accumulated= 10549677)
Number of entries in PID tree= 2637326 for file /Disk/ds-sopa-group/np/RIKEN/May2015/PID_data/go4_3036.root
(accumulated= 13187003)
Number of entries in PID tree= 2635601 for file /Disk/ds-sopa-group/np/RIKEN/May2015/PID_data/go4_3037.root
(accumulated= 15822604)
Number of entries in PID tree= 2606912 for file /Disk/ds-sopa-group/np/RIKEN/May2015/PID_data/go4_3038.root
(accumulated= 18429516)
Number of entries in PID tree= 2635101 for file /Disk/ds-sopa-group/np/RIKEN/May2015/PID_data/go4_3039.root
(accumulated= 21064617)
Number of entries in PID tree= 2634932 for file /Disk/ds-sopa-group/np/RIKEN/May2015/PID_data/go4_3040.root
(accumulated= 23699549)
Number of entries in PID tree= 2633415 for file /Disk/ds-sopa-group/np/RIKEN/May2015/PID_data/go4_3041.root
(accumulated= 26332964)

Number of entries in PID tree= 2633892 for file /Disk/ds-sopa-group/np/RIKEN/May2015/PID_data/go4_3042.root
(accumulated= 2633892)
Number of entries in PID tree= 2640264 for file /Disk/ds-sopa-group/np/RIKEN/May2015/PID_data/go4_3043.root
(accumulated= 5274156)
Number of entries in PID tree= 2612700 for file /Disk/ds-sopa-group/np/RIKEN/May2015/PID_data/go4_3044.root
(accumulated= 7886856)
Number of entries in PID tree= 2632762 for file /Disk/ds-sopa-group/np/RIKEN/May2015/PID_data/go4_3045.root
(accumulated= 10519618)
Number of entries in PID tree= 1962430 for file /Disk/ds-sopa-group/np/RIKEN/May2015/PID_data/go4_3046.root
(accumulated= 12482048)
Number of entries in PID tree= 2611491 for file /Disk/ds-sopa-group/np/RIKEN/May2015/PID_data/go4_3047.root
(accumulated= 15093539)
Number of entries in PID tree= 2649244 for file /Disk/ds-sopa-group/np/RIKEN/May2015/PID_data/go4_3048.root
(accumulated= 17742783)
Number of entries in PID tree= 2679210 for file /Disk/ds-sopa-group/np/RIKEN/May2015/PID_data/go4_3049.root
(accumulated= 20421993)
Number of entries in PID tree= 518667 for file /Disk/ds-sopa-group/np/RIKEN/May2015/PID_data/go4_3050.root
(accumulated= 20940660)

We noticed a peculiar feature in the time-stamp synchronization monitor. The spectra of timestamp difference between pairs of DAQ systems show, for all possible pair combinations, a peak at Delta(ts)= 65535 = 2**15

This corresponds to a difference of 2.6 ms (for 25MHz correlation clock). See the attachments taken ~23:00 of Nov 28th.

We performed the AIDA system-wide checks (no errors) and a timestamp reset, but the second peak at 65K is still there (we also checked that there is no peak at 2*65K, at least in a short run period).

We also observed a double peak for timestam-differences close to zero, which we interpret as good correlations (attachment 2). Note, however, that this double peak became much supprese around midnight (see attachment 6 and 7).

From analysis of ion (BigRIPS) and implant (AIDA) correlations we have some confidence that these two DAQs are synchronized; see entry https://elog.ph.ed.ac.uk/AIDA/492 where we identify an implant for 20% ofions at F11 (and with an implantatin profile that, for example, is consistent with changes to the degrader configuration)

Attached are Paul Morrall's instructions on how to move new AIDA support table into place, for a setup with 
EURICA at F11 (March 2015).