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

Design and implement telescope model for visibility receive

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

Details

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

      A unified way for accessing telescope model data will be required to synchronise assumptions about the telescope across simulations, testing and processing (both on SDP and CSP).

      Show
      A unified way for accessing telescope model data will be required to synchronise assumptions about the telescope across simulations, testing and processing (both on SDP and CSP).
    • Hide
      • Determine simple design for determining telescope model information required for receive to produce a valid measurement set for all AA0.5 testing scenarios. Should be within existing architecture, i.e. assume no additional TMC interaction outside of - say - workflow parameters
      • Build a library that can load and interpret telescope model information (possibly as part of ska_telmodel?). Should be integrated into SDP receive. Concrete telescope model (version) to use should be configurable via workflow parameters.
      • Stretch: Demonstrate workflow for adding new telescope model data artefacts and checking their correctness (e.g. trigger a CI job on ska_telmodel, use parameters to point to new telescope model artefact?)
      Show
      Determine simple design for determining telescope model information required for receive to produce a valid measurement set for all AA0.5 testing scenarios. Should be within existing architecture, i.e. assume no additional TMC interaction outside of - say - workflow parameters Build a library that can load and interpret telescope model information (possibly as part of ska_telmodel?). Should be integrated into SDP receive. Concrete telescope model (version) to use should be configurable via workflow parameters. Stretch: Demonstrate workflow for adding new telescope model data artefacts and checking their correctness (e.g. trigger a CI job on ska_telmodel, use parameters to point to new telescope model artefact?)
    • 2
    • 2
    • 20
    • 10
    • Team_YANDA
    • Sprint 4
    • Hide

      AC1
      https://confluence.skatelescope.org/display/SE/UVW+Calculation+and+Measurement+Set+Update+Package
      https://confluence.skatelescope.org/display/SWSI/ADR-50+Terrestrial+frame+motion+correction+responsibilities
      https://docs.google.com/presentation/d/1CZZq1f0ykXThFrvQM1uPNh1QykIigyF-h9KfzbnOwk0/edit?usp=sharing

      AC2
      Static Telescope Model
      https://confluence.skatelescope.org/display/SE/Telescope+Model+attributes+based+on+MS
      https://gitlab.com/ska-telescope/sdp/prototype-telescope-model-repository

      system demo 12.4:

      Show
      AC1 https://confluence.skatelescope.org/display/SE/UVW+Calculation+and+Measurement+Set+Update+Package https://confluence.skatelescope.org/display/SWSI/ADR-50+Terrestrial+frame+motion+correction+responsibilities https://docs.google.com/presentation/d/1CZZq1f0ykXThFrvQM1uPNh1QykIigyF-h9KfzbnOwk0/edit?usp=sharing AC2 Static Telescope Model https://confluence.skatelescope.org/display/SE/Telescope+Model+attributes+based+on+MS https://gitlab.com/ska-telescope/sdp/prototype-telescope-model-repository system demo 12.4: slides https://docs.google.com/presentation/d/1W_ya0g_2ZP6jKjw8762PYLing6eQJpJBGf4TIfmqmPE/edit?usp=sharing see recording for sw demo https://confluence.skatelescope.org/display/SE/2021-11-03+DP+ART+System+Demo+12.4
    • 14.2
    • Stories Completed, Integrated, Solution Intent Updated, BDD Testing Passes (no errors), Outcomes Reviewed, NFRS met, Demonstrated, Satisfies Acceptance Criteria, Accepted by FO

    • PI22 - UNCOVERED

    Description

      Needs to provide a solution for writing valid and correct MS for both MID and LOW for AA0.5 testing scenarios (https://confluence.skatelescope.org/display/SST/AA0.5+Scenarios). Needs to be a solution that allows flexibility in the way an operator (or TBD other system) provides metadata for constructing a minimally complete MS that can be used for comissioning tests with AA0.5

      To this end must maintain consistent models for how the telescope looks like and behaves, specifically so

      • we can keep track of information related to the correlated visibilities
      • we can produce data products that are consistent with our most up-to-date understanding of the telescope

       

      As ADR-30 notes, shared assumptions can be seen as telescope model data and kept in artefact storage. ADR-50 should help clarify how delay and UVW calculations responsibilities are divided up between TMC, SDP and CBF (CSP?).

      Attachments

        Issue Links

          relates to

          Architectural Decision - Software Architectural Decision ADR-50 Terrestrial frame motion correction responsibilities

          • Analyzing

          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-1755 Development of minimal telescope configuration data interface for visibility receive

          • 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

          Architectural Decision - Software Architectural Decision ADR-30 Telescope configuration / model / test data repositories AA0.5

          • decided

          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-1857 Address technical debt and failure modes for SDP AA0.5 visibility receive workflow (and assocated interface emulators)

          • Must have - Items labelled as "Must have" are critical to the current delivery timebox in order for it to be a success.
          • Done

          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-1897 Demonstrate integration and configuration of initial QA metrics and display for visibility receive workflow

          • Must have - Items labelled as "Must have" are critical to the current delivery timebox in order for it to be a success.
          • 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:
                2 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
                  Complete511.0
                  Total511.0

                  Dates

                    Created:
                    Updated:
                    Resolved:

                    Structure Helper Panel