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

The polyethelene arrived at RIKEN. Except 4 neighboring holes (located at the inner ring) the alignment is OK.

Here is a picture of one of our Mesytec preamplifiers. We have  located all seven of them. 
They  have 16 input channels and a common SHV per board.

<p>&nbsp;<a href="141031_125516/24.png?lb=BRIKEN"><img border="0" alt="24.png" src="141031_125516/24.png?
lb=BRIKEN&amp;thumb=1" name="att0" id="att0" /></a></p>

A elog for the setup of the BRIKEN detector is now operational at https://elog.ph.ed.ac.uk/BRIKEN/

We have setup a list of emails that will receive automatic updates for each new entry to the logbook: C. Domingo, G. Lorusso, T. Davinson, A. Estrade, K. Rykaczewski, J.L. Tain, C. Griffin, S. Nishimura, I. Dillman, F. Montes, J. Agramunt, G. Cortes, F. Calvino, M. Marta

A elog for the setup of the BRIKEN detector is now operational at https://elog.ph.ed.ac.uk/BRIKEN/