Uploaded image for project: 'SAFe Program'
  1. SAFe Program
  2. SP-2703

Configuration of SDP Tango attribute archiving (& alarms)

Change Owns to Parent OfsSet start and due date...
    XporterXMLWordPrintable

Details

    • Feature
    • Should have
    • PI16
    • COM SDP SW
    • None
    • Data Processing
    • Hide

      Storing Tango device attribute values in the Engineering Data Archive (EDA) allows users of the system to inspect the history of the attributes. Setting alarms on attributes allows problems to be brought to the attention of users. Enabling archiving of SDP attributes contributes to the development of the EDA and the associated user experience.

      Show
      Storing Tango device attribute values in the Engineering Data Archive (EDA) allows users of the system to inspect the history of the attributes. Setting alarms on attributes allows problems to be brought to the attention of users. Enabling archiving of SDP attributes contributes to the development of the EDA and the associated user experience.
      • SDP Helm chart configures archiving (and alarms, if feasible) on Tango device attributes.
      • Documentation updated to describe parameters controlling archiving (and alarms).
    • Inter Program, Intra Program
    • 1
    • 1
    • 0

    • Sub-system Version REL-191 SDP 0.13.0

    • Team_ORCA
    • Sprint 5
    • Hide

      The feature was demoed at System Demo 16.5.

      Slides: https://docs.google.com/presentation/d/10DH5DrscxTdpQ8LArpwSBO0hWfaRQpkzEry4kfaq6Ec/edit?usp=drive_web&ouid=100779536194539257799

      Tango attribute archiving:

      Archiving and change events on the SDP Subarray device attributes have enabled. Changes in code are:

      Confluence page with summary of discussions and examples of how one can poll these events using itango and get notified when they happen: https://confluence.skatelescope.org/display/SE/Tango+attribute+archiving

      The LMC documentation has also been updated: https://developer.skao.int/projects/ska-sdp-lmc/en/latest/sdp-subarray.html#tango-events

      Attribute archiving is automatic and does not have to be set in the Helm chart explicitly. It is the responsibility of the client (e.g. itango, Engineering Data Archive) to subscribe to these events and use them.

      Tango attribute alarms:

      We analyzed means of setting alarms on tango attributes and provided suggestions of what alarms would be worth setting on the Subarray device. This work is documented on Confluence: https://confluence.skatelescope.org/display/SE/Tango+Attribute+Alarms

       

      Show
      The feature was demoed at System Demo 16.5. Slides: https://docs.google.com/presentation/d/10DH5DrscxTdpQ8LArpwSBO0hWfaRQpkzEry4kfaq6Ec/edit?usp=drive_web&ouid=100779536194539257799 Tango attribute archiving: Archiving and change events on the SDP Subarray device attributes have enabled. Changes in code are: change events: https://gitlab.com/ska-telescope/sdp/ska-sdp-lmc/-/blob/master/src/ska_sdp_lmc/subarray/device.py#L106 archive events: https://gitlab.com/ska-telescope/sdp/ska-sdp-lmc/-/blob/master/src/ska_sdp_lmc/subarray/device.py#L115 push mechanism to push these events, which then can be polled by a client, e.g. for obsState: https://gitlab.com/ska-telescope/sdp/ska-sdp-lmc/-/blob/master/src/ska_sdp_lmc/subarray/device.py#L581 Confluence page with summary of discussions and examples of how one can poll these events using itango and get notified when they happen: https://confluence.skatelescope.org/display/SE/Tango+attribute+archiving The LMC documentation has also been updated: https://developer.skao.int/projects/ska-sdp-lmc/en/latest/sdp-subarray.html#tango-events Attribute archiving is automatic and does not have to be set in the Helm chart explicitly. It is the responsibility of the client (e.g. itango, Engineering Data Archive) to subscribe to these events and use them. Tango attribute alarms: We analyzed means of setting alarms on tango attributes and provided suggestions of what alarms would be worth setting on the Subarray device. This work is documented on Confluence: https://confluence.skatelescope.org/display/SE/Tango+Attribute+Alarms  
    • 16.5
    • Stories Completed, Integrated, Outcomes Reviewed, Demonstrated, Satisfies Acceptance Criteria, Accepted by FO

    • PI24 - UNCOVERED

    • DP-SDP: G1

    Description

      Introduction

      In order to be able to inspect the history of key Tango attributes exposed in the control system, we need to provide a configuration of SDP Tango device services which sets default attribute properties related to archiving to configure the initial state of the Tango Database (e.g. via dsconfig).

      If time allows, also exposing an initial default configuration of Tango attribute alarms on SDP devices should be investigated as this will also be needed in the near future and the belief is that setting attribute archiving and alarms can be done via similar mechanisms. 

      This contributes directly to SS-103 which will enable and deploy the Engineering Data Archive (EDA) for archiving and inspecting the historical state of the telescope. Most of the development of the EDA is expected to be led by the OMC ART but once deployed testing with archived attributed a small selection of sub-systems (e.g. SDP) will help drive future development of this service and the related UX.

      References

      1. https://pytango.readthedocs.io/en/v9.3.4/server_api/attribute.html?highlight=set_archive_event_period#userdefaultattrprop
      2. https://confluence.skatelescope.org/display/SWSI/ADR-61+AA0.5+EDA+Design+and+Deployment
      3. https://confluence.skatelescope.org/display/SE/2022-07-29+Architecture+Sync+Meeting+-+EDA+design+and+deployment
      4. https://tango-controls.readthedocs.io/en/latest/development/device-api/attribute-alarms.html

       
      Who?

      • Control system developers
      • AIV engineers

      What?

      See acceptance criteria.

      Why?

      See benefit hypothesis.

      Attachments

        Issue Links

          Child Of

          Capability - SAFe program capability SS-103 Archiving and visualising engineering parameters with the EDA

          • Must have - Items labelled as "Must have" are critical to the current delivery timebox in order for it to be a success.
          • Done
          Is delivered by

          Sub-system Version - A version of a sub-system, used in the Release Management and Configuration Management process REL-191 SDP 0.13.0

          • Released
          mentioned in

          Page Loading...

          Page Loading...

          Page Loading...

          Page Loading...

          Page Loading...

          Page Loading...

          Structure

            Activity

              People

                m.ashdown Ashdown, Mark
                b.mort Mort, Ben
                Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                Feature Progress

                  Story Point Burn-up: (100.00%)

                  Feature Estimate: 1.0

                  IssuesStory Points
                  To Do00.0
                  In Progress   00.0
                  Complete714.5
                  Total714.5

                  Dates

                    Created:
                    Updated:
                    Resolved:

                    Structure Helper Panel