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

Integrate CBF-SDP emulator into the CBF LMC (and SKAMPI)

Details

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

      The goal is reduction of risk of the most critical CBF-SDP interface (visibility exchange). While we have both CBF simulators and receive workflows, we need to ensure that LMCs can suitably coordinate them. Therefore it seems like we should attempt at least a basic simulator integration as a starting point for future experimentation, especially towards PSI deployments.

      Show
      The goal is reduction of risk of the most critical CBF-SDP interface (visibility exchange). While we have both CBF simulators and receive workflows, we need to ensure that LMCs can suitably coordinate them. Therefore it seems like we should attempt at least a basic simulator integration as a starting point for future experimentation, especially towards PSI deployments.
    • Hide
      1. Provide a CBF LMC that can spawn CBF visibility simulator. Either by providing a new implementation or adapting existing LMC code.
      2. Operation with configuration, receive addresses, and a SPEAD stream parametrised as appropriate for a PSI. Especially means that we can assume just one receive node for the moment.
      3. Demonstrate that the entire chain can be controlled via OET Tango interface (stretch) or equivalent administration interface.
      4. Code review by a member of a CBF LMC team
      5. Demonstrate visibilities getting exchanged. Use statically configured IPs / DNS addresses if too much work is needed to make the receive addresses exchange work correctly
      Show
      Provide a CBF LMC that can spawn CBF visibility simulator. Either by providing a new implementation or adapting existing LMC code. Operation with configuration, receive addresses, and a SPEAD stream parametrised as appropriate for a PSI. Especially means that we can assume just one receive node for the moment. Demonstrate that the entire chain can be controlled via OET Tango interface (stretch) or equivalent administration interface. Code review by a member of a CBF LMC team Demonstrate visibilities getting exchanged. Use statically configured IPs / DNS addresses if too much work is needed to make the receive addresses exchange work correctly
    • 3
    • 3
    • 8.667
    • Team_YANDA
    • Sprint 5
    • Hide

      AC1: YAN-445 - tango device starts/stops sending of data following the observation state machine; derived from SKASubarray base class; implements the Configure, Scan and Abort commands; added pytest-bdd unittests
      AC2: YAN-447 - sysdemo 8.3 demo clip:
      https://drive.google.com/file/d/12M3i4_6yCiIAelS_koG9k_M8g5YPOxNX/view?usp=sharing
      AC3: YAN-449 - not done. OET integration deferred to possible follow-up in PI9
      AC4: SDR-330 - code review by CREAM team's E. Giani https://jira.skatelescope.org/secure/attachment/17517/CT148_yanda.pdf
      AC5: YAN-459 - sysdemo 8.3 demo clip:
      https://drive.google.com/file/d/12M3i4_6yCiIAelS_koG9k_M8g5YPOxNX/view?usp=sharing

      Show
      AC1: YAN-445 - tango device starts/stops sending of data following the observation state machine; derived from SKASubarray base class; implements the Configure, Scan and Abort commands; added pytest-bdd unittests AC2: YAN-447 - sysdemo 8.3 demo clip: https://drive.google.com/file/d/12M3i4_6yCiIAelS_koG9k_M8g5YPOxNX/view?usp=sharing AC3: YAN-449 - not done. OET integration deferred to possible follow-up in PI9 AC4: SDR-330 - code review by CREAM team's E. Giani https://jira.skatelescope.org/secure/attachment/17517/CT148_yanda.pdf AC5: YAN-459 - sysdemo 8.3 demo clip: https://drive.google.com/file/d/12M3i4_6yCiIAelS_koG9k_M8g5YPOxNX/view?usp=sharing
    • 8.6
    • Stories Completed, Integrated, Solution Intent Updated, BDD Testing Passes (no errors), Outcomes Reviewed, NFRS met, Demonstrated, Accepted by FO
    • PI22 - UNCOVERED

    • SPO-705 SPO-706

    Description

      Proposal TANGO device that spawns the emulator / sender and reacts to scan requests. Minimal configurability, see user scenario:

      Ella executes the script providing some specific parameters as input, for example AZ/EL , correlator dump time, scan length.

      [...] During the script execution, Ella tweaks some parameters of the system like adding a constant delay to make sure that the system is reacting correctly.

      How delays would be configured is unclear right now (writeable Tango attributes?), so implementing this would be a stretch goal if we can come up with a design.

      Attachments

        Issue Links

          Structure

            Activity

              People

                p.wortmann Wortmann, Peter
                b.mort Mort, Ben
                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
                  Complete714.0
                  Total714.0

                  Dates

                    Created:
                    Updated:
                    Resolved:

                    Structure Helper Panel