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

SKA-SRC interfaces description

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

Details

    • Data Processing
    • Hide

      Provides a cruicial reference for the design of SRCs and data policy creation.

      Show
      Provides a cruicial reference for the design of SRCs and data policy creation.
    • Hide

      primary goal: Interface Design Document with sufficient detail for System-CDR. To include all interfaces between the observatory and the SRCs.

      furthermore:

      • Google folder with documentation shared with authors and reviewers
        -  Formation of author team
        -  Solicitation of feedback from reviewers concerned with SRC design
      • Initial draft of SDP SRC IDD for review purposes
      • Ensure consistency with SDP and TM documentations, noting gaps if these are discovered.

      Timeline targets:

      By end June 2019: Collate relevant background documents and other resources into shared google drive space: https://drive.google.com/drive/u/2/folders/1e3hTk1dNipXU05FoAPvDmZfShnmwJ25y

      Close out first draft by 23rd August, ready for review by internal SKA stakeholders and the SRCSC. On track to achieve this.

      Final draft ready mid-September (PI5, so need small allocation of effort in PI5 from author team to respond to any reviewers' comments - see https://jira.skatelescope.org/browse/SP-523).

       

      Show
      primary goal: Interface Design Document with sufficient detail for System-CDR. To include all interfaces between the observatory and the SRCs. furthermore: Google folder with documentation shared with authors and reviewers -  Formation of author team -  Solicitation of feedback from reviewers concerned with SRC design Initial draft of SDP SRC IDD for review purposes Ensure consistency with SDP and TM documentations, noting gaps if these are discovered. Timeline targets: By end June 2019: Collate relevant background documents and other resources into shared google drive space:  https://drive.google.com/drive/u/2/folders/1e3hTk1dNipXU05FoAPvDmZfShnmwJ25y Close out first draft by 23rd August, ready for review by internal SKA stakeholders and the SRCSC. On track to achieve this. Final draft ready mid-September (PI5, so need small allocation of effort in PI5 from author team to respond to any reviewers' comments - see https://jira.skatelescope.org/browse/SP-523 ).  
    • 2
    • 2
    • 8
    • Team_ORCA, Team_YANDA
    • Sprint 5
    • Hide

      Full first draft of the SKAO-SRC IDD here, ready for internal review at SKAO

      https://docs.google.com/document/d/1FcO_iyvdKoVISlvzO1SUUvZivcmrUh6AVXC012Cpixo/edit#

      Show
      Full first draft of the SKAO-SRC IDD here, ready for internal review at SKAO https://docs.google.com/document/d/1FcO_iyvdKoVISlvzO1SUUvZivcmrUh6AVXC012Cpixo/edit#
    • 3.6
    • PI24 - UNCOVERED

    • SDP-Discuss SKAO_SciOps Team_ORCA Team_YANDA Yanda_MVPrunway

    Description

      Generate an Interface Design Description for SKAO-SRC interface.

      This has previously been seen only as the SDP-SRC interface but we need to also address all interactions between the observatory and SRCs (even if the descriptions are sparse at the moment).

      See: https://confluence.skatelescope.org/display/BCS/Bridging+Task+SOW%3A133+SRC+interface

      Also, from the SDP CDR Panel Report:

      SDP Is required to deliver Observatory Data Products to the SRCs.  Further, in the Construction Plan p. 8 it states “There are currently no explicit requirements to deploy SDP software or SDP variants at SRCs. However, SKAO have expressed a desire (through the pre-CDR OAR SDPPRECDR-270) for early engagement with SRCs and deployment of SDP software to SRCs which could benefit science commissioning of the telescopes by providing significant compute resources for commissioning.”

      And, on p. 9 “Implementing the Commissioning and AIV support software product variant is included in the cost estimate of the SDP element, but not implementing any other Product Variants.”

      The lack of a formal SDP – SRC ICD prevents a comprehensive elaboration of the DELIV component of SDP, as well as features in or characteristics of SDP that would enable effective use the SDP instances in SRCs.

      Recommendation: Develop a “reference” SDP – SRC ICD in Bridging (even in advance of complete clarity within SKA on the funding, number, location, and capabilities of the SRCs) as a design and planning vehicle, and maintain it until it can be baselined.

      Attachments

        Issue Links

          Structure

            Activity

              People

                r.bolton Bolton, Rosie
                n.rees Rees, Nick
                Votes:
                0 Vote for this issue
                Watchers:
                11 Start watching this issue

                Feature Progress

                  Story Point Burn-up: (100.00%)

                  Feature Estimate: 2.0

                  IssuesStory Points
                  To Do00.0
                  In Progress   00.0
                  Complete925.0
                  Total925.0

                  Dates

                    Created:
                    Updated:
                    Resolved:

                    Structure Helper Panel