<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<meta name="Generator" content="Microsoft Exchange Server">
<!-- converted from text --><style><!-- .EmailQuote { margin-left: 1pt; padding-left: 4pt; border-left: #800000 2px solid; } --></style>
</head>
<body>
<meta content="text/html; charset=UTF-8">
<style type="text/css" style="">
<!--
p
{margin-top:0;
margin-bottom:0}
-->
</style>
<div dir="ltr">
<div id="x_divtagdefaultwrapper" dir="ltr" style="font-size:14pt; color:#000000; font-family:Calibri,Helvetica,sans-serif">
<p>Dear friends,</p>
<p><br>
</p>
<p>sorry for coming up with a very basic question: How can I define different trigger types and make the readout procedure of a specific module dependent on the type of trigger?</p>
<p><br>
</p>
<p>Example:</p>
<p>I have two different trigger types, 1 and 2. To let the DAQ know, which type of trigger I have, they are plugged to the input channels 1 and 2 of our VOLUM4B. Now I would like to know in the readout of the SIS3316 module, which type triggered the current
event. How do I do this?</p>
<p><br>
</p>
<p><br>
</p>
<p>Thank you very much!</p>
<p><br>
</p>
<p><br>
</p>
<p><br>
</p>
<p>Best greetings from Jena</p>
<p>Günter</p>
<p><br>
</p>
<p><br>
</p>
<p>P.S. As I got distracted by some hardware issues in the lab, we did not have a proper hand-over of our modifications of the SIS3316 code in Nurdlib. Did you in the meantime took over these modifications into the main branch or how is the situation?</p>
<p><br>
</p>
<p><br>
</p>
<div id="x_Signature">
<div style="font-family:Tahoma; font-size:13px"></div>
</div>
</div>
<hr tabindex="-1" style="display:inline-block; width:98%">
<div id="x_divRplyFwdMsg" dir="ltr"><font face="Calibri, sans-serif" color="#000000" style="font-size:11pt"><b>Von:</b> subexp-daq <subexp-daq-bounces@lists.chalmers.se> im Auftrag von Håkan T Johansson <f96hajo@chalmers.se><br>
<b>Gesendet:</b> Sonntag, 16. Februar 2025 11:33:35<br>
<b>An:</b> Bajzek, Martin<br>
<b>Cc:</b> Hubbard, Nicolas James Dr.; subexp-daq@lists.chalmers.se<br>
<b>Betreff:</b> [subexp-daq] dropping of data to analysis that cannot keep up</font>
<div> </div>
</div>
</div>
<font size="2"><span style="font-size:10pt;">
<div class="PlainText"><br>
Hi,<br>
<br>
when the point of DAQ being faster than online is reached, we face the <br>
issue of somehow dropping old data.<br>
<br>
Left with default settings, ucesb is not really helpful. Old data will <br>
pile up in the '--server' until that is full, and only then dropped. If <br>
the server is configured with a large amount of memory for buffers <br>
('--server' option 'size='), this can be significant. This leads to <br>
online analysis lagging reality, loosing the 'online' feeling and useful <br>
rapid feedback of changing conditions...<br>
<br>
There is a 'dropold=N' (seconds) option which will not serve buffers to <br>
the client older than the specified time. It may be reasonable to set <br>
this to at most two times the spill length, if the beam has a pulse <br>
structure. Otherwise a few seconds ought to be enough.<br>
<br>
<br>
A dry-run demo (3 instances), using the 'mbuffer' program to limit rates:<br>
<br>
---<br>
<br>
# Generate data (at 10 MB/s):<br>
<br>
file_input/empty_file --lmd \<br>
| mbuffer -r 10M -q \<br>
| empty/empty --file=- --server=trans,size=1G<br>
<br>
# Serve the data, with dropold (can be removed):<br>
<br>
empty/empty --trans=localhost --server=trans:8000,size=1G,dropold=10s<br>
<br>
# 'Analysis' (at 1 MB/s).<br>
# Look at the data (buffer times)<br>
# Note: dd is used here to strip the 16-byte transport protocol startup <br>
# message.<br>
<br>
nc localhost 8000 \<br>
| mbuffer -r 1M -q \<br>
| dd bs=16 skip=1 \<br>
| empty/empty --file=- --print-buffer<br>
<br>
---<br>
<br>
Note: the buffer times only relates to the middle server, not the original <br>
data generation. But in this case is good enough to show the difference.<br>
If 'dropold' is not used in the middle instance, then the last instance <br>
(doing --print-buffer) will be seen to lag further and further.<br>
<br>
<br>
Cheers,<br>
Håkan</div>
</span></font>
</body>
</html>