| ID |
Date |
Author |
Topic |
Subject |
Text |
 |
|
2988
|
21 Mar 2025 |
Stefan Ritt | Bug Fix | bitbucket builds fixed | > bitbucket automatic builds were broken after
mfe.cxx started printing some additional
messages added in commit
|
|
|
2987
|
21 Mar 2025 |
Alex Kozlinski | Suggestion | improved find_package behaviour for Midas | > > currently to link Midas to project one
has to do several steps ...
>
|
|
|
2985
|
21 Mar 2025 |
Stefan Ritt | Bug Report | please fix compiler warning | > Unnamed person who added this clever bit
of c++ coding, please fix this compiler warning.
Stock g++ on Ubuntu LTS 24.04. Thanks in |
|
|
2980
|
21 Mar 2025 |
Stefan Ritt | Suggestion | BINARY INCOMPATIBLE CHANGE: New alarm count added | > > ALL MIDAS CLIENTS GET RE-COMPILED after
the new code is applied.
>
|
|
|
2979
|
21 Mar 2025 |
Stefan Ritt | Bug Report | Default write cache size for new equipments breaks compatibility with older equipments | > All this is kind of reasonable, as only
two settings of write cache size are useful:
0 to
|
|
|
2978
|
21 Mar 2025 |
Jonas A. Krieger | Bug Report | midas equipment "format" | Hi Konstantin,
In the PSI muSR laboratory, we are running |
|
|
2977
|
20 Mar 2025 |
Konstantin Olchanski | Bug Report | manalyzer module init order problem | Andrea Capra reported a problem with manalyzer
module initialization order.
|
|
|
2976
|
20 Mar 2025 |
Konstantin Olchanski | Info | switch midas to next c++ | > time to choose the next c++!
Ununtu-24.04, MIDAS builds with -std=c++23 |
|
|
2975
|
20 Mar 2025 |
Konstantin Olchanski | Bug Report | Default write cache size for new equipments breaks compatibility with older equipments | > > the main purpose of the event buffer write
cache
> how to control the write cache size:
|
|
|
2974
|
20 Mar 2025 |
Konstantin Olchanski | Bug Report | Default write cache size for new equipments breaks compatibility with older equipments | > the main purpose of the event buffer write
cache
|
|
|
2973
|
20 Mar 2025 |
Konstantin Olchanski | Bug Report | Default write cache size for new equipments breaks compatibility with older equipments | the main purpose of the event buffer write
cache is to prevent high contention for the
|
|
|
2972
|
20 Mar 2025 |
Konstantin Olchanski | Bug Report | Default write cache size for new equipments breaks compatibility with older equipments | I think I added the cache size correctly:
{"Trigger", /* equipment |
|
|
2971
|
20 Mar 2025 |
Konstantin Olchanski | Forum | TMFeRpcHandlerInterface::HandleEndRun when running offline on a Midas file | > I have a manalyzer that uses a derived class
of TMFeRpcHandlerInterface to communicate
information to
|
|
|
2970
|
20 Mar 2025 |
Konstantin Olchanski | Suggestion | improved find_package behaviour for Midas | > After some iterations, we merged the branch
with the new build scheme.
|
|
|
2969
|
20 Mar 2025 |
Konstantin Olchanski | Suggestion | improved find_package behaviour for Midas | > currently to link Midas to project one has
to do several steps ...
|
|
|
2968
|
20 Mar 2025 |
Konstantin Olchanski | Info | make coverage | Some time ago Ben Smith added test coverage
reports using GCC -fprofile-arcs -
ftest-coverage and lcov.
|
|
|
2967
|
20 Mar 2025 |
Konstantin Olchanski | Bug Fix | bitbucket builds fixed | bitbucket automatic builds were broken after
mfe.cxx started printing some additional
messages added in commit
|
|
|
2966
|
20 Mar 2025 |
Konstantin Olchanski | Bug Report | please fix mscb compiler warning | I am getting a scary compiler warning from
MSCB code. I generally avoid touching MSCB
code because I have no MSCB hardware to test |
|
|
2965
|
20 Mar 2025 |
Konstantin Olchanski | Bug Report | please fix compiler warning | Unnamed person who added this clever bit of
c++ coding, please fix this compiler warning.
Stock g++ on Ubuntu LTS 24.04. Thanks in |
|
|
2964
|
20 Mar 2025 |
Konstantin Olchanski | Suggestion | BINARY INCOMPATIBLE CHANGE: New alarm count added | > ALL MIDAS CLIENTS GET RE-COMPILED after
the new code is applied.
|
|