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

Testing signal chain in the LOW-PSI

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

Details

    • Services
    • Hide

      To establish connection and software monitoring and control of the signal chain required for the ITF.
      This is to demonstrate a real hardware connected system.
       

       

      Show
      To establish connection and software monitoring and control of the signal chain required for the ITF. This is to demonstrate a real hardware connected system.    
    • Hide
      • Hardware system has been designed, implemented and installed in the PSI LOW
      • Control via TANGO devices has been established
      • A Jupyter notebook demo has been provided
      • unchannelised data has been captured
      • a BDD test can be run from the gitlab-ci pipeline
      Show
      Hardware system has been designed, implemented and installed in the PSI LOW Control via TANGO devices has been established A Jupyter notebook demo has been provided unchannelised data has been captured a BDD test can be run from the gitlab-ci pipeline
    • 2
    • 2
    • 0
    • Team_VULCAN
    • Sprint 5
    • Hide

      The hardware system of signal generator, noise sources and related input into the TPM was established (by the ITF Low team). This was connected up the the monitoring and control software in MCCS and debugged to a point where the capture of unchannelised could be demonstrated.
      This however couldn't be extended to be automated via a BDD test as the MCCS software wasn't ready and released in time and the system unstable. However, it proved invaluable to executed and test the system, so it can be stabilised and released in PI17.
      So not all Acceptance criteria could be fulfilled.

      Continuation is in SP-3004

      Show
      The hardware system of signal generator, noise sources and related input into the TPM was established (by the ITF Low team). This was connected up the the monitoring and control software in MCCS and debugged to a point where the capture of unchannelised could be demonstrated. This however couldn't be extended to be automated via a BDD test as the MCCS software wasn't ready and released in time and the system unstable. However, it proved invaluable to executed and test the system, so it can be stabilised and released in PI17. So not all Acceptance criteria could be fulfilled. Continuation is in  SP-3004
    • 16.6
    • Stories Completed, Integrated, Outcomes Reviewed, Accepted by FO
    • PI24 - UNCOVERED

    Description

      1. Install a signal generator in the PSI. Get it on the network and plugged into a TPM and the frequency reference.
      2. Implement frequency reference monitoring and control into the signal generator.
      3. Deploy ITF setup to the PSI (jupytango, gitlab runner, taranta, etc)
      4. Deploy DAQ and its LMC into the PSI. The main challenge here is that MCCS are currently implementing DAQ funcitonality into MccsStation, and we don't want to deploy an MccsStation instance here. It would be nicer to have a separate MccsDaq device.
      5. A helm chart that deploys a single MccsTile device, a single MccsDaq device, and a single SignalGeneratorDevice.
      6. A BDD test that configures the three devices (with MccsTile configured to send unchannelised data to the DAQ), then sets signal flow going, then checks that a DAQ file is created. Then we give that DAQ file to @Ravi Subrahmanyan to analyse offline.
      7. A BDD test that configures the three devices (with MccsTile configured to send channelised data to the DAQ), then sets signal flow going, then checks that a DAQ file is created. Then we give that DAQ file to Ravi to analyse offline.
      8. Add a step to BDD tests that use Ravi's test scripts, get quantitative metrics, and pass or fail depending on whether those metrics are good enough.

      Attachments

        Issue Links

          Structure

            Activity

              People

                Felipe.Gonzalez Gonzalez, Felipe
                Vani.Naram Naram, Vani
                Votes:
                0 Vote for this issue
                Watchers:
                1 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
                  Complete815.0
                  Total815.0

                  Dates

                    Created:
                    Updated:
                    Resolved:

                    Structure Helper Panel