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

TDC MVP1 Build 1 - Execute Test Plan (Part 2)

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

Details

    • Feature
    • Must have
    • PI15
    • None
    • Obs Mgt & Controls
    • Hide

      Integration of the end-to-end signal chain for one receptor / one frequency slice will reduce the risk of integration during TDC AA0.5 Build 1.

       

      Show
      Integration of the end-to-end signal chain for one receptor / one frequency slice will reduce the risk of integration during TDC AA0.5 Build 1.  
    • Hide

      TDC MVP1 test plan is executed and tests pass.

      Show
      TDC MVP1 test plan is executed and tests pass.
    • 3
    • 5
    • 40
    • 13.333
    • Team_CIPA
    • Sprint 5
    • Hide

      Have written a substantial amount of software to configure the FPGA, receive visibilities using SPEAD, then analyse the data (with pandas) and plot (with plotly). This is executed from a jupyter notebook. The notebook allows you to configure the test, setting parameters for the BITE and data-path configuration. 

      A python script run_tests.py will run through the notebook multiple times enabling each of the test configurations in turn. When a notebook execution is complete, it is rendered as an html document in the results directory

      The html renderings of the notebooks are attached to the respective Jira story tickets.

      Code is committed in the tdc_vcc_processing repository in the hw_testing directory.
      https://gitlab.drao.nrc.ca/SKA/Mid.CBF/FW/persona/tdc_vcc_processing/-/tree/hw_testing/hw_testing

      Some additional work has been done to bring up 4 FSP paths. These can be used to simultaneously process 4 frequency slices as 4 different subarrays.  This is used for test 0.6 to run identical data through with different integration times.

      Show
      Have written a substantial amount of software to configure the FPGA, receive visibilities using SPEAD, then analyse the data (with pandas) and plot (with plotly). This is executed from a jupyter notebook. The notebook allows you to configure the test, setting parameters for the BITE and data-path configuration.  A python script run_tests.py will run through the notebook multiple times enabling each of the test configurations in turn. When a notebook execution is complete, it is rendered as an html document in the results directory The html renderings of the notebooks are attached to the respective Jira story tickets. Code is committed in the tdc_vcc_processing repository in the hw_testing directory. https://gitlab.drao.nrc.ca/SKA/Mid.CBF/FW/persona/tdc_vcc_processing/-/tree/hw_testing/hw_testing Some additional work has been done to bring up 4 FSP paths. These can be used to simultaneously process 4 frequency slices as 4 different subarrays.  This is used for test 0.6 to run identical data through with different integration times.
    • 15.6
    • Stories Completed, Integrated, Outcomes Reviewed, Demonstrated, Satisfies Acceptance Criteria, Accepted by FO

    Description

      Execute TDC MVP1 test plan (see attached).

       

       

       

       

      Attachments

        Issue Links

          Structure

            Activity

              People

                b.alachkar Alachkar, Bassem
                S.Harrison Harrison,Stephen
                Votes:
                0 Vote for this issue
                Watchers:
                1 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
                  Complete621.0
                  Total621.0

                  Dates

                    Created:
                    Updated:
                    Resolved:

                    Structure Helper Panel