| ID |
Date |
Author |
Topic |
Subject |
Text |
 |
|
1566
|
24 Jun 2019 |
Stefan Ritt | Bug Report | ERROR INSTALLING 32BIT MIDAS LIBRARIES ON 64BIT HOST MACHINE | Why don't your try the (yet undocumented)
new installation procedure:
|
|
|
1568
|
24 Jun 2019 |
Stefan Ritt | Bug Report | ERROR INSTALLING 32BIT MIDAS LIBRARIES ON 64BIT HOST MACHINE | Update: "make" instead of "make linux32" should
also work. I believe the "linux32" target
came
|
|
|
1569
|
25 Jun 2019 |
Konstantin Olchanski | Bug Report | ERROR INSTALLING 32BIT MIDAS LIBRARIES ON 64BIT HOST MACHINE | Yikes, the error is in the CRC library. The
assembly-optimized crc32c function fails
to build, and the
|
|
|
1571
|
26 Jun 2019 |
Hassan | Bug Report | ERROR INSTALLING 32BIT MIDAS LIBRARIES ON 64BIT HOST MACHINE | Thanks for your advice. We now have Midas
installed on both our machines (remote machine-Rpi
&
|
|
|
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 -
|
|
|
1577
|
27 Jun 2019 |
Konstantin Olchanski | Bug Report | make linux32 bombs on el7 in crc32c.c, ERROR INSTALLING 32BIT MIDAS LIBRARIES ON 64BIT HOST MACHINE | Reproduced on el7 (CentOS7). Same thing works
on el6 (SL6).
|
|
|
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
|
|
|
1580
|
28 Jun 2019 |
Konstantin Olchanski | Bug Report | make linux32 bombs on el7 in crc32c.c, ERROR INSTALLING 32BIT MIDAS LIBRARIES ON 64BIT HOST MACHINE | > Reproduced on el7 (CentOS7). Same thing
works on el6 (SL6).
|
|
|
1581
|
28 Jun 2019 |
Thorsten Lux | Bug Report | Status page reloads every second | Hello,
We observed a strange behavior, from our |
|
|
1582
|
28 Jun 2019 |
Konstantin Olchanski | Bug Report | Status page reloads every second | > We observed a strange behavior, from our
point of view:
> ... the Midas status page started to reload/refresh |
|
|
1583
|
29 Jun 2019 |
Thorsten Lux | Bug Report | Status page reloads every second |
I am sorry, yesterday evening I must have
been a bit tired after a long day with a |
|
|
1587
|
03 Jul 2019 |
Lukas Gerritzen | Bug Report | mhttpd crashes when including nonexistent script in msequencer | Hi,
the subject line describes the project already
Suppose you have a file foo.msl. Somewhere |
|
|
1591
|
05 Jul 2019 |
Hassan | Bug Report | Header files missing when trying to compile rootana, roody and analyzer | First of all thank you for all the assistance
provided so far, especially making
changes to the code in CMakeList file previously |
|
|
1592
|
05 Jul 2019 |
Konstantin Olchanski | Bug Report | Header files missing when trying to compile rootana, roody and analyzer | > /home/hh19285/packages/rootana/include/TRootanaEventLoop.hxx:24:25:
fatal error:
> THttpServer.h: No such file or directory
|
|
|
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?
> > >
|
|