[subexp-daq] Question on DRASI
Håkan T Johansson
f96hajo at chalmers.se
Thu Jun 6 18:22:22 CEST 2024
On Thu, 6 Jun 2024, Weber, Guenter Dr. wrote:
>
> Dear Håkan,
>
>
> at the moment, we are characterizing our DAQ and have an event every ~0.1
> seconds. We would then immediatly like to check if this event agrees with
> what we fed into the DAQ system.
>
>
> Would flush=1 force the DAQ to send out each event after it was recorded?
No, after 1 s at most in that case. At the moment there is no 'immediate'
flush.
The --server=drasi,... would be the one. But that by default has a 0.5 s
timeout, so can only be made worse wioth the --flush option.
> And if yes, where should I put here?
>
>
> ../r3bfuser/build_cc_ppc-linux_4.2.2_debug/m_read_meb.drasi \
> --label=MCAL2 \
> --triva=master,fctime=10,ctime=50 \
> --server=drasi,dest=lyserv \
> --buf=size=400Mi \
> --max-ev-size=0x1000000 \
> --subev=crate=1,type=20,subtype=2,control=9,procid=1 \
> --eb=lyserv \
Please try to add it in the --server=... options of the event builder.
Cheers,
Håkan
>
>
> Thank you very much!
>
>
>
>
> Best greetings
>
> Günter
>
>
>
> ____________________________________________________________________________
> Von: subexp-daq <subexp-daq-bounces at lists.chalmers.se> im Auftrag von Håkan
> T Johansson <f96hajo at chalmers.se>
> Gesendet: Donnerstag, 6. Juni 2024 16:50:34
> An: Discuss use of Nurdlib, TRLO II, drasi and UCESB.
> Betreff: Re: [subexp-daq] Question on DRASI
>
> Dear Günter,
>
> how long delays are you experiencing?
>
> The default partial buffer timeouts of drasi transport/stream network
> servers looks like they should be 2 or 4 s, depending on the buffer size
> (larger for > 4 MB).
>
> The file writing partial buffer timeout is 30 s.
>
> There are flush=Ns options both for the --server=... and --file-writer=...
> commands.
>
> The modules are read out event-by-event?
> Or there might be some buffering going on there as well?
>
> Cheers,
> Håkan
>
>
>
> On Thu, 6 Jun 2024, Weber, Guenter Dr. wrote:
>
> >
> > Dear friends,
> >
> >
> > is it possible to tell the DAQ that it should send out each event right
> > after it was collected? To us it looks like our DAQ is releasing the
> > collected data in 'bursts'.
> >
> >
> >
> >
> > Thank you very much!
> >
> >
> >
> > Best greetings
> >
> > Günter
> >
> >
> >
> >
> >
>
>
More information about the subexp-daq
mailing list