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

Basic Subarray Resource Allocation for TMC Mid

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

Details

    • Obs Mgt & Controls
    • Hide

      The basic setup of a subarray so that control over an observation can be made; is working and can be used as a means for downstream flow behavior to configure and run a telescope.

      Show
      The basic setup of a subarray so that control over an observation can be made; is working and can be used as a means for downstream flow behavior to configure and run a telescope.
    • Hide

      A set of passing BDD tests for switching on and assigning resources; reflected on a Jira test in XRAY, and traced back to the Execute Observation Use Case.

      A documented API that ensures a client has all the necessary information to switch on telescope elements and assign resources to a subarray.

      Show
      A set of passing BDD tests for switching on and assigning resources; reflected on a Jira test in XRAY, and traced back to the Execute Observation Use Case. A documented API that ensures a client has all the necessary information to switch on telescope elements and assign resources to a subarray.
    • 2
    • 2
    • 40
    • 20

    • Flow USE-39 Operate and Monitor MID Telescope - Basic Flow

    • System Version REL-92 SKA-MID-MVP v0.1.0-experiment

    • Team_SAHYADRI
    • Sprint 2
    • Hide

       

      Show
      A new version of TMC is integrated into SKAMPI ( https://gitlab.com/ska-telescope/ska-skampi/-/merge_requests/670) TelescopeOn/Off and Assign/ReleaseResources commands are successfully tested for about 9000 times.  
    • 19.6
    • Stories Completed, Integrated, Outcomes Reviewed, Demonstrated, Accepted by FO

    • PI24 - NOTRUN

    • Team_HIMALAYA Team_NCRA Team_SAHYADRI

    Description

      Deliver the basic (but verified/validated and fully documented) observational control functionality for TMC (in the Mid telescope) allowing for

      1) Setting devices to the appropriate running state

      2) the allocation of resources to a subarray (EMPTY->IDLE)

      In particular, this feature shall depend on the necessary refactoring work to ensure the CSP Leaf node is in line with changes to the TMC Central Node (see https://jira.skatelescope.org/browse/SP-2285)

      Note the basic flow does not currently have to allow for failure scenarios but the design and implementation should ensure that this functionality can be added iteratively without requiring re-design or changes.

      This Feature subsumes part of the original features below:

      https://jira.skatelescope.org/browse/SP-1687

      https://jira.skatelescope.org/browse/SP-2115

       

      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-90 Reintegrate missing components into SKAMPI

          • Must have - Items labelled as "Must have" are critical to the current delivery timebox in order for it to be a success.
          • 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-2285 Refactor TMC CSP Leaf Nodes in line with the Central Node (SS-82 follow on)

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

          System Version - System releases - ie MID, LOW SW. Configured releases of SKAMPI REL-92 SKA-MID-MVP v0.1.0-experiment

          • Discarded
          relates to

          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-1687 Refactor Test Cases for TMC code refactoring

          • Should have - Items labelled as "Should have" are important but not necessary for delivery in the current delivery timebox. While "Should have" items can be as important as "Must have", they are often not as time-critical or there may be another way to satisfy the requirement so that it can be held back until a future delivery timebox.
          • Discarded

          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-2115 Integration and regression testing of the TMC MVP post SS-82; Identify bugs to be fixed

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

          Page Loading...

          Page Loading...

          Page Loading...

          Page Loading...

          Page Loading...

          Page Loading...

          Structure

            Activity

              People

                g.leroux Le Roux, Gerhard [X] (Inactive)
                g.leroux Le Roux, Gerhard [X] (Inactive)
                Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Feature Progress

                  Story Point Burn-up: (100.00%)

                  Feature Estimate: 2.0

                  IssuesStory Points
                  To Do00.0
                  In Progress   00.0
                  Complete1024.0
                  Total1024.0

                  Dates

                    Created:
                    Updated:
                    Resolved:

                    Structure Helper Panel