AIDA GELINA BRIKEN nToF CRIB ISOLDE CIRCE nTOFCapture DESPEC DTAS EDI_PSA 179Ta CARME StellarModelling DCF K40
  BRIKEN  ELOG logo
Message ID: 6     Entry time: Wed Feb 25 07:38:42 2015
Author: A. Estrade J. Agramunt  
Subject: Usage of synchronization test programs 

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

 

 

Attachment 1: 15.png  216 kB  | Hide | Hide all
15.png
Attachment 2: DataRelayFilter_terminal.png  344 kB  Uploaded Wed Feb 25 09:46:49 2015  | Hide | Hide all
DataRelayFilter_terminal.png
ELOG V3.1.4-unknown