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

Minimal SDP Configuration

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

Details

    • Feature
    • Not Assigned
    • PI3
    • None
    • Data Processing
    • Hide

      TODO!!

      Show
      TODO!!
    • 4
    • 4
    • 10
    • Team_ORCA
    • Sprint 5
    • Hide

      Presented SPO-173 at https://confluence.skatelescope.org/pages/viewpage.action?pageId=74731988

      Code can be found on GitHub: https://github.com/ska-telescope/sdp-prototype . Revision 4c5031dc9 was used for the demo - SDP deployed using Kubernetes as described in `deploy/charts/README.md`, CASA pod configuration in `scripts/casa_pod.yaml`. Example processing block in `examples/example_pb.json`.

      Show
      Presented SPO-173 at https://confluence.skatelescope.org/pages/viewpage.action?pageId=74731988 Code can be found on GitHub: https://github.com/ska-telescope/sdp-prototype . Revision 4c5031dc9 was used for the demo - SDP deployed using Kubernetes as described in `deploy/charts/README.md`, CASA pod configuration in `scripts/casa_pod.yaml`. Example processing block in `examples/example_pb.json`.
    • 8.5
    • Stories Completed, Integrated, Outcomes Reviewed, Demonstrated, Satisfies Acceptance Criteria

    • PI22 - UNCOVERED

    • Team_ORCA

    Description

      This feature will allow a user to issue a minimal SDP configuration command to the existing SIP software. The result should, at least, result in data being written to storage in a CASA measurement set. 

      It will test the integration between SIP and TMC.

      Attachments

        Issue Links

          is duplicated by

          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-313 SDP Tango Attribute Alarms

          • 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.
          • Discarded
          relates to

          PI Risk - Program Increment risk for ROAMing ROAM-32 Maturity of Xray-Gitlab API (only a basic REST API)

          • Retired

          PI Risk - Program Increment risk for ROAMing ROAM-40 CASA python API for writing MS files is incomplete / poorly documented

          • Retired

          Capability - SAFe program capability SS-14 Simple Subarray LMC Control

          • 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...

          Page Loading...

          Page Loading...

          Page Loading...

          Page Loading...

          Page Loading...

          Page Loading...

          Structure

            Activity

              People

                g.leroux Le Roux, Gerhard [X] (Inactive)
                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: 4.0

                  IssuesStory Points
                  To Do00.0
                  In Progress   00.0
                  Complete57130.8
                  Total57130.8

                  Dates

                    Created:
                    Updated:
                    Resolved:

                    Structure Helper Panel