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

Quality Assessment integration

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

Details

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

      See description

      Show
      See description
    • Hide
      1. Develop a test in the sdp-integration repo that shows that when the "visibility receive" workflow is executed, the corresponding QA data is made available on the API and a display can be shown that displays an average autocorrelation power spectra plot with appropriate labelling.
      2. Develop a test in the sdp-integration repo that shows that when "visibility receive" workflow is executed, the corresponding QA data is made available on the API and a display can be shown that displays waterfall (time vs frequency) showing the phase for a select number of baselines
      Show
      Develop a test in the sdp-integration repo that shows that when the "visibility receive" workflow is executed, the corresponding QA data is made available on the API and a display can be shown that displays an average autocorrelation power spectra plot with appropriate labelling. Develop a test in the sdp-integration repo that shows that when "visibility receive" workflow is executed, the corresponding QA data is made available on the API and a display can be shown that displays waterfall (time vs frequency) showing the phase for a select number of baselines
    • 5
    • 5
    • 3
    • 0.6
    • Team_NALEDI
    • Sprint 4
    • Hide

      All stories are complete. NAL-127 is discarded.
      Direct communication between Metric API and Plasma store
      The acceptance criteria for this ticket couldn't be met in sprint 14.6 at the same time as the PI planning. The work on this ticket NAL-127 was quite a bit anyway and was broken down during the PI planning into tickets for Prince for sprints 15.1 and 15.2 as follows:
      15.1
      NAL-159, NAL-157, NAL-160

      15.2
      NAL-161, NAL-163, NAL-164
      Please follow on the above tickets for more fine-grained updates.

      Show
      All stories are complete. NAL-127 is discarded. Direct communication between Metric API and Plasma store The acceptance criteria for this ticket couldn't be met in sprint 14.6 at the same time as the PI planning. The work on this ticket NAL-127 was quite a bit anyway and was broken down during the PI planning into tickets for Prince for sprints 15.1 and 15.2 as follows: 15.1 NAL-159, NAL-157, NAL-160 15.2 NAL-161, NAL-163, NAL-164 Please follow on the above tickets for more fine-grained updates.
    • 17.5
    • Accepted by FO
    • PI24 - UNCOVERED

    • SPO-1591

    Description

       

      Who?

      • For developers of SDP workflows and operator displays

      What?

      • An integrated solution for generation and display of QA metrics for the visibility receive workflow
      • Development of mock / emulated data sources and interface documentation for those developing operator displays as well as those feeding metrics into the system from SDP workflows.
      • Consideration of NFRs

      Why?

      • QA metrics and displays will be needed to establish the telescope is operating correctly.
      • Visibility receive is the first workflow that will need this since we want to integrate and run that by the end of PI15 with CBF hardware at the MID (& LOW) PSI

       


      Notes:

      The focus should be on a complete tested solution for demonstrating use at the PSI or in a persistent deployment of SDP including sufficient developer documentation for others to work with the system developed, continuing to pivot from a prototype to a solution which we will develop for SDP deployment at AA0.5.

      Considerations TBD:

      1) Solution for visibility receive metrics (should be nearly complete but might need some iteration with revisions to the QA display/UI for configuration options). How this is run concurrently with the received workflow needs to be still considered.

      2) Solution for an initial set of metrics for RCAL and RFI flagging workflows - definition of data products to be consumed by the UI display

      3) How metrics might propagate out of the SDP system for use cases other than UI displays

      4) Mocks and emulators for use with QA UI/displays to decouple development

      5) Evolution of the QA metric generator backend to support more advanced operations including aggregation of data from multiple workflow processes.

       

       

      Attachments

        Issue Links

          Structure

            Activity

              People

                D.Fenech Fenech, Danielle
                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: 5.0

                  IssuesStory Points
                  To Do00.0
                  In Progress   00.0
                  Complete1535.0
                  Total1535.0

                  Dates

                    Created:
                    Updated:
                    Resolved:

                    Structure Helper Panel