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

TANGO Base Class Controller implements long-running commands that trigger operational state transitions

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

Details

    • Obs Mgt & Controls
    • Hide

      In many cases, operational state transitions, such as On(), Off() and Standby() cannot be executed instantaneously.  The TMC Central Node and leaf nodes, as well as the sub-system masters and other software components coordinating state transitions of other components/devices will be gradually turning on or off the devices they control in order to control inrush current and other aspects of the telescope; therefore those commands must be implemented as non-blocking. Even in a simulated environment, where all M&C software runs on the same cluster, blocking command calls result in failures. 

      SKA Base Class Master Controller is used as a base for many other components which will inherit this implementation.

      Show
      In many cases, operational state transitions, such as On(), Off() and Standby() cannot be executed instantaneously.  The TMC Central Node and leaf nodes, as well as the sub-system masters and other software components coordinating state transitions of other components/devices will be gradually turning on or off the devices they control in order to control inrush current and other aspects of the telescope; therefore those commands must be implemented as non-blocking. Even in a simulated environment, where all M&C software runs on the same cluster, blocking command calls result in failures.  SKA Base Class Master  Controller is used as a base for many other components which will inherit this implementation.
    • Hide

      Commands On(), Off(), and Standby() implemented as asynchronous commands.

      A set of attributes to report state of command execution implemented (see description).

       

      Show
      Commands On(), Off(), and Standby() implemented as asynchronous commands. A set of attributes to report state of command execution implemented (see description).  
    • 1
    • 1
    • 40
    • 40
    • Team_KAROO
    • Sprint 4
    • Hide

      SKA base controller On, Off, and Standby commands implemented as asynchronous commands

      Show
      SKA base controller On, Off, and Standby commands implemented as asynchronous commands
    • 12.6
    • Stories Completed, Solution Intent Updated, Outcomes Reviewed, Demonstrated, Satisfies Acceptance Criteria, Accepted by FO

    • PI24 - UNCOVERED

    • Cross_Team_Code_Review SS-54

    Description

      The goal is to implement commands: On(), Off(), Standby() as long-running commands, meaning that the caller does not get blocked waiting for the command to be executed.  The control should be returned to the caller within few milliseconds. The progress of the command execution is tracked by additional attributes, and the completion of the command reported as a state transition (event). (Off course, the Client may choose to poll the attribute state).

      Detailed design for each command is still in progress (state transitions and command sequencing).

       

      Attachments

        Issue Links

          Child Of

          Enabler - An Enabler supports the activities needed to extend the Architectural Runway to provide future business functionality. These include exploration, architecture, infrastructure, and compliance. SS-54 Review of Control Systems guidelines and refactoring of implementation

          • Not Assigned - Priority is not assigned yet.
          • Done
          depends on

          Enabler - An Enabler supports the activities needed to extend the Architectural Runway to provide future business functionality. These include exploration, architecture, infrastructure, and compliance. SP-1640 Reference design and implementation for asynchronous (long-running) commands

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

          Enabler - An Enabler supports the activities needed to extend the Architectural Runway to provide future business functionality. These include exploration, architecture, infrastructure, and compliance. SP-1827 Update TANGO Base Classes to handle long running commands

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

          Feature - A Feature is a service that fulfills a stakeholder need. Each feature includes a benefit hypothesis and acceptance criteria, and is sized or split as necessary to be delivered by a single Agile Release Train (ART) in a Program Increment (PI). SP-1984 MCCS adoption of long running command implementation in the tango_base_classes

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

          Architectural Decision - Software Architectural Decision ADR-47 Guidelines for implementation of commands

          • decided
          is required by

          Feature - A Feature is a service that fulfills a stakeholder need. Each feature includes a benefit hypothesis and acceptance criteria, and is sized or split as necessary to be delivered by a single Agile Release Train (ART) in a Program Increment (PI). SP-2077 Refactor and release long running command implementation in ska-tango-base

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

          Enabler - An Enabler supports the activities needed to extend the Architectural Runway to provide future business functionality. These include exploration, architecture, infrastructure, and compliance. SP-1630 SKA Base Class Master - abort command execution

          • Not Assigned - Priority is not assigned yet.
          • Discarded
          relates to

          Spike - A time limited investigation to get some knowledge SP-1794 TMC asynchronous communication

          • Could have - Items labelled as "Could have" are desirable but not necessary and could improve the user experience or customer satisfaction for a little development cost. These will typically be included if time and resources permit.
          • Done
          mentioned in

          Page Loading...

          Page Loading...

          Page Loading...

          Page Loading...

          Page Loading...

          Page Loading...

          Page Loading...

          Page Loading...

          Structure

            Activity

              People

                s.vrcic Vrcic, Sonja
                s.vrcic Vrcic, Sonja
                Votes:
                0 Vote for this issue
                Watchers:
                2 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
                  Complete10.5
                  Total10.5

                  Dates

                    Created:
                    Updated:
                    Resolved:

                    Structure Helper Panel