The Al degrader thickness was reduced to 4.8mm

Beam still down. New background measurement
with new RIKEN tube below the MUSIC chamber 
(call it B)

File: 150505_0040_1130_aprox_bckg.root
Average rate per tube (n/s): U=0.0073, D=0.0065, B=0.0070

Failure of a quadrupole triplet at BigRIPS (some time after earthquake)

We take the chance of measuring background:

File: 150504_1500_2047_bckg.root
Rate per tube (n/s): U=0.098, D=0.0062, US=0.0200
Ratio to 1st 110Zr: U=1.38,  D=1.99,  US=0.90
Notes:
-Compared to the 1st background measurement there are changes
larger than expected statistical fluctuations: 
perhaps due to slight changes in noise

For EURICA measurements degrader thickness were increased
trying to decrease MACI and AIDA trigger rate
Before we had 5.7 mm of Al
Now we have: 
Degrader: 4.0 + 1.0 + 0.6 + 0.4 +0.3 = 6.3 mm of Al
also 2x 0.8mm Al plates were added before 
the MACI start detector (thus covering partially AIDA)
Trigger from AIDA will be taken from 3rd DSSSD

The Lower polyethylene pieces was swamped.

In the photo beam comes from the left.

 New detector placed under the beam line, below MUSIC chamber

This detector replace the USA tubes in the DACQ because we need the preamp to plug it.

AIDA trigger plugged in Mod2 Ch12

We have some new rule about the data taken at RNC from this year.

Shunji

94Se setting:
File: 150503_1500_1554_94Se.root
Rate per tube (n/s): U=0.966, D=0.263, US=0.538
Ratio to 1st 110Zr: U=2.00,  D=1.89,  US=1.84
Notes:
-Compared to the 1st 94Se setting measurement (12:19-13:19)
there is a drop of 25% in the rate without apparent reason

Photos of the general arrangement and details of the new PE blocks

