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

Define an API for TMC.LOW to MCCS Interaction

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

Details

    • Obs Mgt & Controls
      • Allows the creation of an MCCS emulator, against which TMC.LOW and other subsystems can progress
      • Enables continued development of TMC.LOW and earlier integration into SKAMPI of TMC MCCS leaf nodes.
    • Hide
      • A basic API for interaction between TMC.LOW and MCCS is created.
      • API mimics as closely as possible the current best understanding of expected MCCS behaviour for TMC interaction.
      • Allows in the first instance the ability for the TMC to switch the MCCS On/Off.
      Show
      A basic API for interaction between TMC.LOW and MCCS is created. API mimics as closely as possible the current best understanding of expected MCCS behaviour for TMC interaction. Allows in the first instance the ability for the TMC to switch the MCCS On/Off.
    • 1
    • 1
    • 3
    • 3
    • Team_MCCS
    • Sprint 5
    • Hide

      API documentation has been updated. Principally this has meant updating the schemas describing the JSON passed to commands. All commands taking JSON arguments are now being validated against these schemas. Also the Configure command / schema was extended to accept a transaction ID for logging / metadata purposes.

      A workshop was held under this feature to discuss power sequencing within MCCS (SPS and PaSD). Documentation planned to follow this is being deferred for now.

      Confluence page describing the interface

      Subarray definition in MCCS - PDF

      Schemas GitLab link: https://gitlab.com/ska-telescope/mccs/ska-low-mccs/-/tree/main/src/ska_low_mccs/schemas?ref_type=heads

      Confluence page giving these schemas

      Show
      API documentation has been updated. Principally this has meant updating the schemas describing the JSON passed to commands. All commands taking JSON arguments are now being validated against these schemas. Also the Configure command / schema was extended to accept a transaction ID for logging / metadata purposes. A workshop was held under this feature to discuss power sequencing within MCCS (SPS and PaSD). Documentation planned to follow this is being deferred for now. Confluence page describing the interface Subarray definition in MCCS - PDF Schemas GitLab link: https://gitlab.com/ska-telescope/mccs/ska-low-mccs/-/tree/main/src/ska_low_mccs/schemas?ref_type=heads Confluence page giving these schemas
    • 20.5
    • Stories Completed, Integrated, Solution Intent Updated, Outcomes Reviewed, NFRS met, Satisfies Acceptance Criteria, Accepted by FO

    • PI23 - UNCOVERED

    • Team_MCCS
    • Low-G1

    Description

      Enabler to define a basic API defining the interfacing between the TMC and MCCS. Allowing the development of an MCCS emulator against which the TMC.LOW MCCS Leaf Nodes can be developed, tested and integrated into the SKA LOW MVP.

      This should be a collaborative effort between Himalaya and MCCS with MCCS team providing the details of the API /JSON schema in the repo and Himalaya team developing TMC calls against them, using a mock Tango device layer initially to test in the test harness developed by TMC teams.

      Attachments

        Issue Links

          informs

          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-2497 TMC MCCS Leaf Node Subarray implements the full Observing state machine

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

          Page Loading...

          Page Loading...

          Structure

            Activity

              People

                a.bridger Bridger, Alan
                Adam.Avison Avison, Adam
                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
                  Complete511.0
                  Total511.0

                  Dates

                    Created:
                    Updated:
                    Resolved:

                    Structure Helper Panel