ID |
Date |
Author |
Topic |
Subject |
Text |
|
1688
|
16 Sep 2019 |
Konstantin Olchanski | Info | New history plot facility | > During my visit at TRIUMF we rewrote the
history plotting functionality of midas.
|
|
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.
|
|
1695
|
17 Sep 2019 |
Konstantin Olchanski | Info | New history plot facility | > > On the mhttpd side, please capture the
stack trace from the crash
>
|
|
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
|
|
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
|
|
1706
|
27 Sep 2019 |
Konstantin Olchanski | Release | midas-2019-09 | I created the release branch for midas-2019-09
and tag midas-2019-09-a.
|
|
1707
|
27 Sep 2019 |
Konstantin Olchanski | Forum | Open a hotlink to a single element in an ODB array | > I will try to use the db_watch function
in the future.
|
|
1708
|
27 Sep 2019 |
Konstantin Olchanski | Suggestion | recover daq and hardware safety. | > We have encountered a safety issue with
our HPGe HV and it's midas frontend.
|
|
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.
|
|
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
|
|
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 |
|
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 |
|
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 |
|
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, |
|
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 |
|
1729
|
23 Oct 2019 |
Konstantin Olchanski | Forum | Data for key truncated | > I keep on getting messages like this:
> 16:25:35 [fecaen,ERROR] [odb.c:4567:db_get_data,ERROR]
data for key
|
|
1730
|
24 Oct 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.
|
|