| ID |
Date |
Author |
Topic |
Subject |
Text |
 |
|
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] |
|
|
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 |
|
|
1726
|
15 Oct 2019 |
Stefan Ritt | Suggestion | recover daq and hardware safety. | There is a not-so-well-known function in the
ODB to write protect some keys. You can do
|
|
|
Draft
|
14 Oct 2019 |
Joseph McKenna | Forum | tmfe.cxx - Future frontend design | Hi,
I have been looking at the 2019 workshop |
|
|
1724
|
14 Oct 2019 |
Stefan Ritt | Bug Report | lazylogger in cmake & max_event_size | > > The compile option -DHAVE_FTPLIB checked
in mdsupport.cxx disappeared if you
> > compile with cmake.
|
|
|
1723
|
10 Oct 2019 |
Stefan Ritt | Bug Report | History data size mismatch | > Yes, we could have
> kept that apart, yes, in this case a double
would also work (and not break things), but |
|
|
1722
|
10 Oct 2019 |
Nik Berger | Bug Report | History data size mismatch | >I wonder why do you this via ODB links. The
"standard" way of writing to the history
should be to create events for an equipment |
|
|
1721
|
10 Oct 2019 |
Konstantin Olchanski | Bug Report | History data size mismatch | >
> In our history, a long list of doubles
(64 Bit) fas followed by three floats (32 |
|
|
1720
|
06 Oct 2019 |
Stefan Ritt | Bug Report | History data size mismatch | I wonder why do you this via ODB links. The
"standard" way of writing to the history
should be to create events for an equipment |
|
|
1719
|
06 Oct 2019 |
Nik Berger | Bug Report | History data size mismatch | Logging a list of variables to the history
via links in the history ODB subtree,
we get messages as follows at every run start:
|
|
|
1718
|
30 Sep 2019 |
Konstantin Olchanski | Forum | MIDAS interface for WAGASCI online monitor | >
> As Thomas said, maybe the simplest thing
would be to use the ROOT THttpServer. Honestly, |
|
|
1717
|
29 Sep 2019 |
Pintaudi Giorgio | Forum | MIDAS interface for WAGASCI online monitor | Dear Thomas and Konstantin,
thank you very much for the feedback. I found |
|
|
1716
|
29 Sep 2019 |
Konstantin Olchanski | Forum | MIDAS interface for WAGASCI online monitor | > online monitor would show (almost in real-time)
the
> gain, the dark noise, and the pedestal |
|
|
1715
|
29 Sep 2019 |
Konstantin Olchanski | Suggestion | recover daq and hardware safety. | >
> The issue occurs when e.g. one channel
can not be turned on and ramp for some temp/specific |
|
|
1714
|
29 Sep 2019 |
Thomas Lindner | Forum | MIDAS interface for WAGASCI online monitor | Hi Pintaudi Giorgio,
I think that the ROOT THttpServer is an option. |
|
|
1713
|
28 Sep 2019 |
Pintaudi Giorgio | Forum | MIDAS interface for WAGASCI online monitor | Hello!
This question is rather complex so please
forgive me if I leave out some
|
|
|
1712
|
28 Sep 2019 |
Frederik Wauters | Suggestion | recover daq and hardware safety. | Dear Konstantin,
So let me retract the term "safety issue" |
|
|
1711
|
27 Sep 2019 |
Konstantin Olchanski | Forum | mhttpd start and stop redirect to Transition page | > I recently upgraded to MIDAS version midas-2019-06-b.
I had to make a few changes
> to get our custom page running again, but |
|
|
1710
|
27 Sep 2019 |
Konstantin Olchanski | Forum | History plot problems for frontend with multiple indicies | We should fix this for midas-2019-10.
https://bitbucket.org/tmidas/midas/issues/193/confusion-in-history-event-ids
|
|
|
1709
|
27 Sep 2019 |
Konstantin Olchanski | Bug Report | lazylogger in cmake & max_event_size | > The compile option -DHAVE_FTPLIB checked
in mdsupport.cxx disappeared if you
> compile with cmake.
|
|