| ID |
Date |
Author |
Topic |
Subject |
Text |
 |
|
1661
|
13 Aug 2019 |
Stefan Ritt | Info | Precedence of equipment/common structure | > Lacking any ideas for improvements, I vote
for the status quo. (plus a review of the
documentation to ensure we have clearly
|
|
|
1662
|
14 Aug 2019 |
Stefan Ritt | Info | New history plot facility | During my visit at TRIUMF we rewrote the history
plotting functionality of midas. Instead
of
|
|
|
1666
|
28 Aug 2019 |
Stefan Ritt | Forum | History plot problems for frontend with multiple indicies | My first question would be why are you using
several font-ends at all? That makes things
more
|
|
|
1674
|
06 Sep 2019 |
Stefan Ritt | Info | New history plot facility | > 1) it would be nice to have an option to
format the label output (see attachment 1)
|
|
|
Draft
|
07 Sep 2019 |
Stefan Ritt | Info | New history plot facility | > This I found out, yet the attachment here
shows another case where it would be useful
to be |
|
|
1678
|
07 Sep 2019 |
Stefan Ritt | Info | New history plot facility | > This I found out, yet the attachment here
shows another case where it would be useful
to be
|
|
|
1679
|
08 Sep 2019 |
Stefan Ritt | Info | New history plot facility | > 1) it would be nice to have an option to
format the label output (see attachment 1)
|
|
|
1683
|
12 Sep 2019 |
Stefan Ritt | Info | History panels in custom pages | Indeed there was a bug in some JavaScript
code, which I fixed here: https://bitbucket.org/tmidas/midas/commits/d2b1a783240e252820c622001e15c09c5d7798c0
|
|
|
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:
|
|
|
1702
|
26 Sep 2019 |
Stefan Ritt | Forum | Open a hotlink to a single element in an ODB array | [quote="Pintaudi Giorgio"]Hello!
Just a little question about the ODB hotlinks.
Is it possible to open a hotlink
|
|
|
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 |
|
|
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 |
|
|
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.
|
|
|
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
|
|
|
1735
|
15 Nov 2019 |
Stefan Ritt | Suggestion | javascript comunication | Very good idea. And thanks for finding the
document.hidden solution. I put it in, so
give it a try.
|
|
|
1739
|
18 Nov 2019 |
Stefan Ritt | Suggestion | javascript comunication | > Hi, Stefan - I did not look at your code,
if all midas tabs are inactive, will the
alarm sound still play?
|
|
|
1740
|
18 Nov 2019 |
Stefan Ritt | Suggestion | javascript comunication | > a) google chrome slows down the execution
of javascript in inactive tabs, leading to
trouble
|
|
|
1743
|
28 Nov 2019 |
Stefan Ritt | Bug Report | midas alarm sound unreliable in google-chrome | The document
https://docs.google.com/document/d/1_278v_plodvgtXSgnEJ0yjZJLg14Ogf-ekAFNymAJoU/edit
|
|
|
1773
|
14 Jan 2020 |
Stefan Ritt | Forum | frontend issues with midas-2019-09 | We updated midas/examples/experiment/frontend.cxx
to correctly contain
|
|
|
1774
|
14 Jan 2020 |
Stefan Ritt | Forum | frontend issues with midas-2019-09 | Actually now I see that
a4) poll_event() and interrupt_configure() |
|