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

Continued development of continuum imaging pipelines using JACAL / ASKAPSoft

    XporterXMLWordPrintable

Details

    • Enabler
    • Should have
    • PI12
    • COM SDP SW
    • None
    • Data Processing
    • Hide

      Analysis of existing state-of-the-art imaging pipelines will help inform SKA SDP Pipeline development.

      Show
      Analysis of existing state-of-the-art imaging pipelines will help inform SKA SDP Pipeline development.
    • Hide
      • An analysis of the computational performance of Yandasoft/Jacal DI continuum imaging using standard SKA simulated data sets.
      • A mapping of performance bottlenecks against processing functions/processing steps (informing/leveraging SP-1959).
      • A demonstration of a modest level of parallelisation.
      Show
      An analysis of the computational performance of Yandasoft/Jacal DI continuum imaging using standard SKA simulated data sets. A mapping of performance bottlenecks against processing functions/processing steps (informing/leveraging SP-1959 ). A demonstration of a modest level of parallelisation.
    • 1
    • 1
    • 5
    • 5
    • Team_YANDA
    • Sprint 5
    • Hide

      https://confluence.skatelescope.org/display/SE/Yandasoft+Profiling+Low

      Processing workflows CoP presentation:
      https://drive.google.com/file/d/17Ql9rBBEKP-FzsSpQvxqN3rLA3Rz4wNK/view?usp=sharing

      Show
      https://confluence.skatelescope.org/display/SE/Yandasoft+Profiling+Low Processing workflows CoP presentation: https://drive.google.com/file/d/17Ql9rBBEKP-FzsSpQvxqN3rLA3Rz4wNK/view?usp=sharing
    • 14.2
    • Stories Completed, Integrated, Outcomes Reviewed, NFRS met, Demonstrated, Satisfies Acceptance Criteria, Accepted by FO

    • PI22 - UNCOVERED

    Description

      Timeboxed activity to continue analysis of SDP imaging pipelines based on YANDASoft with the aim of informing the development of pipelines for the SKA SDP system.

      Continued analysis of continuum imaging pipelines using YANDASoft, focusing on runtime and memory improvements when using the the Nyquist gridding enhancement developed in PI11 and the gridding work in SP-1859. Performance will be assessed using CoP simulated datasets and will include parallel gridding and merging.

      Analyses will be regularly shared as part of the Processing Workflows CoP and major results will be demoed at DP System Demos. Simulated datasets, performance mapping function, etc., will be updated accordingly.

      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-1549 CASA based SKA1 MID continuum imaging reference pipeline

          • Could have - Items labelled as "Could have" are desirable but not necessary and could improve the user experience or customer satisfaction for a little development cost. These will typically be included if time and resources permit.
          • Funnel

          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-1901 Revised simulations and/or data sets for SDP image pipeline testing

          • 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

          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-1904 Continued development of continuum imaging pipelines using LOFAR codes (WSClean, DP3, ...)

          • 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

          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-1905 Continued development of continuum imaging pipelines using RASCIL

          • 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

          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-1959 Map out continuum imaging pipelines as a set of Processing Functions

          • 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

          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-1859 Add a flexible gridder interface to Jacal

          • 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
          mentioned in

          Page Loading...

          Page Loading...

          Page Loading...

          Page Loading...

          Page Loading...

          Structure

            Activity

              People

                b.mort Mort, Ben
                f.graser Graser, Ferdl
                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
                  Complete23.0
                  Total23.0

                  Dates

                    Created:
                    Updated:
                    Resolved:

                    Structure Helper Panel