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

Updated visibility receive workflow integrated into the SDP prototype

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

Details

    • Data Processing
    • Hide

      In addition to the control and monitoring interfaces, a simple visibility receive workflow is the primary function SDP is required to deploy for testing at the first prototype system integration and array release.

      Now the work has been done in PI6 to develop an updated design and implementation that is suitable for this and can easily be extended and developed further we now need to integrate and test this as part of the full system prototype which includes TMC interfaces.

      Show
      In addition to the control and monitoring interfaces, a simple visibility receive workflow is the primary function SDP is required to deploy for testing at the first prototype system integration and array release. Now the work has been done in PI6 to develop an updated design and implementation that is suitable for this and can easily be extended and developed further we now need to integrate and test this as part of the full system prototype which includes TMC interfaces.
    • Hide
      1. Updated receive workflow that can be executed though the TMC interface provided by the SDP prototype subarray device deployed, tested, and demoed in an integration environment
        1. This does not include the TM interface for metadata such as antenna tables which will be the subject of a future PI.
      2. Update log output produced by the workflow to the SKA logging standards (not negotiable)
      3. determine node level resources for CI workload resource containment (see here)
      4. Stretch: Contribute to the development and (BDD) testing of this as part of the SKAMPI deployment
      Show
      Updated receive workflow that can be executed though the TMC interface provided by the SDP prototype subarray device deployed, tested, and demoed in an integration environment This does not include the TM interface for metadata such as antenna tables which will be the subject of a future PI. Update log output produced by the workflow to the SKA logging standards (not negotiable) determine node level resources for CI workload resource containment (see here ) Stretch: Contribute to the development and (BDD) testing of this as part of the SKAMPI deployment
    • 1
    • 1
    • 16
    • Team_YANDA
    • Sprint 4
    • Hide

      Code: https://gitlab.com/ska-telescope/cbf-sdp-emulator

      Presentation given at System Demo 7.4 (https://confluence.skatelescope.org/display/SE/2020-07-29+DP+ART+System+Demo+7.4)

      Also see linked stories for further details and discussion.

      Show
      Code: https://gitlab.com/ska-telescope/cbf-sdp-emulator Presentation given at System Demo 7.4 ( https://confluence.skatelescope.org/display/SE/2020-07-29+DP+ART+System+Demo+7.4 ) Also see linked stories for further details and discussion.
    • 7.4
    • PI22 - UNCOVERED

    • SDP-Software Team_YANDA
    • SPO-567

    Description

      This feature should extend the great work done by the YANDA team (s.ord) in PI6 which design an developed an updated visibility receive workflow targeted at the PSI (and AA0.5) requirements (see links below).

      The critical next step for this is to test and implement this updated workflow in the SDP prototype code controlled though commands issues to the SDP Subarray device and as part of a tested SKAMPI deployment in a suitable integration environment. If possible this should extend to consider configuration and deployment of a multi-node receive workflow. 

      If time permits this work should also consider some (or all) of the of the following next steps:

      • Working closely alongside the team/teams who select SP-1001 to test this workflow with associated real-time signal plots
      • Working closely alongside the team/teams who select SP-1023 to provide a PoC of how additional RT processing (eg flagging) might be associated with visibility receive.
      • Working closely alongside the team/teams who select  SP-1048 to test deployment latency associated with the risk of assigning and (re-)configuring SDP resources
      • Testing and adding other protocols (eg. RoCE)
      • Adding additional payloads
      • Consideration and PoC of an improved mechanism to obtain MS meta-data for use in the receive workflow. As only limited data is provided by the CBF data stream currently the source of additional meta-data required to construct the MS written by the receive workflow is not architecturally correct.
      • Consideration and testing of error / failure modes relating missing data, dropped connections, failure of a node where receive is started etc.

       


      Links to work from PI6:

      Features:

      Code:

      Demo:

      Attachments

        Issue Links

          Structure

            Activity

              People

                b.mort Mort, Ben
                b.mort Mort, Ben
                Votes:
                0 Vote for this issue
                Watchers:
                3 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
                  Complete46.0
                  Total46.0

                  Dates

                    Created:
                    Updated:
                    Resolved:

                    Structure Helper Panel