At 3:03 PM -0400 2006/04/14, Brian McAllister wrote:
> 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...
I did not mean to imply HYST=0. In fact, I always set it
appropriately for electronic noise and digitization artifacts. The
filter is most useful for occasional, random excursions. And, yes,
NOACKT is usually the right choice for these types of signals.
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.
Agreed: sufficient false positives will always result in defeat of
the system. I like your visual fix as well.
- References:
- Re: AlarmHandler - filtering vs. HYST Brian McAllister
- Navigate by Date:
- Prev:
Re: AlarmHandler - filtering vs. HYST Brian McAllister
- Next:
Re: AlarmHandler - filtering vs. HYST Maren Purves
- Index:
1994
1995
1996
1997
1998
1999
2000
2001
2002
2003
2004
2005
<2006>
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
- Navigate by Thread:
- Prev:
Re: AlarmHandler - filtering vs. HYST Brian McAllister
- Next:
Re: AlarmHandler - filtering vs. HYST Maren Purves
- Index:
1994
1995
1996
1997
1998
1999
2000
2001
2002
2003
2004
2005
<2006>
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
|