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

Control the MVP using the first Scheduling Block Instances

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

Details

    • Obs Mgt & Controls
    • Hide

      Continues the de-risking of the OET design and also begins the process of integrating with the important Scheduling Block data model, initial stages of integrating with the rest of the OSO system and also collaborating with the Architecture team.
       

      Show
      Continues the de-risking of the OET design and also begins the process of integrating with the important Scheduling Block data model, initial stages of integrating with the rest of the OSO system and also collaborating with the Architecture team.  
    • Hide

      This is similar to SP-301 except that the MVP configuration supplied to the Observing Script (i.e., the target positions, CSP and SDP configurations, scan duration) are defined in an SB instance rather than directly defined as CDM JSON. The structure of the SB Instance will follow the data model definition provided by the architecture team in SP-172.

      Resource allocation prior to the SBI execution can be as in SP-142, but as a stretch goal an optional addition would be to take resource requirements from the simple SB instance.

      As with SP-301 this should be a simple, single threaded, single sub-array observation with no handling of external inputs or interrupts during execution.

      Show
      This is similar to SP-301  except that the MVP configuration supplied to the Observing Script (i.e., the target positions, CSP and SDP configurations, scan duration) are defined in an SB instance rather than directly defined as CDM JSON. The structure of the SB Instance will follow the data model definition provided by the architecture team in SP-172 . Resource allocation prior to the SBI execution can be as in SP-142 , but as a stretch goal an optional addition would be to take resource requirements from the simple SB instance. As with SP-301 this should be a simple, single threaded, single sub-array observation with no handling of external inputs or interrupts during execution.
    • 8
    • 6
    • 3.75
    • Team_BUTTONS
    • Sprint 5
    • 6.6

    • PI22 - UNCOVERED

    Description

      In SP-301, Observing Scripts controlled the MVP by relaying externally defined Configuration Data Model (CDM) entities to TMC. These CDM entities were prepared offline and stored on disk. The Observing Script did not create the CDMs and had to do only minimal parsing of them before relaying the CDM entities to TMC SubArrayNodes. While SP-301 resulted in successful sub-array control, it does not reflect the final design where observations are defined in Scheduling Blocks and not in hard-coded Configuration Data Model entities. 

      The next step is to evolve to the standard observing scenario where the Observing Script input takes the form of the first Scheduling Block Instances (SBI). The function of the Observing Script then becomes to parse and interpret the SBIs, convert them (in memory) to CDMs, and then relay the fully defined CDM scan configurations to TMC as/when required to perform an observation. The data flow would then accurately reflect the CDR design where observations defined in the science-focussed, flexible, slightly generalised SBI format are translated to the instrument-focussed, ICD-compliant CDMs, which then control the telescope.  

      There are three aspects to this feature:

      1. Create a Python representation of the SB Instance data model.
      2. Create a shared library that can marshall Python SB Instances to/from a serialised format (assumed to be JSON).
      3. Modify the Observing Scripts to make use of the SB shared library, inserting a conversion step that translates a SBI to equivalent CDMs, then use the CDMs to control the MVP. 

      This feature has a dependency on the delivery of an initial Scheduling block definition (SP-172)

      Attachments

        Issue Links

          Child Of

          Capability - SAFe program capability SS-37 Enable multi-scan capability in the MVP, including reconfigurations

          • Should have - Items labelled as "Should have" are important but not necessary for delivery in the current delivery timebox. While "Should have" items can be as important as "Must have", they are often not as time-critical or there may be another way to satisfy the requirement so that it can be held back until a future delivery timebox.
          • Done
          depends on

          Enabler - An Enabler supports the activities needed to extend the Architectural Runway to provide future business functionality. These include exploration, architecture, infrastructure, and compliance. SP-172 Scheduling Block definitions

          • Not Assigned - Priority is not assigned yet.
          • Done
          is cloned by

          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-1021 CLONE - Control the MVP using the first Scheduling Block Instances

          • Not Assigned - Priority is not assigned yet.
          • Done
          relates to

          Capability - SAFe program capability SS-14 Simple Subarray LMC Control

          • Must have - Items labelled as "Must have" are critical to the current delivery timebox in order for it to be a success.
          • 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-826 system tests for newer "MVP"

          • Not Assigned - Priority is not assigned yet.
          • Done
          mentioned in

          Page Loading...

          Page Loading...

          Page Loading...

          Page Loading...

          Structure

            Activity

              People

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

                Feature Progress

                  Story Point Burn-up: (100.00%)

                  Feature Estimate: 8.0

                  IssuesStory Points
                  To Do00.0
                  In Progress   00.0
                  Complete1025.5
                  Total1025.5

                  Dates

                    Created:
                    Updated:
                    Resolved:

                    Structure Helper Panel