| ID |
Date |
Author |
Topic |
Subject |
Text |
 |
|
2194
|
02 Jun 2021 |
Konstantin Olchanski | Bug Report | History plots deceiving users into thinking data is still logging | https://bitbucket.org/tmidas/midas/issues/305/log_history_periodic-doesnt-account-for
this problem is a blocker for the next midas |
|
|
2336
|
10 Feb 2022 |
Stefan Ritt | Bug Report | History plots deceiving users into thinking data is still logging | The problem has been fixed on commit 825935dc
on Oct. 2021 and runs fine since then at
PSI. If TRIUMF people
|
|
|
1665
|
28 Aug 2019 |
Nick Hastings | Forum | History plot problems for frontend with multiple indicies | Hello experts,
I have been writing a SC frontend for a powersupply. |
|
|
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
|
|
|
1667
|
28 Aug 2019 |
Nick Hastings | Forum | History plot problems for frontend with multiple indicies | Hi Stefan,
thanks for you quick reply.
|
|
|
1668
|
28 Aug 2019 |
lcp | Forum | History plot problems for frontend with multiple indicies | hi,
> > That makes things more
|
|
|
1669
|
29 Aug 2019 |
Ben Smith | Forum | History plot problems for frontend with multiple indicies | Hi Nick,
I confirm that this issue appears when using |
|
|
Draft
|
29 Aug 2019 |
Nick Hastings | Forum | History plot problems for frontend with multiple indicies | Hi LCP,
thanks for the suggestion and link. Unfortunatly |
|
|
Draft
|
29 Aug 2019 |
Nick Hastings | Forum | History plot problems for frontend with multiple indicies | Hi Ben,
thanks for your reply. I can confirm that |
|
|
1672
|
01 Sep 2019 |
Nick Hastings | Forum | History plot problems for frontend with multiple indicies | Hi Ben,
thanks for your reply. I can confirm that |
|
|
1689
|
16 Sep 2019 |
Konstantin Olchanski | 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
|
|
|
1691
|
16 Sep 2019 |
Konstantin Olchanski | Forum | History plot problems for frontend with multiple indicies | > it's probably better to run a multi-threaded
setup, than individual frontends.
|
|
|
1692
|
16 Sep 2019 |
Konstantin Olchanski | Forum | History plot problems for frontend with multiple indicies | > thanks for your reply. I can confirm that
your suggested workaround does indeed
> make the problem dissapear.
|
|
|
1693
|
16 Sep 2019 |
Nick Hastings | Forum | History plot problems for frontend with multiple indicies | Hi Konstantin,
thanks for your reply.
|
|
|
1696
|
17 Sep 2019 |
Konstantin Olchanski | Forum | History plot problems for frontend with multiple indicies | > [local:e666:S]History>ls -l /History/Events
> Key name Type
#Val Size Last Opn Mode Value
|
|
|
Draft
|
18 Sep 2019 |
Nick Hastings | Forum | History plot problems for frontend with multiple indicies | > > [local:e666:S]History>ls -l /History/Events
> > Key name Type
#Val Size Last Opn Mode Value |
|
|
1699
|
18 Sep 2019 |
Nick Hastings | Forum | History plot problems for frontend with multiple indicies | Hi Konstantin,
> > [local:e666:S]History>ls -l /History/Events
|
|
|
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
|
|
|
1986
|
24 Aug 2020 |
Konstantin Olchanski | Forum | History plot problems for frontend with multiple indicies | This turned out to be a tricky problem. I
am adding a warning about it in mlogger.
This should go into midas-
|
|
|
2015
|
19 Nov 2020 |
Joseph McKenna | Forum | History plot consuming too much memory |
A user reported an issue that if they were |
|