U: (Up: 2 RIKEN tubes at 40cm from AIDA)
D: (Down: 12 RIKEN tubes at 80cm from AIDA)
US: (2 ORNL 2" tubes close to the floor at 1.8m from AIDA)

Natural background:
File: 150426_Bckg_1425_1805.root
Rate per tube (n/s): U=0.0071, D=0.0045, US=0.0222
Notes: 
-This rate seems quite small but we should remember 
that we are underground. 
-The fact that U is larger than D could be explained as 
related that the amount of PE around tubes is larger. 
-For comparison: 
BELEN-20@JYFL=0.6n/s (no beam), 0.9n/s (beam)
BELEN-30@GSI=1.2n/s (beam)
BELEN-48@JYFL=1.5n/s

110Zr setting:
File:150501_16111810_110Zr.root
Rate per tube (n/s): U=0.483, D=0.139, US=0.292
Ratio to background: U=68.3,  D=31.1,  US=13.2

Individual tube distribution:
U1	0.280	D1	0.087	D7	0.084	US1	0.132
U2	0.249	D2	0.092	D8	0.084	US2	0.188
		D3	0.083	D9	0.077		
		D4	0.075	D10	0.070		
		D5	0.073	D11	0.069		
		D6	0.065	D12	0.054		

Notes:
-There is huge increase of with beam
-The drop of increase with distance is consistent
with either beam induced or decay of implants

110Zr setting:
File: 150501_1733_1900_110Zr.root (actually 02/05)
Rate per tube (n/s): U=0.869, D=0.242, US=0.516
Ratio to 1st 110Zr: U=1.80,  D=1.74,  US=1.77
Notes:
-We don't quite understand the reason for the near factor two
difference since apparently the settings are the same and beam was
rather stable

In order to investigate the point of origin of the neutrons
we add extra PE covering D5,D6,D11,D12 from the top and
D1,D2,D7,D8 from the front

88Ge setting:
File: 150502_21502333_88Ge.root
Rate per tube (n/s): U=1.271, D=0.349, US=0.706
Ratio to 1st 110Zr: U=2.63,  D=2.51,  US=2.42

Individual rates:
U1	1.340	D1	0.424	D7	0.402	US1	0.576
U2	1.202	D2	0.446	D8	0.381	US2	0.835
		D3	0.408	D9	0.342		
		D4	0.393	D10	0.315		
		D5	0.359	D11	0.250		
		D6	0.275	D12	0.193		

Notes:
-One notices a relative drop of rate for D6, D11 and D12
pointing to a source located in the vicinity of AIDA

94Se setting:
File: 150503_1219_1319_94Se.root
Rate per tube (n/s): U=1.267, D=0.349, US=0.717
Ratio to 1st 110Zr: U=2.62,  D=2.51,  US=2.46
Notes:
-Very similar to 88Ge measurement

A test program for online data transfer is available in aidas1 PC at:

/homes/npg/aev/AIDAbriken/AIDA-jorge-san.exe

no arguments are required to run it from command line

3He tube drawings and technical details: 
RIKEN, UPC, GSI, ORNL-1, ORNL-2

Based on an about 8h long background measurement, the neutron background at the Eurica site was found to be about 0.006 neutron / sec (in the Riken tubes) and 0.019 neutron / sec (in the ORNL tubes). The beam was OFF.

Altogether 16  tubes are mounted for the parasitic detector test (see the attached photos):

- two tubes (belonging to RIKEN) are in a 10 cm x 10 cm x 30 cm polyethylene matrix inside Eurica, the distance from AIDA is about 30 cm

- 12 tubes (belonging to RIKEN) are in a 20 xm x 30 xm x 30 cm matrix, outside (below) Eurica, at the closest possible place to AIDA, the distance is about 60 cm

- further two tubes (ORNL) are at the bottom of the Eurica support, about 1.2 m from the AIDA Silicon.

Furthermore, spectra measured using a 252Cf source is attached to this report, too (Jap1Cf-RIKEN tube, Us1Cf-ORNL tube). At the moment a background measurement is running.

In order to access to the synchronization test, we prepare two programs in the PC  briken1 ( 10.32.6.54).

To Launch the processes, in a terminal type: DataSink -i 3

In other terminal type SynCheck

By default this preform a test with difference RIBF-BRIKEN and AIDA-BRIKEN.

In case of BRIKEN is not running, the option "SynCheck -M 1" perform de differences AIDA-RIBF and BRIKEN-RIBF, and "SynCheck -M 2"  RIBF-AIDA and BRIKEN-AIDA

AIDA Data Relay:

The programming transmitting the data from AIDA to the DataSink includes an intermediate filtering step. This selects only correlation scalars from one module (and possibly ADC values from one channel in that module).

To run the program from aidas1 PC:

DataRelayFilter -n 10.32.6.54 -p 10307 -I 2
 

"-I 2" selects ID 2 as the one for the AIDA data stream, which must correspond to the one expected by the DataSink in the briken1 PC.

The attached screenshot show the terminal when running the code in verbose mode (-v 1), and also sending the ADC energy of the pulser in channel 10 of NNAIDA11 (adc ~38600 ch). This was for random pulser; for a fixed pulser delta will show constant value of delta (timestamp difference between consecutive correlationpulses).

We have performed a successful test of the integration of independent DAQ systems based on a correlation 
scalar counted from a common clock signal. The principles of the integration method are described in the 
following AIDA elog entry: https://elog.ph.ed.ac.uk/AIDA/29

The configuration of the setup we used in the RIKEN test is described by the attached figure:
DAQcorrelation_diagram.pdf. The chosen solution was to use a 25 MHz clock generated by the MACB modules of 
AIDA, which was distributed to the other two systems by a SIS36/38xx module in the BRIKEN VME crate (a 
slightly modified versio of the method proposed by PCS in AIDA Elog#29).

The correlation can be monitored online using the MIDAS DataXfer and DataSpy toolkits 
(http://npg.dl.ac.uk/MIDAS/DataAcq/Data.html). Each system operates a DataRelay program that sends a data 
stream consisting only of IDs and time-stamps to a common DataSink (this requires a DataRelay code that 
does 
some filtering of the raw data). The scheme is shown in the attached diagram (DAQsoftware.pdf).

The DataPeek_Merge and SyncCheck codes use C++11 for parallelization of tasks, which is a helpful feature 
to
improve the efficiency of finding coincidences between the correlation pulses. Thus,  the code will not 
run 
in PCs with any Linux version. For example, it requires version 7 of ScientificLinux, which installed in 
the 
PC being used for BRIKEN DAQ control that will stay at RIBF for the time being.


++ SYNCHRONIZATION RESULTS ++

The figure correlation_25Hz.png shows a correlation plot for the BRIKEN+RIBF+AIDA running with 
correlations 
done by a pulser at 25 Hz. A large fraction of the pulsers appear in the double-coincidence plots (top 
row; 
same plots, except the 'Partial' one is automatically cleared every ~10seconds).

The bottom plots show the pair-wise correlations between BRIKEN and RIBF or AIDA. BRIKEN was defined as 
the
'master' in this test, but current version of the program is flexible to select any stream as the master 
one.

The second figure (correlation_random.png) shows the same test, but using a non-periodic pulser to trigger 
the correlation scalar. We observed the same level of synchronization (peaks look broader because of the 
zoom level).