<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 Hans, dear H<font size="2"><span style="font-size:16pt">ċ</span></font>kan,</p>
<p><br>
</p>
<p>now the compilation was successful.</p>
<p><br>
</p>
<p></p>
<div>RIO4-MCAL-2 mbsdaq > make<br>
Could not figure out RFX1 firmware (8-xdigit number), skipping.<br>
TRIDI_FW=d374466d<br>
VULOM4_FW=d96ffc88<br>
RFX1_FW=<br>
CC build_cc_ppc-linux_4.2.2_debug/tests/test_ctrl/main.o<br>
LD build_cc_ppc-linux_4.2.2_debug/test_ctrl<br>
AR build_cc_ppc-linux_4.2.2_debug/./libnurdlib.a<br>
CC build_cc_ppc-linux_4.2.2_debug/tools/memtest.o<br>
LN bin/memtest<br>
LD build_cc_ppc-linux_4.2.2_debug/tools/memtest<br>
CC build_cc_ppc-linux_4.2.2_debug/ctrl/nurdctrl.o<br>
LN bin/nurdctrl<br>
LD build_cc_ppc-linux_4.2.2_debug/nurdctrl<br>
CC build_cc_ppc-linux_4.2.2_debug/tools/rwdump.o<br>
LN bin/rwdump<br>
LD build_cc_ppc-linux_4.2.2_debug/tools/rwdump<br>
CC build_cc_ppc-linux_4.2.2_debug/tools/wrslew.o<br>
LN bin/wrslew<br>
LD build_cc_ppc-linux_4.2.2_debug/tools/wrslew<br>
build_cc_ppc-linux_4.2.2_debug: Simon says: Alles wird gut ;o)</div>
<p></p>
<p><br>
</p>
<p>Side note:</p>
<p>'export VARIABLE_NAME=VARIABLE_VALUE' did not work on our RIO4. Instead <span>
'setenv VARIABLE_NAME VARIABLE_VALUE' needed to be used. Probably, this due to not using bash but tcsh (for whatever reason).</span></p>
<p><span><br>
</span></p>
<p><span>Now I updated the NURDLIB, right? To check if it actually works with the hardware present, I would now need to run the DAQ and have a look at the output data.</span></p>
<p><span><br>
</span></p>
<p><span>To run the DAQ, Bastian provided us with a set of scripts. The main one looks like this:</span></p>
<p><span><br>
</span></p>
<p><span></p>
<div style="color:#cccccc; background-color:#1f1f1f; font-family:Consolas,'Courier New',monospace; font-weight:normal; font-size:14px; line-height:19px; white-space:pre">
<div><span style="color:#dcdcaa">source</span><span style="color:#cccccc"> </span>
<span style="color:#ce9178">../env/env.sh</span></div>
<br>
<div><span style="color:#dcdcaa">./trloii_setup.sh</span></div>
<br>
<div><span style="color:#6a9955"># gdb --args \</span></div>
<div><span style="color:#dcdcaa">.</span><span style="color:#cccccc">./r3bfuser/build_cc_ppc-linux_4.2.2_debug_drasi/m_read_meb.drasi
</span><span style="color:#d7ba7d">\</span></div>
<div><span style="color:#cccccc"> </span><span style="color:#569cd6">--label=MCAL2</span><span style="color:#cccccc">
</span><span style="color:#d7ba7d">\</span></div>
<div><span style="color:#cccccc"> </span><span style="color:#569cd6">--triva=master,fctime=10,ctime=50</span><span style="color:#cccccc">
</span><span style="color:#d7ba7d">\</span></div>
<div><span style="color:#cccccc"> </span><span style="color:#569cd6">--log-no-rate-limit</span><span style="color:#cccccc">
</span><span style="color:#d7ba7d">\</span></div>
<div><span style="color:#cccccc"> </span><span style="color:#569cd6">--server=drasi,dest=lyserv</span><span style="color:#cccccc">
</span><span style="color:#d7ba7d">\</span></div>
<div><span style="color:#cccccc"> </span><span style="color:#569cd6">--buf=size=400Mi</span><span style="color:#cccccc">
</span><span style="color:#d7ba7d">\</span></div>
<div><span style="color:#cccccc"> </span><span style="color:#569cd6">--max-ev-size=0x1000000</span><span style="color:#cccccc">
</span><span style="color:#d7ba7d">\</span></div>
<div><span style="color:#cccccc"> </span><span style="color:#569cd6">--subev=crate=1,type=20,subtype=2,control=9,procid=1</span><span style="color:#cccccc">
</span><span style="color:#d7ba7d">\</span></div>
<div><span style="color:#cccccc"> </span><span style="color:#569cd6">--eb=lyserv</span><span style="color:#cccccc">
</span><span style="color:#d7ba7d">\</span></div>
<div><span style="color:#cccccc"> </span><span style="color:#ce9178">"</span><span style="color:#9cdcfe">$@</span><span style="color:#ce9178">"</span></div>
<br>
<br>
<br>
</div>
<br>
</span>
<p></p>
<p><span>Will DRASI automatically work with the new NURDLIB or do I need to compile it again?<br>
</span></p>
<p><span><br>
</span></p>
<p><span>The output stream of the data produced by the DAQ is probably set up with this script:<br>
</span></p>
<p><span><br>
</span></p>
<p></p>
<div style="color:#cccccc; background-color:#1f1f1f; font-family:Consolas,'Courier New',monospace; font-weight:normal; font-size:14px; line-height:19px; white-space:pre">
<div><span style="color:#6a9955">#!/bin/bash</span></div>
<div><span style="color:#c586c0">while</span><span style="color:#cccccc"> </span>
<span style="color:#dcdcaa">:</span></div>
<div><span style="color:#c586c0">do</span></div>
<div><span style="color:#d4d4d4">~</span><span style="color:#cccccc">/mbsrun/rio4/mcalstruck/ucesb/empty/empty \</span></div>
<div><span style="color:#cccccc"> </span><span style="color:#dcdcaa">stream://localhost</span><span style="color:#cccccc">
</span><span style="color:#d7ba7d">\</span></div>
<div><span style="color:#cccccc"> </span><span style="color:#569cd6">--server=stream:8001,bufsize=10Mi,flush=1,dataport:7001</span></div>
<div><span style="color:#dcdcaa">sleep</span><span style="color:#cccccc"> </span>
<span style="color:#b5cea8">5</span></div>
<div><span style="color:#c586c0">done</span><span style="color:#cccccc"> </span></div>
</div>
<br>
<p></p>
<p>Will also UCESB automatically adapt to the new NURDLIB or do I need to compile it again?</p>
<p>(I am a bit puzzled by the fact that it is '<span>~/mbsrun/rio4/mcalstruck/ucesb/...' and not '<span>~/mbsrun/rio4/2023_mcalstruck/ucesb/...'. This seems to be inconsistent.)</span></span></p>
<p><br>
</p>
<p>Moreover, I found the following environment variables that (to my understanding) tell the various parts of the DAQ software where it can find some necessary stuff:</p>
<p><br>
</p>
<p></p>
<div>TRLOII_PATH=/LynxOS/mbsusr/mbsdaq/mbsrun/rio4/2023_mcalstruck/trloii<br>
TRIDI_CTRL=/LynxOS/mbsusr/mbsdaq/mbsrun/rio4/2023_mcalstruck/trloii/trloctrl/fw_d374466d_tridi/bin_ppc-linux_4.2.2/tridi_ctrl<br>
TRIMI_CTRL=/LynxOS/mbsusr/mbsdaq/mbsrun/rio4/2023_mcalstruck/trloii/trimictrl/bin_ppc-linux_4.2.2/trimictrl<br>
TRLOII_FLASH=/LynxOS/mbsusr/mbsdaq/mbsrun/rio4/2023_mcalstruck/trloii/flash/bin_ppc-linux_4.2.2/vulomflash<br>
VULOM4_CTRL=/LynxOS/mbsusr/mbsdaq/mbsrun/rio4/2023_mcalstruck/trloii/trloctrl/fw_d96ffc88_trlo/bin_ppc-linux_4.2.2/trlo_ctrl</div>
<div>EXP_PATH=/LynxOS/mbsusr/mbsdaq/mbsrun/rio4/2023_mcalstruck<br>
HTOOLS_PATH=/LynxOS/mbsusr/mbsdaq/mbsrun/rio4/2023_mcalstruck/htools</div>
<p></p>
<p><br>
</p>
<p>As I copied the complete folder structure of <span>'2023_mcalstruck' to <span>
'2024_mcalstruck', to be consistent I will redefine all this variables to point to the new folder.</span></span></p>
<p><span><span><br>
</span></span></p>
<p><span><span><br>
</span></span></p>
<p><span><span><br>
</span></span></p>
<p><span><span>Best greetings from Jena</span></span></p>
<p><span><span>Günter<br>
</span></span></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 Hans Toshihide Törnqvist <hans.tornqvist@chalmers.se><br>
<b>Gesendet:</b> Montag, 8. Januar 2024 16:20:24<br>
<b>An:</b> Discuss use of Nurdlib, TRLO II, drasi and UCESB.; Hċkan T Johansson<br>
<b>Betreff:</b> Re: [subexp-daq] NURDLIB: - how to check which version is installed and how to update to the most recent version</font>
<div> </div>
</div>
</div>
<font size="2"><span style="font-size:10pt;">
<div class="PlainText">Dear Günter,<br>
<br>
I was on a late lunch break.<br>
<br>
That should be the only env-var. I'm adding the explanation to my docu-todo.<br>
<br>
Cheers,<br>
<br>
Hans<br>
<br>
On 2024-01-08 15:57, Hċkan T Johansson wrote:<br>
> <br>
> Dear Günter,<br>
> <br>
> not a definate answer, but looking around for getend in the sources, I <br>
> did not find further suspicious environment variables.<br>
> <br>
> You could try<br>
> <br>
> end | grep 2023_mcalstruck<br>
> <br>
> or with some other significant part of the path to see if there are any <br>
> other.<br>
> <br>
> Cheers,<br>
> Hċkan<br>
> <br>
> <br>
> On Mon, 8 Jan 2024, Weber, Guenter Dr. wrote:<br>
> <br>
>><br>
>> Dear Hans,<br>
>><br>
>><br>
>> thank you very much!<br>
>><br>
>><br>
>> It now dies at a later stage of the compilation process.<br>
>><br>
>><br>
>> ...<br>
>><br>
>> [tests/caen_v792.c:73: IPEDConversion]<br>
>> [tests/caen_v820.c:32: DefaultConfig]<br>
>> 2024-02-08,16:59:58:INFO: Will try default <br>
>> cfgpath='/LynxOS/mbsusr/mbsdaq/mbsrun/rio4/2023_mcalstruck/nurdlib/cfg/default<br>
>> ', can be set with NURDLIB_DEF_PATH. [config/config.c:181]<br>
>> 2024-02-08,16:59:58:INFO: Opened './tests/caen_v820_empty.cfg' {<br>
>> [config/parser.c:287]<br>
>> 2024-02-08,16:59:58:INFO: <br>
>> .Opened'/LynxOS/mbsusr/mbsdaq/mbsrun/rio4/2023_mcalstruck/nurdlib/cfg/default/caen<br>
>> _v820.cfg' { [config/parser.c:287]<br>
>> 2024-02-08,16:59:58:INFO: <br>
>> .Closed'/LynxOS/mbsusr/mbsdaq/mbsrun/rio4/2023_mcalstruck/nurdlib/cfg/default/caen<br>
>> _v820.cfg' } [config/parser.c:299]<br>
>> 2024-02-08,16:59:58:INFO: <br>
>> .Opened'/LynxOS/mbsusr/mbsdaq/mbsrun/rio4/2023_mcalstruck/nurdlib/cfg/default/modu<br>
>> le_log_level.cfg' { [config/parser.c:287]<br>
>> 2024-02-08,16:59:58:INFO: <br>
>> .Closed'/LynxOS/mbsusr/mbsdaq/mbsrun/rio4/2023_mcalstruck/nurdlib/cfg/default/modu<br>
>> le_log_level.cfg' } [config/parser.c:299]<br>
>> 2024-02-08,16:59:58:INFO: Closed './tests/caen_v820_empty.cfg' }<br>
>> [config/parser.c:299]<br>
>> 2024-02-08,16:59:58:ERRR: Could not find keyword config 'paux'.<br>
>> [config/config.c:711]<br>
>> 2024-02-08,16:59:58:ERRR: Calling abort()... [config/config.c:711]<br>
>> make: *** [build_cc_ppc-linux_4.2.2_debug/test_ok] Error 1<br>
>><br>
>> The problem is that the environment variable NURDLIB_DEF_PATH is still <br>
>> set<br>
>> to the old directory ('2023_mcalstruck' instead of '2024_mcalstruck', <br>
>> which<br>
>> I created today). Of course, I can change this now. But is there a <br>
>> list of<br>
>> all the environment variables that need to be updated? Or<br>
>> is NURDLIB_DEF_PATH the only one?<br>
>><br>
>><br>
>><br>
>> Best greetings<br>
>><br>
>> Günter<br>
> <br>
-- <br>
subexp-daq mailing list<br>
subexp-daq@lists.chalmers.se<br>
<a href="https://lists.chalmers.se/mailman/listinfo/subexp-daq">https://lists.chalmers.se/mailman/listinfo/subexp-daq</a><br>
</div>
</span></font>
</body>
</html>