> Steve Lewis wrote:
>> Try this (one of the best features of ALH): use
>> $ALARMCOUNTFILTER count seconds
This will help you, but (IMO) the best solution for any alarm hovering
around a transition value is almost always to set HYST appropriately in the
record.
...snip...
Based on personal experience I can state that any significant number of
"nuisance" alarms will lead to users becoming less reactive to real alarms.
We were having enough issues with operators silencing ALH "forever" (so
they wouldn't be annoyed by "false" alarms) that I modified ALH to put a
black border around the button on the screen so you could tell it was
silenced without opening the alarm window.