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

MVP incorporates delays from KATpoint API

    XporterXMLWordPrintable

Details

    • Obs Mgt & Controls
    • Hide

      Add (at least somewhat) realistic delay calculations to our MVP and highlight any errors or challenges in integrating the Katpoint API. 

      Show
      Add (at least somewhat) realistic delay calculations to our MVP and highlight any errors or challenges in integrating the Katpoint API. 
    • Hide

      1) Current version of Katpoint delay libraries are integrated into TMC based on the baselines specified in the sub-array

      2) 'Scan' procedures are updated to reflect calling the delay libraries at the required interval and passing on to CSP

      3) Code meets Definition of Done  

      This feature will be tested as follows:

      A preconfigured SCAN will be executed with a particular set of pointing parameters and receptor positions.

      Based on these input parameters a theoretical set of delay values will be calculated using the same mathematical model upon which the delay libraries are based. These values will be then be asserted to be equal with the data send to the CSP. Furthermore, the correct protocol for sending the data will be verified by the CSP being able to apply the data in the correct manner.

      Show
      1) Current version of Katpoint delay libraries are integrated into TMC based on the baselines specified in the sub-array 2) 'Scan' procedures are updated to reflect calling the delay libraries at the required interval and passing on to CSP 3) Code meets Definition of Done   This feature will be tested as follows: A preconfigured SCAN will be executed with a particular set of pointing parameters and receptor positions. Based on these input parameters a theoretical set of delay values will be calculated using the same mathematical model upon which the delay libraries are based. These values will be then be asserted to be equal with the data send to the CSP. Furthermore, the correct protocol for sending the data will be verified by the CSP being able to apply the data in the correct manner.
    • 3
    • 3
    • 4.333
    • Team_NCRA
    • Sprint 5
    • Hide

      This was already completed in a previous PI PI5 but remains open for some reason. Moving it to Done. Code with Katpoint API was merged

      Show
      This was already completed in a previous PI PI5 but remains open for some reason. Moving it to Done. Code with Katpoint API was merged
    • 8.4
    • Stories Completed, Integrated, Outcomes Reviewed, NFRS met, Demonstrated, Satisfies Acceptance Criteria, Accepted by FO

    • PI22 - UNCOVERED

    • MVP_Extension PI5_DEMO Team_NCRA goal_O1

    Description

      Currently the scan MVP passes dummy values for delays to CSP, and the actual delay libraries are not called.

      We would like to investigate and begin integrating the actual delay libraries. For this we should use the Katpoint API for the delays. It is likely that the actual Katpoint delay code may be replaced by CALC wrapped with Python however the API is likely to be the same. (However this can be validated with Ben Mort to the extent of any changes in the Katpoint API). The purpose of integrating this into the MVP is so that the APIs can be understood, any gaps highlighted and the CSP receives more accurate delay values. 

      Attachments

        Issue Links

          Child Of

          Epic - Created by Jira Software - do not edit or delete. Issue type for a big user story that needs to be broken down. SS-5 Evolutionary Prototype/SKAMPI

          • Could have - Items labelled as "Could have" are desirable but not necessary and could improve the user experience or customer satisfaction for a little development cost. These will typically be included if time and resources permit.
          • Done
          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-85 Integrate KATpoint into DISH leaf node

          • 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-159 Improve KATPOINT pointing calculations and validate pointing calculations with SOFA

          • Done
          mentioned in

          Page Loading...

          Page Loading...

          Structure

            Activity

              People

                r.laing Laing, Robert
                r.brederode Brederode, Ray
                Votes:
                0 Vote for this issue
                Watchers:
                3 Start watching this issue

                Feature Progress

                  Story Point Burn-up: (100.00%)

                  Feature Estimate: 3.0

                  IssuesStory Points
                  To Do00.0
                  In Progress   00.0
                  Complete1341.0
                  Total1341.0

                  Dates

                    Created:
                    Updated:
                    Resolved:

                    Structure Helper Panel