You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When both an incite and suppress override are set simultaneously we may want to automatically cancel the incite override. The latched and one-shot overrides are particularly clumsy to combine. When ops requests one-shot shelved they are effectively asking to ignore the current annunciation (or next if currently Normal) of an alarm, but when combined with latching the result is that ops still must ack. One work-around is client software can simply always send an ack with a one-shot shelve request (though this only works if alarm in question is currently Active). We may need to consider other combinations of overrides as well, like off-delayed and on-delayed, which may make a confusing experience.
The text was updated successfully, but these errors were encountered:
There are also implications for caching as it turns out JLab alarms in practice are often actively alarming when they really are "not in use". This means caches of overrides often contain useless Latched overrides for alarms that are supposed to be filtered out anyways. So if filtered out, Latches should probably be dropped to keep caches clear of useless info.
When both an incite and suppress override are set simultaneously we may want to automatically cancel the incite override. The latched and one-shot overrides are particularly clumsy to combine. When ops requests one-shot shelved they are effectively asking to ignore the current annunciation (or next if currently Normal) of an alarm, but when combined with latching the result is that ops still must ack. One work-around is client software can simply always send an ack with a one-shot shelve request (though this only works if alarm in question is currently Active). We may need to consider other combinations of overrides as well, like off-delayed and on-delayed, which may make a confusing experience.
The text was updated successfully, but these errors were encountered: