<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 Hakan,</p>
<p><br>
</p>
<p>thank you or your reply. Now I am bit lost because I thought that UPEXPS is a central piece where important things happen. </p>
<p><br>
</p>
<p>Anyway, here is what GIT tells me about UPEXPS:</p>
<p></p>
<div><span style="font-size:8pt">mbsdaq@atpnbg011:~/mbsrun/rio4/2024_mcalstruck/upexps$ git log</span><br>
<span style="font-size:8pt">commit 47db26b7743bf2676ebc2aa0a69e8cfae0e74ef4 (HEAD -> master)</span><br>
<span style="font-size:8pt">Author: Bastian Loeher <b.loeher@gsi.de></span><br>
<span style="font-size:8pt">Date: Mon Mar 15 17:26:29 2021 +0100</span></div>
<br>
<p></p>
<p>Therein is the folder MCAL_2019:</p>
<p></p>
<div><span style="font-size:8pt">mbsdaq@atpnbg011:~/mbsrun/rio4/2024_mcalstruck/upexps/mcal_2019$ ls -l</span><br>
<span style="font-size:8pt">insgesamt 23052</span><br>
<span style="font-size:8pt">-rw-r--r-- 1 mbsdaq users 137 Jan 12 13:41 control.hh</span><br>
<span style="font-size:8pt">drwxr-sr-x 4 mbsdaq users 4096 Jan 12 13:37 gen_mcal</span><br>
<span style="font-size:8pt">-rw-r--r-- 1 mbsdaq users 233 Jan 12 13:37 Makefile</span><br>
<span style="font-size:8pt">-rw-r--r-- 1 mbsdaq users 102 Jan 12 13:41 makefile_additional.inc</span><br>
<span style="font-size:8pt">-rw-r--r-- 1 mbsdaq users 1574 Jan 12 13:37 mapping.h</span><br>
<span style="font-size:8pt">-rwxr-xr-x 1 mbsdaq users 12503880 Jan 12 13:41 mcal</span><br>
<span style="font-size:8pt">-rw-r--r-- 1 mbsdaq users 24005 Jan 12 13:41 mcal.dep</span><br>
<span style="font-size:8pt">-rw-r--r-- 1 mbsdaq users 1571 Jan 12 13:41 mcal.spec</span><br>
<span style="font-size:8pt">-rw-r--r-- 1 mbsdaq users 2777 Jan 12 13:41 mcal_user.cc</span><br>
<span style="font-size:8pt">-rwxr-xr-x 1 mbsdaq users 11020872 Jan 12 13:41 mcal.working</span><br>
<span style="font-size:8pt">drwxr-sr-x 2 mbsdaq users 4096 Jan 12 13:41 mc_gen_mcal</span><br>
<span style="font-size:8pt">drwxr-sr-x 2 mbsdaq users 4096 Jan 12 13:41 obj_mcal</span><br>
<span style="font-size:8pt">-rw-r--r-- 1 mbsdaq users 6545 Jan 12 13:41 sis3316_mapping_macros.h</span><br>
<span style="font-size:8pt">-rw-r--r-- 1 mbsdaq users 5082 Jan 12 13:41 vme_struck_sis3316.spec</span></div>
<br>
<p></p>
<p>And my impression was that these files are somehow central to reading out our DAQ system.</p>
<p><br>
</p>
<p>My understanding is that for initializing and readout of the modules by the DAQ software, the following configuration files are used (they are in a different directory):</p>
<p><span style="font-size:8pt">-rw-r--r-- 1 mbsdaq users 4883 Jan 12 13:44 main.cfg</span><br>
</p>
<p><span style="font-size:8pt">-rw-r--r-- 1 mbsdaq users 194 Jan 12 13:42 r3bfuser.cfg</span></p>
<p><span style="font-size:8pt">-rw-r--r-- 1 mbsdaq users 3065 Jan 12 13:42 vulom.trlo</span><br>
</p>
<p><br>
</p>
<p>But for telling UCESB what to find in the the LMD stream coming from the RIO (which is a result of these configuration files), somehow a 'mapping' is necessary. And this I associated with UPEXPS. But maybe my understanding was wrong, if UPEXPS is not used
by you guys.</p>
<p><br>
</p>
<p>After lunch, I will give it a try to simply start the DAQ.</p>
<p><br>
</p>
<p><br>
</p>
<p><br>
</p>
<p><br>
</p>
<p>Best greetings</p>
<p>Günter<br>
</p>
<p><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> Dienstag, 16. Januar 2024 11:36:03<br>
<b>An:</b> Discuss use of Nurdlib, TRLO II, drasi and UCESB.<br>
<b>Betreff:</b> Re: [subexp-daq] How to start a DAQ system after NURDLIB, TRLOII, DRASI, etc. were updated</font>
<div> </div>
</div>
</div>
<font size="2"><span style="font-size:10pt;">
<div class="PlainText"><br>
Dear Günter,<br>
<br>
On Tue, 16 Jan 2024, Weber, Guenter Dr. wrote:<br>
<br>
> <br>
> Dear Hans, dear Håkan,<br>
> <br>
> <br>
> would it be possible to modify the Makefiles in such a way that basics<br>
> checks (e.g. NURDLIB_DEF_PATH and TRLOII_PATH are set to a path that<br>
> exsists) are done right in the beginning? Also maybe the outcomes logged in<br>
> files like trloii.h.log could be more clearly communicated on the command<br>
> line. This would have helped a great deal.<br>
<br>
Agree. Something(s) needs to be done. Fail early is a good strategy!<br>
<br>
One could have some 'make checkconfig' target which could try to check <br>
especially externally set variables that can affect the compile flow in a <br>
tool. And have it run early always, especially if it is quiet by <br>
default. And some VERBOSE=1 flag that would print useful info (as well as <br>
make that 'make checkconfig' tell more what it is doing. Since there <br>
already is the QUIET= option that starts to print everything which is <br>
done, verbose might not be the rigth name. Not thinking of printing <br>
everything here, which is just unreadable, but some actually useful debug <br>
info. PRETTY_VERBOSE=1 ? :-)<br>
<br>
(drasi and trloii has 'make showconfig' which tells what internal <br>
configurations it has come up with internally, but that is not what we are <br>
after here.)<br>
<br>
> I now also compiled UCESB (on PC).<br>
> <br>
> <br>
> What now?<br>
<br>
Try to run the DAQ. ;)<br>
<br>
> There is the folder UPEXPS, in which (to my limited understanding) it is<br>
> defined what the DAQ actually does with the various modules. Unfortunately,<br>
> I have no idea how exactly this works. Do I have to recompile here after<br>
> TRLOII, DRASI, NURDLIB, etc. were replaced by new versions?<br>
<br>
The upexps presumably if 'just' unpacking, i.e. not involved in the DAQ as <br>
such, only in the data unpacking.<br>
<br>
That should only depend on ucesb, not on the other DAQ tools, and the DAQ <br>
should not depend on it. Except if your normal file writing goes via <br>
ucesb, which I hope not...<br>
<br>
upexps is a repository which ... needs help (it is not being properly <br>
maintained). Could you tell which commit you are using in that?<br>
<br>
> Thank you very much!<br>
<br>
Thank you for all the feedback!<br>
<br>
Cheers,<br>
Håkan</div>
</span></font>
</body>
</html>