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

Visibility receive workflow configured and tested for use with the PSI

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

Details

    • Data Processing
    • Hide

      One of the first functions we will need to test at a PSI deployment is a visibility receive workflow which captures data from a data stream provided by the CBF prototype. We need to be ready for this by updating, turning, and demonstrating the visibility receive workflow on a timescale before first PSI integration to reduce the risk that this critical functionality may not work correctly when first integrated with a CBF data stream.

      An updated receive workflow will also be needed to test signal display functionality which will also be needed for PSI deployment.

      Show
      One of the first functions we will need to test at a PSI deployment is a visibility receive workflow which captures data from a data stream provided by the CBF prototype. We need to be ready for this by updating, turning, and demonstrating the visibility receive workflow on a timescale before first PSI integration to reduce the risk that this critical functionality may not work correctly when first integrated with a CBF data stream. An updated receive workflow will also be needed to test signal display functionality which will also be needed for PSI deployment.
    • Hide
      • Identify requirements for running within the PSI
      • Document use as a standalone module (package e.g. as singularity container?) so that it can be used for testing by CBF
      • Multi-node receive workflow tested to work with the data dimensions of the CBF deployed at the PSI (Mid: ~2-4 antennas, ~10k-20k channels, 1 pol, 0.08s dump rate, Low: 4 Stations, 300MHz bandwidth: ~56k channels, 4 pol, 0.9s dump rate)
      • Workflow produces a MS directly or indirectly that could be loaded and imaged in CASA (producing the CASA image is not required for this ticket)
      • Initial benchmarking to understand steps required to achieve future scaling requirements (see SS-35, ie Mid stage 3 -> 56000 channels)
      Show
      Identify requirements for running within the PSI Document use as a standalone module (package e.g. as singularity container?) so that it can be used for testing by CBF Multi-node receive workflow tested to work with the data dimensions of the CBF deployed at the PSI (Mid: ~2-4 antennas, ~10k-20k channels, 1 pol, 0.08s dump rate, Low: 4 Stations, 300MHz bandwidth: ~56k channels, 4 pol, 0.9s dump rate) Workflow produces a MS directly or indirectly that could be loaded and imaged in CASA (producing the CASA image is not required for this ticket) Initial benchmarking to understand steps required to achieve future scaling requirements (see SS-35 , ie Mid stage 3 -> 56000 channels)
    • 3
    • 3
    • 5.333
    • Team_YANDA
    • Sprint 5
    • Hide

      dev artifacts of CBF emulator are the same for sender (SP-794) and receiver (SP-836)
      code repo
      https://gitlab.com/ska-telescope/cbf-sdp-emulator.git
      documentation
      https://developer.skatelescope.org/projects/cbf-sdp-emulator/en/latest/
      Notes on requirements
      https://confluence.skatelescope.org/display/SE/CSP-SDP+Correlator+Interface+Emulator+for+Prototype+System+Integration+%28PSI%29+Usage+-+Notes+on+Requirements
      system demo slides
      https://docs.google.com/presentation/d/1tsQYiY4fj2-5vWi7JXtqIvEcuU2PWmur4FXggx1QiEg/edit?usp=sharing

      Show
      dev artifacts of CBF emulator are the same for sender ( SP-794 ) and receiver ( SP-836 ) code repo https://gitlab.com/ska-telescope/cbf-sdp-emulator.git documentation https://developer.skatelescope.org/projects/cbf-sdp-emulator/en/latest/ Notes on requirements https://confluence.skatelescope.org/display/SE/CSP-SDP+Correlator+Interface+Emulator+for+Prototype+System+Integration+%28PSI%29+Usage+-+Notes+on+Requirements system demo slides https://docs.google.com/presentation/d/1tsQYiY4fj2-5vWi7JXtqIvEcuU2PWmur4FXggx1QiEg/edit?usp=sharing
    • 6.6

    • PI24 - UNCOVERED

    Description

      Including the ability to deploy multiple receive processes.

      Stretch: RDMA based receive workflow.

      Attachments

        Issue Links

          relates to

          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-837 Interface for access to SDP data products produced at the PSI

          • Not Assigned - Priority is not assigned yet.
          • 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-838 Real-time signal displays & metrics for the PSI (QA displays)

          • Not Assigned - Priority is not assigned yet.
          • 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-900 PSI platform requirements

          • Not Assigned - Priority is not assigned yet.
          • 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-910 Create an RDMA-based receive code for ingest into the Imaging/Gain Calibration Pipeline

          • Not Assigned - Priority is not assigned yet.
          • 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-794 CBF visibility data stream emulator for testing PSI deployment

          • Not Assigned - Priority is not assigned yet.
          • 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-950 Updated visibility receive workflow integrated into the SDP prototype

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

          Page Loading...

          Page Loading...

          Page Loading...

          Page Loading...

          Page Loading...

          Page Loading...

          Page Loading...

          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: 3.0

                  IssuesStory Points
                  To Do00.0
                  In Progress   00.0
                  Complete813.0
                  Total813.0

                  Dates

                    Created:
                    Updated:
                    Resolved:

                    Structure Helper Panel