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

Implement full subarray beam configuration and control (allocate/release, configure, scan, etc)

    XporterXMLWordPrintable

Details

    • Obs Mgt & Controls
      • implementation of revisions above
      • demo of resource management in beams
      • update of confluence documentation
    • 3
    • 5
    • 7
    • Team_MCCS
    • Sprint 5
    • Hide

      This feature has had to be significantly descoped with many of the desired areas of subarray beam implementation not progressing as hoped. Early in PI10 a number of clarifications were needed in the area of subarray, stattion and station beam management within MCCS. These were established, but we then began to encouter issues which prevented the implemented code from passing the CI pipeline integration tests. To assist in overcoming these problems MCCS implemented a message queue as well as investigating the possible use of Tango Groups.

      • Update of confluence documentation
        We have been able to update the Confluence documentation on the Station Beam device and the subarray hieracrhy is now captured in class diagram form:
      • Implementation of revisions above
        Not achieved, but aim to fulfil through SP-1645
      • Demo of resource management in beams
        Not achieved, but aim to fulfil through SP-1645
      Show
      This feature has had to be significantly descoped with many of the desired areas of subarray beam implementation not progressing as hoped. Early in PI10 a number of clarifications were needed in the area of subarray, stattion and station beam management within MCCS. These were established, but we then began to encouter issues which prevented the implemented code from passing the CI pipeline integration tests. To assist in overcoming these problems MCCS implemented a message queue as well as investigating the possible use of Tango Groups. Update of confluence documentation We have been able to update the Confluence documentation on the Station Beam device and the subarray hieracrhy is now captured in class diagram form: https://confluence.skatelescope.org/display/SE/Beam+Classes%2C+Assignment+and+Configuration Implementation of revisions above Not achieved, but aim to fulfil through SP-1645 Demo of resource management in beams Not achieved, but aim to fulfil through SP-1645
    • 10.6
    • Stories Completed, Outcomes Reviewed, NFRS met, Satisfies Acceptance Criteria, Accepted by FO

    Description

      Clone of the PI#9 depending on clarifying beam architecture

      • StationsResourceManager - move it from Subarray into Controller
        • It also needs changing so that ownership is not exclusive
      • StationBeamsResourceManager - move it from Subarray into Controller
        • There is no reason to tie the beam devices to one subarray, other than because their resource management is closely tied to the resource management of stations
      • SubarrayBeamsResourceManager - needed to manage a pool of SubarrayBeam devices.
      • Implement Controller.Allocate with new architecture
      • Implement health roll-up StationBeam →SubarrayBeam →Subarray
      • Resource management of Channels within Station
        • Reserve channel capacity in response to Allocate()
        • Assemble channel configuration in response to Configure()
        • From this we will pass config to Tile
        • Beam ids must then be matched back (to StationBeam presumably) and made available (in Subarray?) to TM.
      • Implement Scan()
        • Implies we work on PointingJob in some manner

      Attachments

        Issue Links

          is cloned 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-1645 Implement full subarray beam configuration and control (allocate/release, configure, scan, etc) PI11 CLONE

          • Must have - Items labelled as "Must have" are critical to the current delivery timebox in order for it to be a success.
          • Done
          supported 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-1458 Updates to the Antenna device

          • Not Assigned - Priority is not assigned yet.
          • Done
          mentioned in

          Page Loading...

          Page Loading...

          Page Loading...

          Structure

            Activity

              People

                a.bridger Bridger, Alan
                r.braddock Braddock, Ralph
                Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Feature Progress

                  Story Point Burn-up: (100.00%)

                  Feature Estimate: 3.0

                  IssuesStory Points
                  To Do00.0
                  In Progress   00.0
                  Complete34.5
                  Total34.5

                  Dates

                    Created:
                    Updated:
                    Resolved:

                    Structure Helper Panel