| ID |
Date |
Author |
Topic |
Subject |
Text |
 |
|
3175
|
08 Dec 2025 |
Konstantin Olchanski | Suggestion | manalyzer root output file with custom filename including run number | I updated the root helper constructor to give
the user more control over ROOT output file
names.
|
|
|
3174
|
08 Dec 2025 |
Konstantin Olchanski | Suggestion | Get manalyzer to configure midas::odb when running offline | > > #include "manalyzer.h"
> > #include "midasio.h"
> > +#include "odbxx.h"
|
|
|
3173
|
08 Dec 2025 |
Konstantin Olchanski | Bug Report | odbxx memory leak with JSON ODB dump | I was testing odbxx with manalyzer, decided
to print an odb value in every event,
and it worked fine in online mode, but bombed |
|
|
3172
|
08 Dec 2025 |
Zaher Salman | Bug Report | Error(?) in custom page documentation | The sequencer pages were adjusted to the work
with this bug fix.
|
|
|
3171
|
07 Dec 2025 |
Konstantin Olchanski | Suggestion | Get manalyzer to configure midas::odb when running offline | > #include "manalyzer.h"
> #include "midasio.h"
> +#include "odbxx.h"
|
|
|
3170
|
05 Dec 2025 |
Konstantin Olchanski | Info | address and thread sanitizers | I added cmake support for the thread sanitizer
(address sanitizer was already
there). Use:
|
|
|
3169
|
05 Dec 2025 |
Konstantin Olchanski | Bug Fix | update of JRPC and BRPC | With the merge of RPC_CXX code, MIDAS RPC
can now return data of arbitrary large size
and I am
|
|
|
3168
|
05 Dec 2025 |
Konstantin Olchanski | Info | MIDAS RPC add support for std::string and std::vector<char> | > > This is moving slowly. I now have RPC
caller side support for std::string and
> > std::vector<char>. RPC server side is |
|
|
3167
|
03 Dec 2025 |
Stefan Ritt | Suggestion | Improve process for adding new variables that can be shown in history plots | > Now, mlogger just silently continues not
writing to history. There is no ongoing error
message, there is no
|
|
|
3166
|
03 Dec 2025 |
Konstantin Olchanski | Suggestion | Improve process for adding new variables that can be shown in history plots | > 3b) mlogger used to rescan ODB each time
a new run is started, this code was removed
|
|
|
3165
|
03 Dec 2025 |
Konstantin Olchanski | Bug Fix | no more breakage in history display when panning | In the DL experiment (unknown version of midas,
likely mid-summer 2025), we see artefacts
in the
|
|
|
3164
|
02 Dec 2025 |
Konstantin Olchanski | Info | cm_expand_env() | Just to remember, MIDAS has cm_expand_env()
to expand environment variables, in
file paths, etc. It is used in several places |
|
|
3163
|
01 Dec 2025 |
Konstantin Olchanski | Info | MIDAS RPC add support for std::string and std::vector<char> | > This is moving slowly. I now have RPC caller
side support for std::string and
> std::vector<char>. RPC server side is next. |
|
|
3162
|
01 Dec 2025 |
Konstantin Olchanski | Bug Fix | mvodb updated | I updated mvodb and test_mvodb. MIDAS ODB
and JSON ODB now implement all API
functions. ReadKey, ReadDir and ReadKeyLastWritten |
|
|
3160
|
28 Nov 2025 |
Konstantin Olchanski | Suggestion | mvodb WS and family type matching | Just in time, enter std::string_view.
https://stackoverflow.com/questions/40127965/how-exactly-is-stdstring-view-faster-than-const-stdstring
|
|
|
3159
|
28 Nov 2025 |
Konstantin Olchanski | Suggestion | mvodb WS and family type matching | > > 2) "advanced" c++ code:
> >
> > void foo(const std::string& xxx) { ... |
|
|
3158
|
27 Nov 2025 |
Stefan Ritt | Suggestion | mvodb WS and family type matching | > 2) "advanced" c++ code:
>
> void foo(const std::string& xxx) { ... |
|
|
3157
|
27 Nov 2025 |
Stefan Ritt | Suggestion | Improve process for adding new variables that can be shown in history plots | > 1) history is independent from "runs", we
see a change, we apply it (even if it takes
10 sec or 2 minutes).
|
|
|
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
|
|