| ID |
Date |
Author |
Topic |
Subject |
Text |
 |
|
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.
|
|
|
3023
|
02 Apr 2025 |
Konstantin Olchanski | 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.
>
|
|
|
170
|
22 Oct 2004 |
Konstantin Olchanski | Bug Fix | mhttpd message colouring | I commited a fix to mhttpd logic that decides
which messages should be shown in
"red" colour- before, any message with square |
|
|
174
|
09 Nov 2004 |
Pierre-Andre Amaudruz | Bug Fix | New transition scheme | Problem:
If cm_set_transition_sequence() is used for
changing the sequence number, the
|
|
|
200
|
25 Feb 2005 |
Konstantin Olchanski | Bug Fix | fixed: double free in FORMAT_MIDAS ybos.c causing lazylogger crashes | We stumbled upon and fixed a "double free"
bug in src/ybos.c causing crashes in
lazylogger writing .mid files in the FORMAT_MIDAS |
|
|
211
|
05 May 2005 |
Konstantin Olchanski | Bug Fix | fix: minor bit rot in the example experiment | I fixed some minor bit rot in the example
experiment: a few minor Makefile
problems, make the analyzer use the current |
|
|
212
|
02 Aug 2005 |
Konstantin Olchanski | Bug Fix | fix odb corruption when running analzer for the first time | I have been plagued by ODB corruption when
I run the analyzer for the first time
after setting up the new experiment. Some |
|
|
216
|
18 Aug 2005 |
Konstantin Olchanski | Bug Fix | fix race condition between clients on run start/stop, pause/resume | It turns out that the new priority sequencing
of run state transitions had a
flaw: the frontends, the analyzer and the |
|
|
219
|
01 Sep 2005 |
Stefan Ritt | Bug Fix | fix race condition between clients on run start/stop, pause/resume | > It turns out that the new priority sequencing
of run state transitions had a
> flaw: the frontends, the analyzer and the |
|
|
229
|
17 Oct 2005 |
Exaos Lee | Bug Fix | "make install" error under MacOS X | Under MacOS X, "make install" will cours an
error like this:
[code]
|
|
|
235
|
23 Nov 2005 |
Stefan Ritt | Bug Fix | Endian swapping in mana.c | It was reported that following code in mana.c
:
|
|