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

Establish the SKA SDP Processing Function Library

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

Details

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

      Processing functions will provide the building blocks for future SDP pipeline development, therefore establishing how these will be organised, discovered, developed, and maintained early is critical to the future sucess of the SDP product.

      Setting this up now will set an initial minimum standard which for how we develop processing functions in future both in terms of organisation and software engineering quality.

      Show
      Processing functions will provide the building blocks for future SDP pipeline development, therefore establishing how these will be organised, discovered, developed, and maintained early is critical to the future sucess of the SDP product. Setting this up now will set an initial minimum standard which for how we develop processing functions in future both in terms of organisation and software engineering quality.
    • Hide
      • Define and create a repository structure with initial directory layout and infrastructure to provide basis for future SDP processing function development. The intention is that this will either become the single SDP processing library (preferred) or alternately a template that others should follow if the case can be made that it is better to have more than one library.
      • This should contain a simple, well documented, tested, example for others to follow for how to develop and integrate processing functions in future and establishing the minimum software quality standards for doing so.
      Show
      Define and create a repository structure with initial directory layout and infrastructure to provide basis for future SDP processing function development. The intention is that this will either become the single SDP processing library (preferred) or alternately a template that others should follow if the case can be made that it is better to have more than one library. This should contain a simple, well documented, tested, example for others to follow for how to develop and integrate processing functions in future and establishing the minimum software quality standards for doing so.
    • 3
    • 3
    • 100
    • 33.333
    • Team_HIPPO
    • Sprint 4
    • Hide

      Existing solutions were investigated, and the summary is on the confluence page: https://confluence.skatelescope.org/display/SE/SPO-1371+--+Processing+function+library, where there is also a proposal for the processing function library regarding structure, what it should contain and desire behaviour. The example of a processing function using this proposal is located here: https://github.com/KAdamek/sdp_PF_library

      Show
      Existing solutions were investigated, and the summary is on the confluence page: https://confluence.skatelescope.org/display/SE/SPO-1371+--+Processing+function+library , where there is also a proposal for the processing function library regarding structure, what it should contain and desire behaviour. The example of a processing function using this proposal is located here: https://github.com/KAdamek/sdp_PF_library
    • 14.2
    • Stories Completed, Integrated, Outcomes Reviewed, Satisfies Acceptance Criteria
    • PI22 - UNCOVERED

    Description

      Overall goal is a library with the sufficient structure and testing so that multiple teams can work on concurrently it in future PIs.

      As a starting point it will need to support C/C++, GPU acceleration, and Python language bindings and will eventually be populated to provide a simple portable set of functions that can be combined to develop SDP pipelines.

      The documentation and testing need to be at a level that new people/teams can contribute by the end of the work (although probably not efficiently, that will require iteration).

      Prior to setting this up, it would also be advisable to consider the approach and taken by other widely used libraries with similar aims some of which are being discussed in the comments below.

      While possibly a stretch for PI12 (and not a core requirement for the feature), it would also be valuable to discuss, consider, and document a proposed intial approach to consistent calling conversions and data representations.

       

      Attachments

        Issue Links

          Structure

            Activity

              People

                b.nikolic Nikolic, Bojan
                b.mort Mort, Ben
                Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Feature Progress

                  Story Point Burn-up: (93.33%)

                  Feature Estimate: 3.0

                  IssuesStory Points
                  To Do00.0
                  In Progress   11.0
                  Complete714.0
                  Total815.0

                  Dates

                    Created:
                    Updated:
                    Resolved:

                    Structure Helper Panel