| ID |
Date |
Author |
Topic |
Subject |
Text |
 |
|
1504
|
21 Mar 2019 |
Konstantin Olchanski | Info | Gyrations of custom pages and ODB /Custom/Path | > Before the days of javascript and ajax and
web 2.0, MIDAS introduced "custom pages"
for
|
|
|
435
|
18 Feb 2008 |
Exaos Lee | Bug Report | Great! But I failed to run it. :( | I encountered the error message as the following:
[CODE]
Traceback (most recent call last):
|
|
|
1574
|
27 Jun 2019 |
Hassan | Bug Report | Getting an error when trying to compile a frontend file | When we run the following commands on the
hostname(DAQ machine) and the remote
frontend(Rpi):
|
|
|
1576
|
27 Jun 2019 |
Konstantin Olchanski | Bug Report | Getting an error when trying to compile a frontend file | If the latest midas does not work, try the
previous release versions. "git tags" and
"git branch -
|
|
|
1579
|
27 Jun 2019 |
Stefan Ritt | Bug Report | Getting an error when trying to compile a frontend file | Note that the example experiment compiles
a simple example frontend and a root-based
analyzer. If you don't have
|
|
|
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? |
|
|
183
|
15 Dec 2004 |
Stefan Ritt | 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? |
|
|
1183
|
06 Jul 2016 |
Zhe Wang | Suggestion | Frontend crush on high event rate | Dear friends,
We have some questions on using midas.
|
|
|
1184
|
09 Jul 2016 |
Zhe Wang | Suggestion | Frontend crush on high event rate | Dear friends,
I may add a little more information.
|
|