| ID |
Date |
Author |
Topic |
Subject |
Text |
 |
|
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 |
|
|
2851
|
17 Sep 2024 |
Konstantin Olchanski | Bug Report | Crash using ODB watch | > {
> odb new_settings("/Equipment/Test FE/Settings");
> new_settings.watch(watch); // <-- here |
|
|
2852
|
18 Sep 2024 |
Marius Koeppel | Bug Report | Crash using ODB watch | I created a PR to fix this issue https://bitbucket.org/tmidas/midas/pull-requests/42.
The crash happened since the change in commit
3ad98c5 always got the ODB via XML.
|
|
|
2853
|
20 Sep 2024 |
Stefan Ritt | Bug Report | Crash using ODB watch | The problem has been fixed in the current
version. Here is my analysis:
|
|
|
2856
|
22 Sep 2024 |
Tam Kai Chung | Bug Report | Can we convert the .mid file into .root file | Dear experts,
I am a new user of MIDAS. I have just created
some banks by a frontend.cxx code.
|
|
|
2858
|
24 Sep 2024 |
Konstantin Olchanski | Bug Report | Can we convert the .mid file into .root file | "Can we convert the .mid file into .root file".
yes, you can, but the operation is under-defined. |
|
|
2861
|
07 Oct 2024 |
Amy Roberts | Bug Report | Difficulty running MIDAS on Rocky 9.4 | We're trying to install the SuperCDMS version
of MIDAS on a Rocky 9.4 Virtual
Machine and are getting a persistent error |
|
|
2862
|
07 Oct 2024 |
Ben Smith | Bug Report | Difficulty running MIDAS on Rocky 9.4 | > We're trying to install the SuperCDMS version
of MIDAS on a Rocky 9.4 Virtual
> Machine and are getting a persistent error |
|
|
2863
|
07 Oct 2024 |
Konstantin Olchanski | Bug Report | Difficulty running MIDAS on Rocky 9.4 | > We're trying to install the SuperCDMS version
of MIDAS on a Rocky 9.4 Virtual
> Machine and are getting a persistent error |
|
|
2864
|
08 Oct 2024 |
Mark Grimes | Bug Report | Difficulty running MIDAS on Rocky 9.4 | We run Midas with no problems on Rocky 9.4,
although not in a virtual machine. We're
very close to the head of `develop`.
|
|
|
2865
|
08 Oct 2024 |
Amy Roberts | Bug Report | Difficulty running MIDAS on Rocky 9.4 | > > We're trying to install the SuperCDMS
version of MIDAS on a Rocky 9.4 Virtual
> > Machine and are getting a persistent |
|