Uploaded image for project: 'Data Management'
  1. Data Management
  2. DM-32495

Add watcher configuration for dew point, humidity, and over-temp for one hexapod

    XMLWordPrintable

    Details

    • Type: Story
    • Status: Done
    • Resolution: Done
    • Fix Version/s: None
    • Component/s: None
    • Labels:

      Description

      Update summit watcher configuration with one humidity rule and one dew point rule for each telescope (or maybe just one humidity period) and an over-temperature rule for the one MT hexapod that has thermal sensors on the struts.

      See https://confluence.lsstcorp.org/display/LTS/ESS+CSC+Index+Registry for ESS sensor information.

        Attachments

          Issue Links

          is triggered by

          Story - Created by Jira Software - do not edit or delete. Issue type for a user story. DM-32453 Add a Watcher alarm for MT Hexapod temperature.

          • Done
          is triggering

          Story - Created by Jira Software - do not edit or delete. Issue type for a user story. DM-32270 Release my packages awaiting ts_xml 10.1

          • Done

            Activity

            Ascending order - Click to sort in descending order
            Hide
            Permalink
            rowen Russell Owen added a comment - - edited

            The new ESS rules are all polling rules. I was not sure how often to poll, but chose 10 seconds as a reasonable compromise between polling far more often than new data arrives, and having a long delay after new data arrives. What is the interval between updates for the temperatures and humidity/dew-point sensors? If it is very different than 60 seconds, then max_data_age should probably be changed from 180 seconds. I wanted the rules to have a chance to miss 1 or maybe 2 updates (e.g. due to restarting an ESS) but not much more than that. If too short then we'll get false alarms. If too long then we wait needlessly long before realizing the Watcher isn't getting the data it needs.

            Pull request: https://github.com/lsst-ts/ts_config_ocs/pull/42

            Show
            rowen Russell Owen added a comment - - edited The new ESS rules are all polling rules. I was not sure how often to poll, but chose 10 seconds as a reasonable compromise between polling far more often than new data arrives, and having a long delay after new data arrives. What is the interval between updates for the temperatures and humidity/dew-point sensors? If it is very different than 60 seconds, then max_data_age should probably be changed from 180 seconds. I wanted the rules to have a chance to miss 1 or maybe 2 updates (e.g. due to restarting an ESS) but not much more than that. If too short then we'll get false alarms. If too long then we wait needlessly long before realizing the Watcher isn't getting the data it needs. Pull request: https://github.com/lsst-ts/ts_config_ocs/pull/42
            Hide
            Permalink
            wvreeven Wouter van Reeven added a comment -

            How often a sensor sends data depends on the type of sensor and, in case of the temperature sensor, on the amount of temperature probes attached. But new data may be expected at least once every 2 seconds. The data in the EFD should give a good indication of this.

            Show
            wvreeven Wouter van Reeven added a comment - How often a sensor sends data depends on the type of sensor and, in case of the temperature sensor, on the amount of temperature probes attached. But new data may be expected at least once every 2 seconds. The data in the EFD should give a good indication of this.
            Hide
            Permalink
            wvreeven Wouter van Reeven added a comment -

            Reviewed in GitHub.

            Show
            wvreeven Wouter van Reeven added a comment - Reviewed in GitHub.
            Hide
            Permalink
            rowen Russell Owen added a comment -

            Updated as per reviewer suggestions. Merged to develop. Release awaits ts_xml 10.1 (see DM-32270)

            Show
            rowen Russell Owen added a comment - Updated as per reviewer suggestions. Merged to develop. Release awaits ts_xml 10.1 (see DM-32270 )
            Hide
            Permalink
            rowen Russell Owen added a comment -

            Thanks! If all data appears at least once every 2 seconds then I withdraw any suggestion to document the rate as comments in the yaml file.

            Show
            rowen Russell Owen added a comment - Thanks! If all data appears at least once every 2 seconds then I withdraw any suggestion to document the rate as comments in the yaml file.

              People

              Assignee:
              rowen Russell Owen
              Reporter:
              rowen Russell Owen
              Reviewers:
              Wouter van Reeven
              Watchers:
              Russell Owen, Wouter van Reeven
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:

                  Jenkins

                  No builds found.