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

[Håkan T Johansson]

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

> 
> 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.

True, for reading the data after the DAQ as such.

> 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

Yes.  Well outside upexps I hope.  ;)

> 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.

You are correct.

Only distinction would that that ucesb / upexps are only involved to 
either read .lmd files, or to read live data streams (which is also on lmd 
format) from the DAQ.

--

With the git references above, we can hopefully try to figure out how deep 
into the other parts of upexps your directory has dependencies.

But - as long as the data format has not changed - and the intention with 
the update to nurdlib etc was to not change any of those - the current 
unpacker specification and mapping should still work.  In fact - if it 
does not - then we do not want to fix the unpacking stages, but understand 
why the DAQ delivers different data.

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

Cheers,
Håkan