| ID |
Date |
Author |
Topic |
Subject |
Text |
 |
|
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 |
|
|
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 |
|
|
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 |
|
|
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
|
|
|
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
|
|
|
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:
|
|
|
2977
|
20 Mar 2025 |
Konstantin Olchanski | Bug Report | manalyzer module init order problem | Andrea Capra reported a problem with manalyzer
module initialization order.
|
|
|
2978
|
21 Mar 2025 |
Jonas A. Krieger | Bug Report | midas equipment "format" | Hi Konstantin,
In the PSI muSR laboratory, we are running |
|
|
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
|
|
|
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 |
|
|
2989
|
21 Mar 2025 |
Stefan Ritt | Bug Report | please fix mscb compiler warning | I hopefully fixed the waring (narrowing down
from size_t to int). Please double check
with your compiler.
|
|
|
2998
|
25 Mar 2025 |
Konstantin Olchanski | Bug Report | midas equipment "format" | > In the PSI muSR laboratory, we are running
about 140 slow control devices across six
instruments using Format FIXED.
|
|
|
2999
|
25 Mar 2025 |
Konstantin Olchanski | Bug Report | manalyzer module init order problem | > Andrea Capra reported a problem with manalyzer
module initialization order.
|
|
|
3002
|
25 Mar 2025 |
Konstantin Olchanski | Bug Report | please fix compiler warning | Confirming warning is fixed. Thanks! K.O.
> > Unnamed person who added this clever |
|
|
3003
|
25 Mar 2025 |
Konstantin Olchanski | Bug Report | please fix mscb compiler warning | > I hopefully fixed the waring (narrowing
down from size_t to int). Please double check
with your compiler.
|
|
|
3004
|
25 Mar 2025 |
Konstantin Olchanski | 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
|
|
|
3012
|
01 Apr 2025 |
Pavel Murat | Bug Report | MIDAS history system not using the event timestamps ? | Dear MIDAS experts,
I confirm that when writing out history files |
|
|
3018
|
01 Apr 2025 |
Konstantin Olchanski | Bug Report | ODB corruption | We see ODB corruption crashes in the DS20k
vertical slice MIDAS instance.
|
|
|
3020
|
01 Apr 2025 |
Konstantin Olchanski | Bug Report | MIDAS history system not using the event timestamps ? | > I confirm that when writing out history
files corresponding to the slow control event
data,
|
|
|
3022
|
02 Apr 2025 |
Pavel Murat | Bug Report | MIDAS history system not using the event timestamps ? | > You can always include your "true" data
timestamp as the first value in your data.
|
|