<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 <font face="Calibri,Helvetica,sans-serif" size="4" color="black" style="font-family:Calibri,Helvetica,sans-serif,serif,"EmojiFont"">
<span id="x_x_divtagdefaultwrapper" style="font-size:14pt">Håkan</span></font>,</p>
<p><br>
</p>
<p>next thing is that we would like to teach the HBOOK part to work with 64-bit uints (to not have the timestamp as two 32-bit words). We noticed there is a pearl script: make_external_struct_sender.pl</p>
<p>Is this an integral part that we would need to touch?</p>
<p><br>
</p>
<p><br>
</p>
<p><br>
</p>
<p>Best greetings</p>
<p>Günter<br>
</p>
<br>
</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> Mittwoch, 10. April 2024 12:57:19<br>
<b>An:</b> Discuss use of Nurdlib, TRLO II, drasi and UCESB.<br>
<b>Betreff:</b> Re: [subexp-daq] Question on UCESB</font>
<div> </div>
</div>
</div>
<font size="2"><span style="font-size:10pt;">
<div class="PlainText"><br>
On Wed, 10 Apr 2024, Weber, Guenter Dr. wrote:<br>
<br>
> This is really great. The only remaining question for now is if there is a<br>
> way to get the content of an array (in the above case the counts in the 16<br>
> scaler channels) without the additional information on the scaler channel<br>
> numbers? In case of the SIS3316 digitizers a single pulse trace can have a<br>
> length of tens of thousands of samples. Somehow I do not like the idea that<br>
> without necessity we always transfer an additional array with just the<br>
> numbers from 1 to n.<br>
> <br>
> Bottom line: is there an easy way to get rid of the '..._nI' part of the<br>
> array object in the JSON output?<br>
<br>
Nice that it worked.<br>
<br>
I think the only 'easy' way to avoid the '..._nI' entries is to not use <br>
zero-suppression for the array.<br>
<br>
However, then it would/should appear fully in all events. Since the <br>
scaler module might not always be read, it would then contain the value 0 <br>
when nothing filled the array for that event. That may (or not) be more <br>
confusing.<br>
<br>
Cheers,<br>
Håkan</div>
</span></font>
</body>
</html>