| ID |
Date |
Author |
Topic |
Subject |
Text |
 |
|
3081
|
22 Sep 2025 |
Stefan Ritt | Suggestion | Get manalyzer to configure midas::odb when running offline | I will work today on the odbxx API to make
sure there are no memory leaks when you switch
form one file to another. I talked to KO |
|
|
3082
|
22 Sep 2025 |
Konstantin Olchanski | Suggestion | Get manalyzer to configure midas::odb when running offline | > I will work today on the odbxx API to make
sure there are no memory leaks when you switch
form one file to another. I talked to KO |
|
|
3083
|
22 Sep 2025 |
Konstantin Olchanski | Suggestion | Get manalyzer to configure midas::odb when running offline | > > ....Before commit of this patch, can you
confirm the RunInfo destructor
> > deletes this ODB stuff from odbxx? manalyzer |
|
|
3085
|
22 Sep 2025 |
Stefan Ritt | Suggestion | Get manalyzer to configure midas::odb when running offline | > > I will work today on the odbxx API to
make sure there are no memory leaks when
you switch form one file to another. I talked |
|
|
3086
|
22 Sep 2025 |
Stefan Ritt | Suggestion | Get manalyzer to configure midas::odb when running offline | > > > Of course with this patch extending
manalyzer to process two or more runs at
the same time becomes impossible.
|
|
|
3097
|
24 Sep 2025 |
Thomas Lindner | Suggestion | Improve process for adding new variables that can be shown in history plots | Documenting a discussion I had with Konstantin
a while ago.
|
|
|
3099
|
26 Sep 2025 |
Mark Grimes | Suggestion | Get manalyzer to configure midas::odb when running offline | > ...I talked to KO so he agreed that yo then
commit your proposed change of manalyzer
|
|
|
Draft
|
26 Sep 2025 |
Konstantin Olchanski | Suggestion | Get manalyzer to configure midas::odb when running offline | > > ...I talked to KO so he agreed that yo
then commit your proposed change of manalyzer
|
|
|
3106
|
27 Oct 2025 |
Giovanni Mazzitelli | Suggestion | Python sc_frontend.py Display and History variables | We would like to write an sc_frontend in Python
instead of C++. All our drivers
work correctly, as well as the creation of |
|
|
3112
|
12 Nov 2025 |
Jonas A. Krieger | Suggestion | manalyzer root output file with custom filename including run number | Hi all,
Could you please get back to me about whether |
|
|
3114
|
13 Nov 2025 |
Stefan Ritt | Suggestion | Python sc_frontend.py Display and History variables | > We would like to write an sc_frontend in
Python instead of C++. All our drivers
> work correctly, as well as the creation |
|
|
3115
|
13 Nov 2025 |
Ben Smith | Suggestion | Python sc_frontend.py Display and History variables | > > We would like to write an sc_frontend
in Python instead of C++. All our drivers
|
|
|
3142
|
25 Nov 2025 |
Konstantin Olchanski | Suggestion | manalyzer root output file with custom filename including run number | Hi, Jonas, thank you for reminding me about
this. I hope to work on manalyzer in the
next few weeks and I will review the ROOT |
|
|
3143
|
25 Nov 2025 |
Konstantin Olchanski | Suggestion | Improve process for adding new variables that can be shown in history plots | > One aspect of the MIDAS history plotting
I find frustrating is the sequence for adding
a new history
|
|
|
3145
|
26 Nov 2025 |
Thomas Lindner | Suggestion | Improve process for adding new variables that can be shown in history plots |
> 3) mlogger must discover this new ODB entry:
>
|
|
|
3146
|
26 Nov 2025 |
Lars Martin | Suggestion | mvodb WS and family type matching | This is not a bug per se, but I find it a
little odd that the MVOdb functions RS,
RSA, RSAI, and WSA use std::string as their |
|
|
3149
|
27 Nov 2025 |
Stefan Ritt | Suggestion | Improve process for adding new variables that can be shown in history plots | > I assume that mlogger rescanning ODB is
somewhat intensive process; and that's why
we don't want rescanning to
|
|
|
3151
|
27 Nov 2025 |
Konstantin Olchanski | Suggestion | mvodb WS and family type matching | > This is not a bug per se, but I find it
a little odd that the MVOdb functions RS,
|
|
|
3153
|
27 Nov 2025 |
Konstantin Olchanski | Suggestion | Improve process for adding new variables that can be shown in history plots | > > I assume that mlogger rescanning ODB is
somewhat intensive process; and that's why
we don't want rescanning to
|
|
|
3156
|
27 Nov 2025 |
Thomas Lindner | Suggestion | Improve process for adding new variables that can be shown in history plots | > > Indeed. But whatever "new" we design for
the scan will users complain "last week it
was enough to restart the logger, now what |
|