| ID |
Date |
Author |
Topic |
Subject |
Text |
 |
|
1687
|
16 Sep 2019 |
Konstantin Olchanski | Info | New history plot facility | > I see currently quite often is the error
hs_read_arraybuffer (see the
attachement).
|
|
|
1688
|
16 Sep 2019 |
Konstantin Olchanski | Info | New history plot facility | > During my visit at TRIUMF we rewrote the
history plotting functionality of midas.
|
|
|
1690
|
16 Sep 2019 |
Stefan Ritt | Info | New history plot facility | > Also the new system is still incomplete,
i.e. there is no trivial way to save a history
plot into a file:
|
|
|
1694
|
17 Sep 2019 |
Andreas Suter | Info | New history plot facility | > On the mhttpd side, please capture the stack
trace from the crash: enable
> core dumps (ODB "/experiment/enable core |
|
|
1695
|
17 Sep 2019 |
Konstantin Olchanski | Info | New history plot facility | > > On the mhttpd side, please capture the
stack trace from the crash
>
|
|
|
1727
|
18 Oct 2019 |
Joseph McKenna | Info | sysmon: New system monitor and performance logging frontend added to MIDAS |
I have written a system monitor tool for |
|
|
1746
|
03 Dec 2019 |
Joseph McKenna | Info | mfe.c: MIDAS frontend's 'Equipment name' can embed hostname, determined at run-time | A little advertised feature of the modifications
needed support the msysmon program is
that MIDAS equipment names can support the |
|
|
1748
|
06 Dec 2019 |
Konstantin Olchanski | Info | c++11 for RHEL/SL/CentOS-6 | > The default el6 (RHEL/SL/CentOS-6) compiler
is gcc-4.4.7, it does not support c++11,
not even a little bit.
|
|
|
1758
|
12 Jan 2020 |
Konstantin Olchanski | Info | midas on centos-8 status | I now have a centos-8 computer and I tried
midas on it:
|
|
|
1764
|
13 Jan 2020 |
Konstantin Olchanski | Info | How to convert C midas frontends to C++, CAEN libraries | Big thanks to Peter Kunz - specifically when
using the CAEN libraries:
|
|
|
1769
|
13 Jan 2020 |
Konstantin Olchanski | Info | status of self-signed https certificates | Now firefox returns the same error. version
72.0.1.
|
|
|
1799
|
29 Jan 2020 |
Pintaudi Giorgio | Info | Force triggering of idle routine of a frontend | Hello!
As you know, the generic MIDAS frontend has
a class driver, device driver, bus driver
|
|
|
1802
|
02 Feb 2020 |
Konstantin Olchanski | Info | Force triggering of idle routine of a frontend | Hi, Giorgio - I think you encountered a fundamental
problem with what to do at the begin of
run. There are two ways of thinking about |
|
|
1805
|
02 Feb 2020 |
Pintaudi Giorgio | Info | Force triggering of idle routine of a frontend | Dear Konstantin,
thank you very much for the explanation.
I already have an idea of how to solve my |
|
|
1806
|
03 Feb 2020 |
Stefan Ritt | Info | Force triggering of idle routine of a frontend | It is important to note that slow control
readout and sending of midas events are two
separate things. Readout is done as fast |
|
|
1808
|
04 Feb 2020 |
Pintaudi Giorgio | Info | Force triggering of idle routine of a frontend | Dear Stefan,
thank you very much for the clarification.
I knew about the DF_XXX flags and I am making |
|
|
1811
|
07 Feb 2020 |
Stefan Ritt | Info | Force triggering of idle routine of a frontend | Dear Giorgio,
ok, now I'm slowly getting your point.
|
|
|
1812
|
07 Feb 2020 |
Pintaudi Giorgio | Info | Force triggering of idle routine of a frontend | Dear Stefan,
Thank you for the advice. I will try to modify
the driver as you say. As for the dynamical |
|
|
1813
|
09 Feb 2020 |
Stefan Ritt | Info | Force triggering of idle routine of a frontend | You dirty hacks will probably work, but what
you REALLY want is to read out your HV always
as fast as possible, not only during run |
|
|
1816
|
10 Feb 2020 |
Konstantin Olchanski | Info | Force triggering of idle routine of a frontend | > We had a case where a detector produced
electrostatic discharges which only lasted
for a second or so
|
|