Changes between Initial Version and Version 1 of Ticket #592, comment 38


Ignore:
Timestamp:
Jun 2, 2014, 4:13:08 PM (8 years ago)
Author:
olle
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #592, comment 38

    initial v1  
    11Design update of alarm blocking:
    22
    3 An alarm can be reported either when a lab environment value (temperature or humidity) is out of range, or when contact is lost with a lab sensor (missing data). Currently, a reported alarm blocks further alarms for that alarm configuration, irrespective of what caused the alarm. However, if contact is re-established with a lab sensor after a missing data alarm, alarms of lab environment variables being out of range for that sensor should have higher priority and result in a reported alarm, even if the previous missing data alarm had not been re-set manually. This can be implemented as follows:
     3An alarm can be reported either when a lab environment value (temperature or humidity) is out of range, or when contact is lost with a lab sensor (missing data). Currently, a reported alarm blocks further alarms for that alarm configuration, irrespective of what caused the alarm. However, if contact is re-established with a lab sensor after a missing data alarm, alarms for lab environment variables being out of range for that sensor should have higher priority and result in a reported alarm, even if the previous missing data alarm had not been re-set manually. This can be implemented as follows:
    44
    55 1. Data access object `LabSensorAlarmConfig.java` in `src/net/sf/basedb/labenv/dao/` updated:[[BR]]a. Three new public static final integer constants `ALARM_BLOCK_TYPE_UNKNOWN`, `ALARM_BLOCK_TYPE_MISSING_DATA`, and `ALARM_BLOCK_TYPE_LAB_ENVIRONMENT_DATA` are defined.[[BR]]b. New private instance variable `Integer alarmBlockType` with public accessor methods added. It is initialized to `null`.