Back Midas Rome Roody Rootana
  Midas DAQ System, Page 64 of 144  Not logged in ELOG logo
ID Datedown Author Topic Subject Text Attachments
  1615   11 Jul 2019 Konstantin OlchanskiBug ReportHeader files missing when trying to compile rootana, roody and analyzer> > You can confirm that you are linking against
the correct ROOT by running cmake with VERBOSE=1
> > and examine the linker command line to
  
  1614   11 Jul 2019 Konstantin OlchanskiBug ReportFrontend 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
  
  1613   11 Jul 2019 Vinzenz BildsteinBug ReportFrontend killed at stop of run> > ... finding a current midas.log file

> On the "help" page, see "midas.log".
  
  1612   11 Jul 2019 Stefan RittBug ReportHeader files missing when trying to compile rootana, roody and analyzer> You can confirm that you are linking against
the correct ROOT by running cmake with VERBOSE=1
> and examine the linker command line to
  
  1611   10 Jul 2019 Konstantin OlchanskiBug ReportHeader files missing when trying to compile rootana, roody and analyzer>> [hh19285@it038146 ~]$ which root-config
> /software/root/v6.06.08/bin/root-config
> [hh19285@it038146 ~]$ root-config --cflags
  
  1610   10 Jul 2019 Konstantin OlchanskiBug ReportFrontend killed at stop of run> ... finding a current midas.log file

On the "help" page, see "midas.log".
  
  1609   10 Jul 2019 Stefan RittBug Reportmhttpd crashes when including nonexistent script in msequencerThe bug has been fixed. It was actually in
the mxml library. So you have to go to the
midas/mxml 
  
  1608   10 Jul 2019 Vinzenz BildsteinBug ReportFrontend killed at stop of run> > > > 
> > > > For SIGKILL, my gdb reports "Program
terminated with signal SIGKILL, Killed."
  
  1607   10 Jul 2019 HassanBug ReportHeader files missing when trying to compile rootana, roody and analyzerHi, we have now done a clean install of Root
and after some dynamic linking we have been
able to make Rootana and analyzer. However
  
  1606   09 Jul 2019 Stefan RittInfoLimitations of MSL> Yes, this has been the way to do it for
years...
  
  1605   08 Jul 2019 Vinzenz BildsteinBug ReportFrontend killed at stop of run> > > 
> > > For SIGKILL, my gdb reports "Program
terminated with signal SIGKILL, Killed."
  
  1604   08 Jul 2019 Konstantin OlchanskiBug ReportFrontend killed at stop of run> > 
> > For SIGKILL, my gdb reports "Program
terminated with signal SIGKILL, Killed."
  
  1603   08 Jul 2019 Vinzenz BildsteinBug ReportFrontend killed at stop of run> > > run the frontend inside gdb and post
the stack trace after the crash?
> > > 
  
  1602   08 Jul 2019 Konstantin OlchanskiBug ReportFrontend killed at stop of run> > run the frontend inside gdb and post the
stack trace after the crash?
> > 
  
  1601   08 Jul 2019 Vinzenz BildsteinBug ReportFrontend killed at stop of run> run the frontend inside gdb and post the
stack trace after the crash?
  
  1600   08 Jul 2019 Konstantin OlchanskiInfoLimitations of MSLHi, Stefan, on second thought, I agree, I
do not know of any scripting language implementation
(packaged as a library or not) that
  
  1599   08 Jul 2019 Konstantin OlchanskiInfoLimitations of MSL> Konstantin, would you mind resurrecting
and sharing the python code?
  
  1598   08 Jul 2019 Konstantin OlchanskiBug ReportFrontend 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
  
  1597   08 Jul 2019 Vinzenz BildsteinBug ReportFrontend killed at stop of runI wrote a c++ frontend to read data from CAEN
VX1730 digitizers which is used in
parallel with the GRIFFIN frontend to read
  
  1595   08 Jul 2019 Lukas GerritzenInfoLimitations of MSLThank you two!

Actually, both solutions would allow me to
  
ELOG V3.1.4-2e1708b5