| ID |
Date |
Author |
Topic |
Subject |
Text |
 |
|
1155
|
19 Jan 2016 |
Tom Stuttard | Suggestion | 64 bit bank type | > > I've seen that a similar question has
been asked in 2011 but I'll ask again in
|
|
|
846
|
14 Dec 2012 |
Vinzenz Bildstein | Suggestion | Midas + Elog with SSL | I've been trying to set up midas to create
an automatic elog entry at the end of
each run and I've run into a problem. I've |
|
|
848
|
17 Dec 2012 |
Vinzenz Bildstein | Suggestion | Midas + Elog with SSL | > > I've been trying to set up midas to create
an automatic elog entry at the end of
> > each run and I've run into a problem. |
|
|
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 |
|
|
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?
>
|
|
|
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?
> > >
|
|
|
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." |
|
|
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".
|
|
|
1680
|
08 Sep 2019 |
Vinzenz Bildstein | Bug Report | https redirect and ODB access | I'm not sure if these issues are related or
not, but I'm getting an error
message when I want to access the root of |
|
|
1728
|
21 Oct 2019 |
Vinzenz Bildstein | Forum | Data for key truncated | I keep on getting messages like this:
16:25:35 [fecaen,ERROR] [odb.c:4567:db_get_data,ERROR] |
|
|
859
|
11 Feb 2013 |
Wes Gohn | Forum | send_tcp error | I am getting a series of errors from MIDAS
that I do not understand, so I hope
someone can help me figure this out.
|
|
|
861
|
11 Feb 2013 |
Wes Gohn | Forum | send_tcp error | > > I am getting a series of errors from MIDAS
that I do not understand, so I hope
> > someone can help me figure this out.
|
|
|
865
|
19 Feb 2013 |
Wes Gohn | Forum | send_tcp error |
Thank you for the help. As it turns out, |
|
|
990
|
15 Apr 2014 |
Wes Gohn | Forum | C++11 error | I am having some trouble creating a frontend
that interacts with some libraries that use
C++11.
|
|
|
992
|
16 Apr 2014 |
Wes Gohn | Forum | C++11 error | > > I am having some trouble creating a frontend
that interacts with some libraries that use
C++11.
|
|
|
1048
|
17 Mar 2015 |
Wes Gohn | Forum | PosgresQL | For our MIDAS installation at Fermilab, it
is necessary that we be able to write to
a PosgresQL
|
|
|
1083
|
29 Jul 2015 |
Wes Gohn | Forum | error | SIGSEGV is a segmentation fault. Most often
it means some ODB parameter is out of bounds
or there is
|
|
|
1088
|
10 Aug 2015 |
Wes Gohn | Forum | bk_create change | After pulling the newest version of midas,
our compilation would fail on
bk_create, with the error:
|
|
|
1175
|
22 Apr 2016 |
Wes Gohn | Bug Report | Calling external script from sequencer | Can the MIDAS Sequencer call an external script?
It seems that it should be able to. I have
a simple
|
|