| ID |
Date |
Author |
Topic |
Subject |
Text |
 |
|
2052
|
11 Dec 2020 |
Frederik Wauters | Forum | history and variables confusion | 1. ok, so calling the same readout functions
from different equipments is just a bad idea,
my bad, no blame for Midas to write data |
|
|
2131
|
15 Mar 2021 |
Frederik Wauters | Forum | INT INT32 in experim.h | works!
> Ok, I added
|
|
|
2296
|
29 Oct 2021 |
Frederik Wauters | Bug Report | midas::odb::iterator + operator | I have 16 array odb key
{"FIR Energy", {
|
|
|
2297
|
29 Oct 2021 |
Frederik Wauters | Bug Report | midas::odb::iterator + operator | work around | ok, so retrieving as a std::array (as it was
defined) does not work
|
|
|
2310
|
26 Jan 2022 |
Frederik Wauters | Forum | .gz files | I adapted our analyzer to compile against
the manalyzer included in the midas repo.
|
|
|
2328
|
31 Jan 2022 |
Frederik Wauters | Forum | .gz files | > > I adapted our analyzer to compile against
the manalyzer included in the midas repo.
> > TMReadEvent: error: short read 0 instead |
|
|
2447
|
11 Nov 2022 |
Frederik Wauters | Bug Fix | O_CREAT in open in split.cxx | midas currently does not compile on linux
/usr/include/x86_64-linux-gnu/bits/fcntl2.h:50:24: |
|
|
2606
|
19 Sep 2023 |
Frederik Wauters | Bug Report | epics fe "Start Command" | The epics frontend overwrites the "start command"
odb after each start:
|
|
|
2608
|
24 Sep 2023 |
Frederik Wauters | Suggestion | scroll when browsing for a link | Another small user experience request:
When making a link in the odb (web interface) |
|
|
2671
|
15 Jan 2024 |
Frederik Wauters | Forum | dump history FILE files | We switched from the history files from MIDAS
to FILE, so we have *.dat files now (per
variable), instead of the old *.hst.
|
|
|
2716
|
18 Feb 2024 |
Frederik Wauters | Forum | dump history FILE files | > $ cat mhf_1697445335_20231016_run_transitions.dat
> event name: [Run transitions], time [1697445335]
> tag: tag: /DWORD 1 4 /timestamp
|
|
|
3059
|
19 Jun 2025 |
Frederik Wauters | Bug Report | add history variables | I have encounter this a few times
* Make a new history panel
* Use the web GUI to add history variables
|
|
|
3101
|
01 Oct 2025 |
Frederik Wauters | Forum | struct size mismatch of alarms | So I started our DAQ with an updated midas,
after ca. 6 months+.
|
|
|
3105
|
02 Oct 2025 |
Frederik Wauters | Forum | struct size mismatch of alarms | > Sorry to intervene there, but the FEs are
usually compiled against libmidas.a . Therefore
you have to compile midas, usually do a "make |
|
|
1279
|
26 Apr 2017 |
Francesco Renga | Forum | Problem with logger at run start | Dear experts,
we have a problem when trying to run
a MIDAS DAQ which worked in the past on the |
|
|
1283
|
26 Apr 2017 |
Francesco Renga | Forum | Problem with logger at run start | Dear Stefan,
thank you very much for your reply.
We could finally fix the problem by replacing |
|
|
1367
|
04 May 2018 |
Francesco Renga | Forum | ODB full | Dear expert,
I'm developing a frontend and I'm getting
this kind of error at each event:
|
|
|
1393
|
11 Sep 2018 |
Francesco Renga | Forum | Launching an executable script from the sequencer | Dear experts,
is there any way to launch
an executable script on the host computer |
|
|
1484
|
11 Mar 2019 |
Francesco Renga | Forum | Run length | Dear all,
I need to implement a DAQ sequence
where a short run (100 events, which takes |
|
|
1485
|
12 Mar 2019 |
Francesco Renga | Forum | Problem stopping every second run | Dear all,
I'm running a DAQ frontend and it
works well if one single run is
|
|