| ID |
Date |
Author |
Topic |
Subject |
Text |
 |
|
3074
|
17 Sep 2025 |
Mark Grimes | Suggestion | Get manalyzer to configure midas::odb when running offline | Hi,
Lots of users like the midas::odb interface
for reading from the ODB in manalyzers. It |
|
|
3075
|
17 Sep 2025 |
Konstantin Olchanski | Suggestion | Get manalyzer to configure midas::odb when running offline | > Lots of users like the midas::odb interface
for reading from the ODB in manalyzers.
> +#include "odbxx.h"
|
|
|
3077
|
18 Sep 2025 |
Mark Grimes | Suggestion | Get manalyzer to configure midas::odb when running offline | > ....Before commit of this patch, can you
confirm the RunInfo destructor
> deletes this ODB stuff from odbxx? manalyzer |
|
|
3078
|
18 Sep 2025 |
Stefan Ritt | Suggestion | Get manalyzer to configure midas::odb when running offline | > > Of course with this patch extending manalyzer
to process two or more runs at the same time
becomes impossible.
|
|
|
3057
|
11 Jun 2025 |
Stefan Ritt | Info | Frontend write cache size | We had issues with the frontend write cache
size and the way it was implemented in the
frontend
|
|
|
2874
|
11 Oct 2024 |
Denis Calvet | Bug Report | Frontend name must differ from others by more than the last three characters | Hi,
I have developed two Midas front-end programs
for different hardware. The frontend_name |
|
|
2875
|
11 Oct 2024 |
Stefan Ritt | Bug Report | Frontend name must differ from others by more than the last three characters | Hi Denis,
indeed a bug. Will fix it next week.
|
|
|
2878
|
18 Oct 2024 |
Stefan Ritt | Bug Report | Frontend name must differ from others by more than the last three characters | Fixed and committed.
Best,
|
|
|
1597
|
08 Jul 2019 |
Vinzenz Bildstein | Bug Report | Frontend killed at stop of run | I wrote a c++ frontend to read data from CAEN
VX1730 digitizers which is used in
parallel with the GRIFFIN frontend to read |
|
|
1598
|
08 Jul 2019 |
Konstantin Olchanski | Bug Report | Frontend killed at stop of run | > After a long overnight run to check that
the frontend runs smoothly for a longer
> time, I stopped the run and the frontend |
|
|
1601
|
08 Jul 2019 |
Vinzenz Bildstein | Bug Report | Frontend killed at stop of run | > run the frontend inside gdb and post the
stack trace after the crash?
>
|
|
|
1602
|
08 Jul 2019 |
Konstantin Olchanski | Bug Report | Frontend killed at stop of run | > > run the frontend inside gdb and post the
stack trace after the crash?
> >
|
|
|
1603
|
08 Jul 2019 |
Vinzenz Bildstein | Bug Report | Frontend killed at stop of run | > > > run the frontend inside gdb and post
the stack trace after the crash?
> > >
|
|
|
1604
|
08 Jul 2019 |
Konstantin Olchanski | Bug Report | Frontend killed at stop of run | > >
> > For SIGKILL, my gdb reports "Program
terminated with signal SIGKILL, Killed." |
|
|
1605
|
08 Jul 2019 |
Vinzenz Bildstein | Bug Report | Frontend killed at stop of run | > > >
> > > For SIGKILL, my gdb reports "Program
terminated with signal SIGKILL, Killed." |
|
|
1608
|
10 Jul 2019 |
Vinzenz Bildstein | Bug Report | Frontend killed at stop of run | > > > >
> > > > For SIGKILL, my gdb reports "Program
terminated with signal SIGKILL, Killed." |
|
|
1610
|
10 Jul 2019 |
Konstantin Olchanski | Bug Report | Frontend killed at stop of run | > ... finding a current midas.log file
On the "help" page, see "midas.log".
|
|
|
1613
|
11 Jul 2019 |
Vinzenz Bildstein | Bug Report | Frontend killed at stop of run | > > ... finding a current midas.log file
>
> On the "help" page, see "midas.log".
|
|
|
1614
|
11 Jul 2019 |
Konstantin Olchanski | Bug Report | Frontend killed at stop of run | > Wed Jul 10 06:23:58 2019 [mhttpd,ERROR]
[system.c:4580:ss_recv_net_command,ERROR]
timeout receiving network command header
|
|
|
181
|
14 Dec 2004 |
Jan Wouters | Forum | Frontend index | What is the api call to determine the index
of the frontend when specifying the
-i parameter during execution of the frontend? |
|