| ID |
Date |
Author |
Topic |
Subject |
Text |
 |
|
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 |
|
|
3155
|
27 Nov 2025 |
Konstantin Olchanski | Forum | Control external process from inside MIDAS | > Rather than investing time to re-invent
the wheel here, better try to modify your
EPICS driver process to
|
|
|
3154
|
27 Nov 2025 |
Konstantin Olchanski | Info | switch midas to c++17 | >
> set(CMAKE_CXX_STANDARD 17)
> set(CMAKE_CXX_STANDARD_REQUIRED ON)
|
|
|
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
|
|
|
3152
|
27 Nov 2025 |
Konstantin Olchanski | Bug Report | Error(?) in custom page documentation | the double-decode bug strikes again!
> This commit breaks the sequencer pages...
|
|
|
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,
|
|
|
3150
|
27 Nov 2025 |
Zaher Salman | Bug Report | Error(?) in custom page documentation | This commit breaks the sequencer pages...
> Indeed a bug. Fixed in commit
|
|
|
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
|
|
|
3148
|
27 Nov 2025 |
Stefan Ritt | Bug Report | Error(?) in custom page documentation | Indeed a bug. Fixed in commit
https://bitbucket.org/tmidas/midas/commits/5c1133df073f493d74d1fc4c03fbcfe80a3edae4
|
|
|
3147
|
26 Nov 2025 |
Lars Martin | Bug Report | Error(?) in custom page documentation | https://daq00.triumf.ca/MidasWiki/index.php/Custom_Page#modb
says that
|
|
|
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 |
|
|
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:
>
|
|
|
3144
|
26 Nov 2025 |
Stefan Ritt | Info | switch midas to c++17 | I switched from
target_compile_features(<target> PUBLIC |
|
|
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
|
|
|
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 |
|
|
3141
|
25 Nov 2025 |
Konstantin Olchanski | Info | switch midas to c++17 | > target_compile_features(<target> PUBLIC
cxx_std_17)
> which correctly causes a
|
|
|
3140
|
25 Nov 2025 |
Konstantin Olchanski | Info | switch midas to c++17 | >
> > I notice the cmake does not actually
pass "-std=c++17" to the c++ compiler, and |
|
|
3139
|
25 Nov 2025 |
Konstantin Olchanski | Bug Report | Cannot edit values in a subtree containing only a single array of BOOLs using the ODB web interface | > Thanks --- it looks like this commit resolves
the issue for us ...
> Thanks to Ben Smith for pointing us at |
|
|
3138
|
25 Nov 2025 |
Konstantin Olchanski | Bug Fix | ODB update, branch feature/db_delete_key merged into develop | > Thanks for the fixes, which I all approve.
>
> There is still a "follow_links" in midas_c_compat.h |
|
|
3137
|
25 Nov 2025 |
Konstantin Olchanski | Bug Fix | fixed db_find_keys() | Function db_find_keys() added by person unnamed
in April 2020 never worked correctly, it
is now fixed,
|
|