| ID |
Date |
Author |
Topic |
Subject |
Text |
 |
|
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 |
|
|
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 |
|
|
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 |
|
|
2860
|
27 Sep 2024 |
Ben Smith | Forum | Python frontend rate limitations? | > in your case the limitation is likely that
you're sending 1.25MB per event and we have
a lot of data marshalling to do between the |
|
|
2859
|
24 Sep 2024 |
Konstantin Olchanski | Suggestion | Clean up compiler warning in manalyzer | > > I like the look of std::format, looks
cleaner than string streams
>
|
|
|
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. |
|
|
2857
|
24 Sep 2024 |
Stefan Ritt | Info | News MSCB++ API | > Where is the example of error handling?
#include "mscbxx.h"
|
|
|
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.
|
|
|
2855
|
20 Sep 2024 |
Stefan Ritt | Suggestion | Clean up compiler warning in manalyzer | > I like the look of std::format, looks cleaner
than string streams
|
|
|
2854
|
20 Sep 2024 |
Joseph McKenna | Suggestion | Clean up compiler warning in manalyzer | > > This is a super small pull request, simple
replace deprecated sprintf with snprintf
> > https://bitbucket.org/tmidas/manalyzer/pull-requests/9
|
|
|
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:
|
|
|
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.
|
|
|
2851
|
17 Sep 2024 |
Konstantin Olchanski | Bug Report | Crash using ODB watch | > {
> odb new_settings("/Equipment/Test FE/Settings");
> new_settings.watch(watch); // <-- here |
|
|
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 |
|
|
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 |
|
|
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 |
|
|
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! |
|
|
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 |
|
|
2845
|
16 Sep 2024 |
Marius Köppel | Bug Report | Crash using ODB watch | Hi all,
last week I was running MIDAS with the commit |
|
|
2844
|
13 Sep 2024 |
Konstantin Olchanski | Suggestion | Clean up compiler warning in manalyzer | > This is a super small pull request, simple
replace deprecated sprintf with snprintf
> https://bitbucket.org/tmidas/manalyzer/pull-requests/9
|
|