[subexp-daq] How to start a DAQ system after NURDLIB, TRLOII, DRASI, etc. were updated

Tue Jan 16 12:13:52 CET 2024

Dear Hakan,

thank you or your reply. Now I am bit lost because I thought that UPEXPS is a central piece where important things happen.

Anyway, here is what GIT tells me about UPEXPS:

mbsdaq at atpnbg011:~/mbsrun/rio4/2024_mcalstruck/upexps$ git log
commit 47db26b7743bf2676ebc2aa0a69e8cfae0e74ef4 (HEAD -> master)
Author: Bastian Loeher <b.loeher at gsi.de>
Date:   Mon Mar 15 17:26:29 2021 +0100

Therein is the folder MCAL_2019:

mbsdaq at atpnbg011:~/mbsrun/rio4/2024_mcalstruck/upexps/mcal_2019$ ls -l
insgesamt 23052
-rw-r--r-- 1 mbsdaq users      137 Jan 12 13:41 control.hh
drwxr-sr-x 4 mbsdaq users     4096 Jan 12 13:37 gen_mcal
-rw-r--r-- 1 mbsdaq users      233 Jan 12 13:37 Makefile
-rw-r--r-- 1 mbsdaq users      102 Jan 12 13:41 makefile_additional.inc
-rw-r--r-- 1 mbsdaq users     1574 Jan 12 13:37 mapping.h
-rwxr-xr-x 1 mbsdaq users 12503880 Jan 12 13:41 mcal
-rw-r--r-- 1 mbsdaq users    24005 Jan 12 13:41 mcal.dep
-rw-r--r-- 1 mbsdaq users     1571 Jan 12 13:41 mcal.spec
-rw-r--r-- 1 mbsdaq users     2777 Jan 12 13:41 mcal_user.cc
-rwxr-xr-x 1 mbsdaq users 11020872 Jan 12 13:41 mcal.working
drwxr-sr-x 2 mbsdaq users     4096 Jan 12 13:41 mc_gen_mcal
drwxr-sr-x 2 mbsdaq users     4096 Jan 12 13:41 obj_mcal
-rw-r--r-- 1 mbsdaq users     6545 Jan 12 13:41 sis3316_mapping_macros.h
-rw-r--r-- 1 mbsdaq users     5082 Jan 12 13:41 vme_struck_sis3316.spec

And my impression was that these files are somehow central to reading out our DAQ system.

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):

-rw-r--r-- 1 mbsdaq users        4883 Jan 12 13:44 main.cfg

-rw-r--r-- 1 mbsdaq users         194 Jan 12 13:42 r3bfuser.cfg

-rw-r--r-- 1 mbsdaq users        3065 Jan 12 13:42 vulom.trlo

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.

After lunch, I will give it a try to simply start the DAQ.

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: Dienstag, 16. Januar 2024 11:36:03
An: Discuss use of Nurdlib, TRLO II, drasi and UCESB.
Betreff: Re: [subexp-daq] How to start a DAQ system after NURDLIB, TRLOII, DRASI, etc. were updated

Dear Günter,

On Tue, 16 Jan 2024, Weber, Guenter Dr. wrote:

>
> Dear Hans, dear Håkan,
>
>
> would it be possible to modify the Makefiles in such a way that basics
> checks (e.g. NURDLIB_DEF_PATH and TRLOII_PATH are set to a path that
> exsists) are done right in the beginning? Also maybe the outcomes logged in
> files like trloii.h.log could be more clearly communicated on the command
> line. This would have helped a great deal.

Agree.  Something(s) needs to be done.  Fail early is a good strategy!

One could have some 'make checkconfig' target which could try to check
especially externally set variables that can affect the compile flow in a
tool.  And have it run early always, especially if it is quiet by
default.  And some VERBOSE=1 flag that would print useful info (as well as
make that 'make checkconfig' tell more what it is doing.  Since there
already is the QUIET= option that starts to print everything which is
done, verbose might not be the rigth name.  Not thinking of printing
everything here, which is just unreadable, but some actually useful debug
info.  PRETTY_VERBOSE=1 ? :-)

(drasi and trloii has 'make showconfig' which tells what internal
configurations it has come up with internally, but that is not what we are
after here.)

> I now also compiled UCESB (on PC).
>
>
> What now?

Try to run the DAQ. ;)

> There is the folder UPEXPS, in which (to my limited understanding) it is
> defined what the DAQ actually does with the various modules. Unfortunately,
> I have no idea how exactly this works. Do I have to recompile here after
> TRLOII, DRASI, NURDLIB, etc. were replaced by new versions?

The upexps presumably if 'just' unpacking, i.e. not involved in the DAQ as
such, only in the data unpacking.

That should only depend on ucesb, not on the other DAQ tools, and the DAQ
should not depend on it.  Except if your normal file writing goes via
ucesb, which I hope not...

upexps is a repository which ... needs help (it is not being properly
maintained).  Could you tell which commit you are using in that?

> Thank you very much!

Thank you for all the feedback!

Cheers,
Håkan
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.chalmers.se/pipermail/subexp-daq/attachments/20240116/da593130/attachment.html>