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

Exercising control flow through OET to Tango devices through Observing scripts

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

Details

    • Feature
    • Not Assigned
    • PI3
    • None
    • Hide

      Exercising the OET's ‘Observing Script to Observing Task’ interface and ‘Observing Task to TMC device’ interface will continue to establish the viability of the OET's core architecture and put in place the initial stages of being able to execute simple observations controlling virtual systems via TMC TANGO devices. This creates a platform that can be extended. The first extension - to be able to parse a simple SB instance - is proposed in SP-302.

      Show
      Exercising the OET's ‘Observing Script to Observing Task’ interface and ‘Observing Task to TMC device’ interface will continue to establish the viability of the OET's core architecture and put in place the initial stages of being able to execute simple observations controlling virtual systems via TMC TANGO devices. This creates a platform that can be extended. The first extension - to be able to parse a simple SB instance - is proposed in SP-302 .
    • Hide

      Pre-condition: a sub array has been created using the resource allocation scripts developed in SP-142.

      A simple observing script is executed taking as input arguments a set of pointing positions in RA,Dec, and a scan length. This script should run appropriate Observing Tasks that will configure the system and then scan to observe, for each pointing position.

      The result of executing these Tasks is that configure and scan Tango commands are issued and the TMC prototype commands the virtual dishes in the sub-array to track at each pointing position(s) and scan at each position in a sequence.

      NOTE: This should be a simple, first, observing script. It is expected to execute in a single thread, and there is no expectation of implementing the entire State Control Model.

      Show
      Pre-condition: a sub array has been created using the resource allocation scripts developed in SP-142 . A simple observing script is executed taking as input arguments a set of pointing positions in RA,Dec, and a scan length. This script should run appropriate Observing Tasks that will configure the system and then scan to observe, for each pointing position. The result of executing these Tasks is that configure and scan Tango commands are issued and the TMC prototype commands the virtual dishes in the sub-array to track at each pointing position(s) and scan at each position in a sequence. NOTE: This should be a simple, first, observing script. It is expected to execute in a single thread, and there is no expectation of implementing the entire State Control Model.
    • 4
    • 4
    • 10
    • Team_BUTTONS
    • Sprint 3
    • 3.6
    • PI22 - UNCOVERED

    • Team_BUTTONS

    Description

      Following on from the work done in SP-142, where resource allocation was demonstrated through the OET to Tango devices, this feature goes a step further to ensure that some simple configuration and scanning can be done using a defined observing script. This is a pre-cursor to SP-302 which will introduce the concept of using a simple scheduling block instance to perform the same,

       

      This feature exercises the flow of information through Figure 71 of the OSO SAD (attached as a single figure to SP-142) from the Observing script (in the script layer) to the observing task (in the observing task layer) to the command executor (in the OET domain layer) and then onto Tango. It will also exercise (and depend upon) a simple API provided by the TMC for configuring the system for a scan.

      Attachments

        Issue Links

          Structure

            Activity

              People

                a.bridger Bridger, Alan
                p.klaassen Klaassen, Pamela
                Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Feature Progress

                  Story Point Burn-up: (0%)

                  Feature Estimate: 4.0

                  IssuesStory Points
                  To Do00.0
                  In Progress   00.0
                  Complete00.0
                  Total00.0

                  Dates

                    Created:
                    Updated:
                    Resolved:

                    Structure Helper Panel