 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 so he agreed that yo
then commit your proposed change of manalyzer
|
|
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 so he agreed that yo
then commit your proposed change of manalyzer
|
|
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 takes object life times very seriously.
>
|
|
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 so he agreed that
yo then commit your proposed change of manalyzer
>
|
|
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.
> > Yes, I hadn't realised that was an option.
>
|
 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.
One aspect of the MIDAS history plotting I find frustrating is the sequence for adding a new history
|
|
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
Merged and pushed.
|
|
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
> Merged and pushed.
|
|
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 the database in the ODB, including the
creation of Commons, Statistics, Variables, and Settings.
|
|
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 something like my earlier suggestion might be considered, or if I should set up some workaround to rename |
|
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 of the database in the ODB, including the
> creation of Commons, Statistics, Variables, and Settings.
|
|
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
> > work correctly, as well as the creation of the database in the ODB, including the
> > creation of Commons, Statistics, Variables, and Settings.
|
|
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 output file name scheme.
K.O.
|
|
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
> variable and then plotting them. ...
|
|
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:
>
|
|
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 type, while WS ans WSAI use const
char*
|
|
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
> happen every time the ODB is changed?
|
|
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,
> RSA, RSAI, and WSA use std::string as their type, while WS ans WSAI use const
> char*
|
|
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
> > happen every time the ODB is changed?
>
|
|
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 do I have to do". So
nothing
> > is perfect. But having a button in the ODB editor like "Rebuild history database" might look more elegant. One issue is that it needs special treatment, |