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

Visibility Receive workflow enhancements

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

Details

    • Feature
    • Must have
    • PI14
    • COM SDP SW
    • None
    • Data Processing
    • Hide

      See description

      Show
      See description
    • Hide
      • New release of the visibility receive workflow (with sufficient documentation and following SKA release management practices)
      • BDD style, Xray tests, preferably in the SDP integration repository and based on those being developed for SP-2364 (and pervious SDP integration work) that verify:
        • The vis receive workflow makes use of station coordinates obtained from the telescope model configuration service (SP-2369)
        • The visibility receive workflow is able to capture data from successive scan, with scan information persisted into the resultant data file(s). note this may also be done by SP-2369 (dropped from parent objective on 2022-05-04)
        • The new workflow can operate with >1 (configurable, default 30) channels per UDP socket.
      • (Stretch) In collaboration with the teams working on QA integration (SP-1977 & SP-2368) demonstrate QA displays for the new visibility receive workflow
      • (stretch) New release of the CBF-SDP emulator capable of working with data dumps from the MID-CBF hardware (Tallon Demonstrator Correlator TDC)
      Show
      New release of the visibility receive workflow (with sufficient documentation and following SKA release management practices) BDD style, Xray tests, preferably in the SDP integration repository and based on those being developed for SP-2364 (and pervious SDP integration work) that verify: The vis receive workflow makes use of station coordinates obtained from the telescope model configuration service ( SP-2369 ) The visibility receive workflow is able to capture data from successive scan, with scan information persisted into the resultant data file(s).  note this may also be done by SP-2369 (dropped from parent objective on 2022-05-04) The new workflow can operate with >1 (configurable, default 30) channels per UDP socket. (Stretch) In collaboration with the teams working on QA integration ( SP-1977 & SP-2368 ) demonstrate QA displays for the new visibility receive workflow (stretch) New release of the CBF-SDP emulator capable of working with data dumps from the MID-CBF hardware (Tallon Demonstrator Correlator TDC)
    • Inter Program, Intra Program
    • 5
    • 5
    • 8
    • 1.6

    • Sub-system Version REL-8 SDP 1.0.x

    • Team_YANDA
    • Sprint 5
    • Hide

      AC1: A new RCAL consumer based on the RASCIL BlockVisibility object has been provided. (It was used in ORCA's sysdemo 14.6 of SP-2142)
      AC2: Added BDD style test making use of station coordinates from TM configuration service.

      Multiple scan support has not been implemented when running out of implementation capacity and it is now in the PI15 backlog as new feature SP-2483.

      Show
      AC1 : A new RCAL consumer based on the RASCIL BlockVisibility object has been provided. (It was used in ORCA's sysdemo 14.6 of SP-2142 ) AC2 : Added BDD style test making use of station coordinates from TM configuration service. Multiple scan support has not been implemented when running out of implementation capacity and it is now in the PI15 backlog as new feature SP-2483 .
    • 17.5
    • Stories Completed, Integrated, BDD Testing Passes (no errors), Outcomes Reviewed, NFRS met, Satisfies Acceptance Criteria, Accepted by FO

    • PI24 - UNCOVERED

    • SPO-1590

    Description

      Who?

      • For AA Operators, AIV Engineers, and commissioning scientists 

      What?

      • A new release of the SDP visibility receive workflow along with associated emulators needed for testing
      • We need to consider the following:
        • Testing a model that can handle more than 1 channel (expected to be 30) per UDP stream
        • Make sure the telescope model configuration service is a source of truth across the telescope so that metadata captured in Measurement Sets is complete and consistent
        • An emulator mode capable of using raw data dumps produced from the test correlator hardware to derisk end-to-end test with CBF hardware in PI15
        • Receive supports multiple successive scans capturing appropriate metadata for each
        • Supporting teams working on QA display integration if needed (although expected to be decoupled through data exchange in the Plasma)
        • Analysis and capturing any possible issues that might arise if we were to deploy a persistent version of SDP with this workflow for stakeholders to play with (and try to break)

      Why?

      • Visibility receive is a core function for integration and commissioning tests.

       

      Notes:

      Further improvements aimed at issuing a new release of the SDP visibility receive workflow for use with MID PSI testing.

      To be considered:

      • Use of a simple telescope model configuration data service (including associated updated control and configuration schemas for running the workflow)
      • Configuration and tests for running with 10+ channels in one stream/port
      • Execution and data capture from multiple successive scans
      • Emulator modes for testing with data fields captured from the CBF hardware
      • Working with AIV engineers to define test scripts for demonstrating this pipeline at the PSI (towards end of PI14 or during PI15)

      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-77 Software Deployment configuration in AA0.5 and ITF

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

          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-2146 Initial SDP AA0.5 visibility receive workflow and test preparation

          • Must have - Items labelled as "Must have" are critical to the current delivery timebox in order for it to be a success.
          • 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-2369 Telescope model (instrument configuration) service improvements

          • Must have - Items labelled as "Must have" are critical to the current delivery timebox in order for it to be a success.
          • Done
          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-2466 CBF-SDP emulator sends correlator data dumps

          • Won't have (this time) - Items labelled as "Won't have", have been agreed by stakeholders as the least-critical, lowest-payback items, or not appropriate at that time. As a result, "Won't have" items are not planned into the schedule for the next delivery timebox.
          • Funnel
          Is delivered by

          Sub-system Version - A version of a sub-system, used in the Release Management and Configuration Management process REL-8 SDP 1.0.x

          • Discarded
          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-2483 Visibility Receive Multiple Scan Support (ADR-54)

          • Must have - Items labelled as "Must have" are critical to the current delivery timebox in order for it to be a success.
          • 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-2364 SDP Integration in an end-to-end software deployment

          • 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...

          Page Loading...

          Structure

            Activity

              People

                b.mort Mort, Ben
                b.mort Mort, Ben
                Votes:
                0 Vote for this issue
                Watchers:
                4 Start watching this issue

                Feature Progress

                  Story Point Burn-up: (100.00%)

                  Feature Estimate: 5.0

                  IssuesStory Points
                  To Do00.0
                  In Progress   00.0
                  Complete1420.0
                  Total1420.0

                  Dates

                    Created:
                    Updated:
                    Resolved:

                    Structure Helper Panel