ISISComputingGroup / ISISComputingGroup/IBEX

[Alarms]: Alarms should consider multiple states to flag actual alarm state

Open
#8,649 1 comment 0 reactions 0 assignees View on GitHub
Dominant language
No language data
Stars
6
Forks
2
Avg merge
16h 40m
Merged PRs (30d)
2

Description

# Issue Description
As an instrument scientist I would like to see that the system understands that different alarm states can be combined in some cases to get the real alarm situation. For example, in case of multiple temperature sensors, while one sensor is expected to be lesser than the threshold and the other is more than the threshold, but it errors out because it considers the one lesser than the limit as in error (but it is exactly how it was needed to be)

Similarly some IOCs start up with inappropriate alarm limits for the instrument they’re used on, e.g. the TPG300 pressure gauge considers “under-range” on the Pirani sensors as an error when this is a perfectly normal situation on RIKENFE

### How & Where?
- Various instruments

### Reproducible (Yes/No)?
Yes

### Additional Information
1. We need to collate which IOCs need such special consideration
2. We need to see whether same PVs but in different IOCs of same type can be at all combined together - that is technical feasibility of such a behaviour

# Acceptance Criteria
1. Minimal set of PVs are identified which need combinatorial logic to determine "real" alarm state.
2. Technical feasibility of such an implementation is established may be by means of a POC.
3. The approach is defined and new ticket is created for implementation if it is feasible.

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.