ID |
Date |
Author |
Topic |
Subject |
Text |
 |
1512
|
28 Mar 2019 |
Konstantin Olchanski | Bug Fix | rmlogger events - double counting | > I realized that if I use 'rmlogger' to write
events in ROOT format,
> each event is counted twice;
|
|
Draft
|
29 Mar 2019 |
Gennaro Tortone | Bug Fix | rmlogger events - double counting | Hi,
> I confirm this problem - event counter |
|
1515
|
29 Mar 2019 |
Gennaro Tortone | Bug Fix | rmlogger events - double counting | Hi,
> I confirm this problem - event counter |
|
1518
|
29 Mar 2019 |
Konstantin Olchanski | Bug Fix | rmlogger events - double counting | >
> > BTW, I do not think the ROOT writer (and
rmlogger) get much use these days ...
|
|
1551
|
17 Jun 2019 |
Konstantin Olchanski | Bug Fix | removed modbset() from mhttpd.js | The modbset() function in mhttpd.js is not
used anywhere in midas and it misleads midas
users into thinking that it works like the |
|
1554
|
17 Jun 2019 |
Stefan Ritt | Bug Fix | removed modbset() from mhttpd.js | I disagree. The modbset() function is used
in many custom pages at PSI because people
are tired of typing mjsonrpc_db_paste([path],[value]) |
|
1555
|
17 Jun 2019 |
Konstantin Olchanski | Bug Fix | removed modbset() from mhttpd.js | If it's a function intended for general use,
it should be in midas.js.
|
|
1556
|
17 Jun 2019 |
Konstantin Olchanski | Bug Fix | restored modbset() in midas.js | > The modbset() function is used in many custom
pages at PSI ...
|
|
1559
|
17 Jun 2019 |
Stefan Ritt | Bug Fix | removed modbset() from mhttpd.js | A ladder of promise event handlers is certainly
one possibility to enforce the order of ODB
writes, but I wonder if we could so something |
|
1560
|
18 Jun 2019 |
Konstantin Olchanski | Bug Fix | removed modbset() from mhttpd.js | > A ladder of promise event handlers is certainly
one possibility to enforce the order of ODB
writes, but I wonder if we could so something |
|
1561
|
18 Jun 2019 |
Stefan Ritt | Bug Fix | removed modbset() from mhttpd.js | Just to make this point clear: The "write-to-odb-read-via-hotlink"
was never meant to guarantee the receiving
side to see each change. If changes happen |
|
1563
|
18 Jun 2019 |
Konstantin Olchanski | Bug Fix | removed modbset() from mhttpd.js | > Just to make this point clear: The "write-to-odb-read-via-hotlink"
was never meant to guarantee the receiving
side to see each change. If changes happen |
|
1663
|
14 Aug 2019 |
Konstantin Olchanski | Bug Fix | incorrect recursion in ss_suspend() via the user event handler | The ROOTANA midas analyzer uncovered a problem
with recursive use of ss_suspend().
|
|
1704
|
27 Sep 2019 |
Konstantin Olchanski | Bug Fix | improvement for midas web page resource use | I noticed that midas web pages consume unexpectedly
large amount of resources, as observed by
the chrome browser
|
|
1705
|
27 Sep 2019 |
Konstantin Olchanski | Bug Fix | improvement for midas web page resource use (alarm sound) | > I noticed that midas web pages consume unexpectedly
large amount of resources, as observed by
the chrome browser
|
|
1744
|
28 Nov 2019 |
Konstantin Olchanski | Bug Fix | improvement for midas web page resource use (alarm sound and fit_message) | > > I noticed that midas web pages consume
unexpectedly large amount of resources, as
observed by the chrome browser
|
|
1745
|
28 Nov 2019 |
Konstantin Olchanski | Bug Fix | improvement for midas web page resource use (alarm sound and fit_message) | > > > I noticed that midas web pages consume
unexpectedly large amount of resources, as
observed by the chrome browser
|
|
2229
|
24 Jun 2021 |
Konstantin Olchanski | Bug Fix | changes in history plots | I am updating the history plots. Main changes:
- the old history display code should again |
|
2231
|
24 Jun 2021 |
Stefan Ritt | Bug Fix | changes in history plots | I disagree with the proposed change to scale
the HV current for a "nice" display. If values
are scaled, the axis should be
|
|
2234
|
25 Jun 2021 |
Stefan Ritt | Bug Fix | changes in history plots | A general warning: With the recent history
changes implemented in the develop branch,
starting from a fresh ODB and editing
|
|