| ID |
Date |
Author |
Topic |
Subject |
Text |
 |
|
2921
|
12 Dec 2024 |
Stefan Ritt | Suggestion | New alarm sound flag to be tested | We had the case in MEG that some alarms were
actually just warnings, not very severe.
This happens for example if we calibrate |
|
|
2924
|
19 Dec 2024 |
Stefan Ritt | Bug Report | [History plots] "Jump to current time" resets x range to 7d | I had put in a check which limits the range
to 7d into the past if you press the "play"
button, but now I'm not sure why this was |
|
|
2925
|
19 Dec 2024 |
Stefan Ritt | Suggestion | New alarm count added | Another modification has been done to the
alarm system.
|
|
|
2929
|
05 Jan 2025 |
Stefan Ritt | Forum | time ordering of run transition calls to TMFeEquipment things | Hi Pavel,
have you looked into
|
|
|
2931
|
09 Jan 2025 |
Stefan Ritt | Suggestion | improved find_package behaviour for Midas | After some iterations, we merged the branch
with the new build scheme. Now you can compile
any midas program as described at
|
|
|
2944
|
24 Feb 2025 |
Stefan Ritt | Bug Report | Default write cache size for new equipments breaks compatibility with older equipments | The commit that introduced the write cache
size check is https://bitbucket.org/tmidas/midas/commits/3619ecc6ba1d29d74c16aa6571e40920018184c0
|
|
|
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
|
|
|
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.
>
|
|
|
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 |
|
|
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
|
|
|
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.
|
|
|
2990
|
21 Mar 2025 |
Stefan Ritt | Forum | LabView-Midas interface | > Hello,
>
> Does anyone have experience with writing |
|
|
3015
|
01 Apr 2025 |
Stefan Ritt | Suggestion | Sequencer ODBSET feature requests | A new sequencer which understands Python is
in the works. There you can use all features
from that language.
|
|
|
3016
|
01 Apr 2025 |
Stefan Ritt | Suggestion | Sequencer ODBSET feature requests | The extended ODBSET[x,y1-y2,z] could make
sense to be implemented, since it then will
match the alarm system which uses the same |
|
|
3025
|
02 Apr 2025 |
Stefan Ritt | Suggestion | Sequencer ODBSET feature requests | And there is one more argument:
We have a Python expert in our development |
|
|
3027
|
07 Apr 2025 |
Stefan Ritt | Suggestion | Sequencer ODBSET feature requests | If people are simultaneously editing scripts
this is indeed an issue, which probably never
can be resolved by technical means. It need |
|
|
3031
|
30 Apr 2025 |
Stefan Ritt | Info | New ODB++ API | I had to change the ODBXX API: https://bitbucket.org/tmidas/midas/commits/273c4e434795453c0c6bceb46bac9a0d2d27db18
The old C API is case-insensitive, meaning |
|
|
3033
|
30 Apr 2025 |
Stefan Ritt | Bug Report | ODBXX : ODB links in the path names ? | Indeed this was missing from the very beginning.
I added it, please report back if it's not
working.
|
|
|
3037
|
05 May 2025 |
Stefan Ritt | Bug Report | abort and core dump in cm_disconnect_experiment() | I would be in favor of not curing the symptoms,
but fixing the cause of the problem. I guess
you put the watchdog disable into mhist, |
|
|
3038
|
05 May 2025 |
Stefan Ritt | Info | db_delete_key(TRUE) | I would handle this actually like symbolic
links are handled under linux. If you delete
a symbolic link, the link gets
|
|