|
Back
Midas
Rome
Roody
Rootana
|
Midas DAQ System |
Not logged in |
 |
|
12 Dec 2024, Stefan Ritt, Suggestion, New alarm sound flag to be tested
|
19 Dec 2024, Stefan Ritt, Suggestion, New alarm count added
|
20 Mar 2025, Konstantin Olchanski, Suggestion, BINARY INCOMPATIBLE CHANGE: New alarm count added
|
21 Mar 2025, Stefan Ritt, Suggestion, BINARY INCOMPATIBLE CHANGE: New alarm count added
|
21 Mar 2025, Konstantin Olchanski, Suggestion, BINARY INCOMPATIBLE CHANGE: New alarm count added
|
|
Message ID: 2994
Entry time: 21 Mar 2025
In reply to: 2980
|
Author: |
Konstantin Olchanski |
Topic: |
Suggestion |
Subject: |
BINARY INCOMPATIBLE CHANGE: New alarm count added |
|
|
> > > ALL MIDAS CLIENTS GET RE-COMPILED after the new code is applied.
>
> - I did clearly announce this change in the forum.
>
I missed the announcement and I was surprised to discover this change.
This is why I changed the title from "useful improvement" to "ACHTUNG!!!"
> - The extension is not there "just for fun" but needed by several experiments which experience spurious alarms
> triggered by some noisy signals.
Agreed, a useful improvement.
To prevent this kind of trouble in the future, I think I should finish my crusade against db_get_record().
> - If there are frontend programs which have not been re-compiled for ten years, I think it is very unlikely that these
> experiments need the latest cutting edge version of midas. The can safely stick to your tag midas-2024-12-a and not
> experience the issue of different /Alarm trees.
Yes, now that I added the tag, posted a more visible notice and people who have to run frontends build against older midas
(because reasons) can breathe out.
Also please note that "Konstantin != all experiments at TRIUMF".
K.O. |