AIDA
GELINA
BRIKEN
nToF
CRIB
ISOLDE
CIRCE
nTOFCapture
DESPEC
DTAS
EDI_PSA
179Ta
CARME
StellarModelling
DCF
K40
BRIKEN
Draft saved at 00:00:00
Fields marked with
*
are required
Entry time:
Sat Mar 29 11:35:39 2025
Author
*
:
Subject
*
:
<p>In order to access to the synchronization test, we prepare two programs in the PC briken1 ( 10.32.6.54).</p> <p>To Launch the processes, in a terminal type: DataSink -i 3</p> <p>In other terminal type SynCheck</p> <p>By default this preform a test with difference RIBF-BRIKEN and AIDA-BRIKEN.</p> <p>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</p> <p> </p> <p>AIDA Data Relay:</p> <p>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).</p> <p>To run the program from aidas1 PC:</p> <p>DataRelayFilter -n 10.32.6.54 -p 10307 -I 2<br /> </p> <p>"-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.</p> <p>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).</p> <p> </p> <p> </p>
Encoding
:
HTML
ELCode
plain
Suppress Email notification
Attachment 1:
Drop attachments here...
Draft saved at 00:00:00
ELOG V3.1.4-unknown