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

DISH AIV: Expose required SPFC attributes via Tango

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

Details

    • MID ART
    • Hide

      Enables the development of a GUI based on the available attributes.

      Show
      Enables the development of a GUI based on the available attributes.
    • Hide
      • Enable SPFC and SPFRx to register on the TangoDB for Dish LMC to access
      • All required attributes for a prototype GUI are identified
      • All required attributes are exposed via Tango
        • The required attributes are exposed on SPFRx and SPFC directly and not on Dish.LMC necessarily.
      • A command line interface is used to demonstrate successful return the required attribute values upon request.
        • iTango used to demonstrate retrieving values from SPFC and SPFRx directly
      • Basic PoC is demonstrated to stakeholders of this GUI in Taranta based on the slides in google doc below.
        • The Taranta GUI will connect directly to SPFC and SPFRx and display the required attributes

       

      EDIT: De-scoping SPFRx work

      Show
      Enable SPFC and SPFRx to register on the TangoDB for Dish LMC to access All required attributes for a prototype GUI are identified All required attributes are exposed via Tango The required attributes are exposed on SPFRx and SPFC directly and not on Dish.LMC necessarily. A command line interface is used to demonstrate successful return the required attribute values upon request. iTango used to demonstrate retrieving values from SPFC and SPFRx directly Basic PoC is demonstrated to stakeholders of this GUI in Taranta based on the slides in google doc below. The Taranta GUI will connect directly to SPFC and SPFRx and display the required attributes   EDIT: De-scoping SPFRx work
    • 2
    • 2
    • 0
    • Team_KAROO
    • Sprint 4
    • Hide

      We did decide on a procedure to register the SPFC in the Dish.LMC Tango DB. See here for details: https://confluence.skatelescope.org/display/SWSI/SPF+Controller+Tango+device+registration+on+Dish.LMC+TangoDB

       

      Unfortunately we required the SPFC device to be integrated with Dish.LMC to be able to do this work.

      SPFC is still being upgraded to Tango 9.4.2 and as such is not available for integration in time.

      Show
      We did decide on a procedure to register the SPFC in the Dish.LMC Tango DB. See here for details: https://confluence.skatelescope.org/display/SWSI/SPF+Controller+Tango+device+registration+on+Dish.LMC+TangoDB   Unfortunately we required the SPFC device to be integrated with Dish.LMC to be able to do this work. SPFC is still being upgraded to Tango 9.4.2 and as such is not available for integration in time.
    • 23.4

    Description

       

      The Dish AIV team need a GUI to expose a number of low-level device attributes for SPFC maintenance and installation. This GUI has come with a short time frame and so pragmatic solutions are required.

      A full specification is given in: TAIV-788

      The initial focus (PI20) is on "Services" (Helium and Vacuum) and B2 interfaces. See slides 2,4,7 and 8 of https://docs.google.com/presentation/d/1Wk4B2QptrrVa9MXKWUrapmX7_CRaJPrApMDOWhC6kIE/edit?usp=drive_web

      This enabler seeks to expose via Tango the required attributes for the GUI as listed in th

      Attachments

        Issue Links

          relates to

          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-3743 DISH AIV: Prototype interface with SPFC and Band 2 Reciver for DISH Maintenance GUI

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

          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-3836 Deliver DSH LMC and GUI to commission first dish structure, SPF and SPFRx

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

          Page Loading...

          Page Loading...

          Page Loading...

          Page Loading...

          Structure

            Activity

              People

                s.vrcic Vrcic, Sonja
                Adam.Avison Avison, Adam
                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
                  Complete21.5
                  Total21.5

                  Dates

                    Created:
                    Updated:
                    Resolved:

                    Structure Helper Panel