| ID |
Date |
Author |
Topic |
Subject |
Text |
 |
|
2786
|
04 Jul 2024 |
Nick Hastings | Bug Report | Fail to build in the examples/experiment | I think this may only be an issue on the development
branch.
Can you confirm that that is what you are |
|
|
2789
|
05 Jul 2024 |
Tam Kai Chung | Bug Report | Fail to build in the examples/experiment | Hello Nick,
I am using the most updated tag: midas-2022-05-c-1284-g4a77127b.
|
|
|
2794
|
31 Jul 2024 |
Lukas Gerritzen | Bug Report | New history plots: Zooming in on logarithmic y axis does not work as expected | Using the mouse to click and drag on a logarithmic
y axis triggers a zooming behaviour as if
the user zoomed in on a linear axis.
|
|
|
2795
|
31 Jul 2024 |
Stefan Ritt | Bug Report | New history plots: Zooming in on logarithmic y axis does not work as expected | I fixed that and committed the change to megon02,
just reload your browser. I also set ymin
and ymax of the Vacuum plot to meaningful |
|
|
2798
|
07 Aug 2024 |
Lukas Gerritzen | Bug Report | File name bug in csv export | When I export data from a history plot, I
get nonsensical filenames. For example, for
data from today, I got "Xenon-Vacuum-20247107-152815-20247107-160032.csv".
|
|
|
2799
|
07 Aug 2024 |
Stefan Ritt | Bug Report | File name bug in csv export | Thanks. Fixed. Committed. Pulled on megon02.
Stefan |
|
|
2800
|
07 Aug 2024 |
Lukas Gerritzen | Bug Report | File name bug in csv export | Thanks. I think, mplot.js:1844 should be changed
as well, but I haven't tried it with mplot. |
|
|
2801
|
07 Aug 2024 |
Stefan Ritt | Bug Report | File name bug in csv export | Fixed as well. |
|
|
2815
|
30 Aug 2024 |
Zaher Salman | Bug Report | Params not initialized when starting sequencer | The issue with the parameters should be fixed
now. Please test and let me know if it still
happens.
|
|
|
2821
|
04 Sep 2024 |
Lukas Gerritzen | Bug Report | Multiple issues with mhist | Hi,
I am having some trouble with mhist. I suppose |
|
|
2822
|
04 Sep 2024 |
Lukas Gerritzen | Bug Report | Params not initialized when starting sequencer | I think I have had similar issues in a custom
page, where I wrote values to the ODB and
they were not ready when I needed them. If |
|
|
2823
|
04 Sep 2024 |
Zaher Salman | Bug Report | Params not initialized when starting sequencer | The problem here was that the JS code did
not wait to msequencer to finish preparing
the "/Sequencer/Param" in the ODB, so I had |
|
|
2834
|
11 Sep 2024 |
Konstantin Olchanski | Bug Report | Multiple issues with mhist | I think I can offer some insight into your
problems:
|
|
|
2841
|
13 Sep 2024 |
Konstantin Olchanski | Bug Report | mfe.cxx with RO_STOPPED and EQ_POLLED | > > I noticed that a check was added to mfe.cxx
in 1961af0d6:
|
|
|
2845
|
16 Sep 2024 |
Marius Köppel | Bug Report | Crash using ODB watch | Hi all,
last week I was running MIDAS with the commit |
|
|
2846
|
16 Sep 2024 |
Stefan Ritt | Bug Report | Crash using ODB watch | The answer is in the error message: „Object
went out of scope“. When your frontent_init()
exits, the odb objects are destroyed. When |
|
|
2847
|
16 Sep 2024 |
Marius Koeppel | Bug Report | Crash using ODB watch | This is not the case here. Note that the error
message: "Callback received for a midas::odb
object which went out of scope" is not called! |
|
|
2848
|
16 Sep 2024 |
Stefan Ritt | Bug Report | Crash using ODB watch | Well, the object *went* out of scope. For
my code it‘s hard to realize this, so the
error reporting is poor. Also the first object |
|
|
2849
|
16 Sep 2024 |
Marius Koeppel | Bug Report | Crash using ODB watch | Okay, but this is then a big issue IMO. For
Mu3e we do this in every frontend and I also
checked again all of these watches are broken |
|
|
2850
|
16 Sep 2024 |
Mark Grimes | Bug Report | Crash using ODB watch | Hi,
Maybe I've misunderstood the code, but odb::watch()
creates a deep copy of itself to set the |
|