We started the synchronization monitoring programs to check that
it is OK as can be seen in the figure below

We are using the same scheme used during Ahn parasitic run,
namely the synchronization check signal is the BigRIPS trigger
signal send by them to us (AIDA, BRIKEN).

The monitorization procedure is different from the one used
in 2016. The description to lauch the processes is described
here below and in the attached PDF.

***********

To Launch the processes:

Open 4 terminals:

Terminal 1 (DataSink) type:

>ssh aida@d05

>cd /home/aida/DataPackage/DataSink/Linux64

>DataSink -i 3

Terminal 2 (SynCheck) type:

>ssh aida@d05

>cd /home/aida/SyncCheck

>./SynCheck

Terminal 3 (BigRIPS Data Relay) type:

>ssh aida@d05

>cd /home/aida/ribfts/ribftssender

>./ribftssender_mar17ca debug

(specific for current 40Ca parasitic run because we are not sending
a pulse signal to  BigRIPS as trigger but receiving triggers from
BigRIPS to create the pulses)

Terminal 4 (AIDA Data Relay) type:

>npg@aidas1
>DataRelayFilter -n 10.32.0.12 -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 d05 PC.
The programming transmitting the data from AIDA to the DataSink includes an 
intermediate filtering step. This selects only correlation scalers from one 
module (and possibly ADC values from one channel in that module).

Gasific MainWindow (Briken Data Relay):

   In the DAQ Control tab: Click "Start Sync Monitoring" button.

   In the pop up window set server ip and port (ip:10.32.0.12, port:10305)

By default this perform a check on the differences RIBF-BRIKEN and AIDA-BRIKEN.

In case that BRIKEN is not running, the option "SynCheck -M 1" check the differences 
AIDA-RIBF and BRIKEN-RIBF, while "SynCheck -M 2" checks RIBF-AIDA and BRIKEN-AIDA

To synchronize:

   In the Gasific MainWindow, DAQ Control tab: Click "Send Sync Pulse" button