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

Standardise testing of initial (PI9) SDP imaging pipelines

    XporterXMLWordPrintable

Details

    • Enabler
    • Not Assigned
    • PI10
    • COM SDP SW
    • None
    • Data Processing
    • Hide

      With the amount of modifiability we have built into the SDP architecture, it is important that we have robust means to establish that processing is doing its job correctly even when we change technologies.

      Show
      With the amount of modifiability we have built into the SDP architecture, it is important that we have robust means to establish that processing is doing its job correctly even when we change technologies.
    • Hide
      • Automated pipeline that can establish functional correctness of more than one pipeline (developed during last PI)
        • Ideally embedded into GitLab CI - might require a new "workflow integration/testing" repository.
      • Both the tests themselves and especially the metrics used for establishing correctness are well-documented.
      • Identify requirements for the platform to run these tests on (K8s? SLURM?), implement on a currently available approximation (P3? IRIS resources? ASTRON's effort?)
      • Stretch: Also collect (computational) performance metrics, keeping in mind the connection to SP-1585
      • Stretch: Organise and store metrics and test results collected from pipelines to allow contrasting different implementations and versions
      Show
      Automated pipeline that can establish functional correctness of more than one pipeline (developed during last PI) Ideally embedded into GitLab CI - might require a new "workflow integration/testing" repository. Both the tests themselves and especially the metrics used for establishing correctness are well-documented. Identify requirements for the platform to run these tests on (K8s? SLURM?), implement on a currently available approximation (P3? IRIS resources? ASTRON's effort?) Stretch: Also collect (computational) performance metrics, keeping in mind the connection to SP-1585 Stretch: Organise and store metrics and test results collected from pipelines to allow contrasting different implementations and versions
    • 4
    • 4
    • 13.25
    • Team_YANDA
    • Sprint 5
    • Hide

      Repo for SDP workflows:
      https://gitlab.com/ska-telescope/sdp/ska-sdp-continuum-imaging-pipelines
      sysdemo 10.4 sample workflow demos:
      https://drive.google.com/file/d/1yfhe1efpmKujyL_JCqrpU-ShxjxPSkcO/view?usp=sharing
      https://drive.google.com/file/d/10ZlVQcFgBLCy87fn0lvxMaJGOqQzxOJV/view?usp=sharing

      Show
      Repo for SDP workflows: https://gitlab.com/ska-telescope/sdp/ska-sdp-continuum-imaging-pipelines sysdemo 10.4 sample workflow demos: https://drive.google.com/file/d/1yfhe1efpmKujyL_JCqrpU-ShxjxPSkcO/view?usp=sharing https://drive.google.com/file/d/10ZlVQcFgBLCy87fn0lvxMaJGOqQzxOJV/view?usp=sharing
    • 12.4
    • Stories Completed, Integrated, Outcomes Reviewed, NFRS met, Demonstrated, Satisfies Acceptance Criteria, Accepted by FO

    • PI22 - UNCOVERED

    • SPO-1002

    Description

      Following up on the continuum pipeline work from the last PI - we have now proven that we have multiple pipelines that can perform roughly the same task. However, comparisons are still manual and somewhat subjective, and we must make sure that the results are reproducable so we can track the situation as we improve our solutions. The goal for this feature is therefore to standardise on a common method for pipeline testing.

      Attachments

        Issue Links

          followed 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-1693 Onboard and test complete set continuum imaging pipelines using simulation data (without DD effects)

          • Should have - Items labelled as "Should have" are important but not necessary for delivery in the current delivery timebox. While "Should have" items can be as important as "Must have", they are often not as time-critical or there may be another way to satisfy the requirement so that it can be held back until a future delivery timebox.
          • Done
          relates to

          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-1585 Standardise SDP processing performance benchmarking

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

          Page Loading...

          Page Loading...

          Page Loading...

          Page Loading...

          Structure

            Activity

              People

                p.wortmann Wortmann, Peter
                r.brederode Brederode, Ray
                Votes:
                0 Vote for this issue
                Watchers:
                7 Start watching this issue

                Feature Progress

                  Story Point Burn-up: (100.00%)

                  Feature Estimate: 4.0

                  IssuesStory Points
                  To Do00.0
                  In Progress   00.0
                  Complete1626.0
                  Total1626.0

                  Dates

                    Created:
                    Updated:
                    Resolved:

                    Structure Helper Panel