ELOG BRIKEN

AIDA GELINA BRIKEN nToF CRIB ISOLDE CIRCE nTOFCapture DESPEC DTAS EDI_PSA 179Ta CARME StellarModelling DCF K40

BRIKEN

Fields marked with * are required

Entry time:

Wed Feb 25 07:38:42 2015

Author*:

Subject*:

In order to access to the synchronization test, we prepare two programs in the PC&nbsp; 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 &quot;SynCheck -M 1&quot; perform de differences AIDA-RIBF and BRIKEN-RIBF, and &quot;SynCheck -M 2&quot;&nbsp; RIBF-AIDA and BRIKEN-AIDA
&nbsp;
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 
&nbsp;
&quot;-I 2&quot; 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).
&nbsp;
&nbsp;

Encoding: HTML ELCode plain
Suppress Email notification Resubmit as new entry

Attachment 1:

15.png Original size: 1920x1080

Attachment 2:

DataRelayFilter_terminal.png Original size: 1210x949

Attachment 3:

Drop attachments here...

ELOG V3.1.4-unknown