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

The schemata provided in the Telescope Model is updated to the aim CSP.LMC can verify the various JSON scripts for the commands neded to execute a scan

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

Details

    • Obs Mgt & Controls
    • Hide

      When this feature is completed CSP  LMC will be able to verify the correctness and completeness of the Json script  for the commands assign resources and configure.

      Show
      When this feature is completed CSP  LMC will be able to verify the correctness and completeness of the Json script  for the commands assign resources and configure.
    • Hide

      Telescope Model contains the following:

      • JSON  Schema for CSP LMC LOW command Assign Resources
      • JSON Schema for CSP LMC LOW command Configure
      • JSON Schema for CSP LMC MID command Assign Resources
      • JSON Schema for CSP LMC MID command Configure
      • JSON Schema for PST LOW command Configure
      • JSON Schema for PST MID command Configure

      Note: In the case that PST schemata is identical for the LOW and MID Telescope, only one schema instance is provided for each command.

      Behavior:

      Given CSP.LMC Subarray  where obsState=EMPTY 
      When CSP.LMC Subarray receives an assign resources command that passes correctly specified JSON script
      Then CSP.LMC accepts the command, transitions to obsState=RESOURCING, successfully completes the resourcing and transitions to obsState=IDLE.

      Given CSP.LMC Subarray  where obsState=EMPTY
      When CSP.LMC Subarray receives an assign resources command that passes incorrect or incomplete JSON script
      Then CSP.LMC [rises an exception | answers with the return code "wrong argument"  ] and remains in obsState=EMPTY.

      Given CSP.LMC Subarray  where obsState=IDLE 
      When CSP.LMC Subarray receives a Configure command that passes correctly specified JSON script
      Then CSP.LMC accepts the command,  transitions to obsState=CONFIGURING, successfully completes configuring and transitions to obsState=READY.

      Given CSP.LMC Subarray  where obsState=IDLE
      When CSP.LMC Subarray receives a Configure  command that passes incorrect or incomplete JSON script
      Then CSP.LMC [rises an exception | answers with the return code "wrong argument"  ] remains in obsState=IDLE.

      Given CSP.LMC Subarray  where obsState=READY 
      When CSP.LMC Subarray receives a Configure command that passes correctly specified JSON script
      Then CSP.LMC accepts the command,  transitions to obsState=CONFIGURING, successfully completes configuring and transitions to obsState=READY.

      Given CSP.LMC Subarray  where obsState=READY
      When CSP.LMC Subarray receives a Configure  command that passes incorrect or incomplete JSON script
      Then CSP.LMC [rises an exception | answers with the return code "wrong argument"  ] remains in obsState=READY  and the Subarray configuration remains unchanged.

      Note: When an invalid JSON script is received, whether CSP.LMC rises an exception or answers with the return code "wrong argument"  depends on the type of error in the JSON script. (To Be Confirmed).

      CSP.LMC tests for the command configure shall be repeated at least for the following observing modes:

      a) scan that performs only correlation

      b) scan that performs correlation and PST beamforming and capture (the actual Pulsar Timing is not supported in this release).

       

      PST does not implement Assign Resources, and shall pass the tests for Configure command.

      The following shall be repeated for LOW and MID (to be confirmed):

      Given an instance of PST Beam/Pipeline where obsState=IDLE 
      When PST Beam/Pipeline receives a Configure command that passes correctly specified JSON script
      Then PST Beam/Pipeline accepts the command,  transitions to obsState=CONFIGURING, successfully completes configuring and transitions to obsState=READY.

      Given an instance of PST Beam/Pipeline where obsState=IDLE
      When PST Beam/Pipeline receives a Configure  command that passes incorrect or incomplete JSON script
      Then PST Beam/Pipeline [rises an exception | answers with the return code "wrong argument"  ] remains in obsState=IDLE.

      Given an instance of PST Beam/Pipeline where obsState=READY 
      When PST Beam/Pipeline receives a Configure command that passes correctly specified JSON script
      Then PST Beam/Pipeline accepts the command,  transitions to obsState=CONFIGURING, successfully completes configuring and transitions to obsState=READY.

      Given an instance of PST Beam/Pipeline where obsState=READY
      When PST Beam/Pipeline receives a Configure  command that passes incorrect or incomplete JSON script
      Then PST Beam/Pipeline [rises an exception | answers with the return code "wrong argument"  ] remains in obsState=READY  and the Subarray configuration remains unchanged.

       

      Initially suggested behavior :

      Given CSP.LMC correctly connected with one component
      When CSP.LMC receive a configuration or assign resources command
      Then CSP.LMC can asses the correctness and completeness of Json argument

      Given CSP.LMC correctly connected with PST.LMC
      When CSP.LMC receive an invalid or incomplete configuration or assign resources command
      Then CSP.LMC [rises an exception | answer with wrong argument return code ] and does not transition to next steady state

      Show
      Telescope Model contains the following: JSON  Schema for CSP LMC LOW command Assign Resources JSON Schema for CSP LMC LOW command Configure JSON Schema for CSP LMC MID command Assign Resources JSON Schema for CSP LMC MID command Configure JSON Schema for PST LOW command Configure JSON Schema for PST MID command Configure Note: In the case that PST schemata is identical for the LOW and MID Telescope, only one schema instance is provided for each command. Behavior: Given CSP.LMC Subarray  where obsState=EMPTY  When CSP.LMC Subarray receives an assign resources command that passes correctly specified JSON script Then CSP.LMC accepts the command, transitions to obsState=RESOURCING, successfully completes the resourcing and transitions to obsState=IDLE. Given CSP.LMC Subarray  where obsState=EMPTY When CSP.LMC Subarray receives an assign resources command that passes incorrect or incomplete JSON script Then CSP.LMC [rises an exception | answers with the return code "wrong argument"  ] and remains in obsState=EMPTY. Given CSP.LMC Subarray  where obsState=IDLE  When CSP.LMC Subarray receives a Configure command that passes correctly specified JSON script Then CSP.LMC accepts the command,  transitions to obsState=CONFIGURING, successfully completes configuring and transitions to obsState=READY. Given CSP.LMC Subarray  where obsState=IDLE When CSP.LMC Subarray receives a Configure  command that passes incorrect or incomplete JSON script Then CSP.LMC [rises an exception | answers with the return code "wrong argument"  ] remains in obsState=IDLE. Given CSP.LMC Subarray  where obsState=READY  When CSP.LMC Subarray receives a Configure command that passes correctly specified JSON script Then CSP.LMC accepts the command,  transitions to obsState=CONFIGURING, successfully completes configuring and transitions to obsState=READY. Given CSP.LMC Subarray  where obsState=READY When CSP.LMC Subarray receives a Configure  command that passes incorrect or incomplete JSON script Then CSP.LMC [rises an exception | answers with the return code "wrong argument"  ] remains in obsState=READY  and the Subarray configuration remains unchanged. Note: When an invalid JSON script is received, whether CSP.LMC rises an exception or answers with the return code "wrong argument"  depends on the type of error in the JSON script. (To Be Confirmed). CSP.LMC tests for the command configure shall be repeated at least for the following observing modes: a) scan that performs only correlation b) scan that performs correlation and PST beamforming and capture (the actual Pulsar Timing is not supported in this release).   PST does not implement Assign Resources, and shall pass the tests for Configure command. The following shall be repeated for LOW and MID (to be confirmed): Given an instance of PST Beam/Pipeline where obsState=IDLE  When PST Beam/Pipeline receives a Configure command that passes correctly specified JSON script Then PST Beam/Pipeline accepts the command,  transitions to obsState=CONFIGURING, successfully completes configuring and transitions to obsState=READY. Given  an instance of PST Beam/Pipeline where obsState=IDLE When PST Beam/Pipeline receives a Configure  command that passes incorrect or incomplete JSON script Then PST Beam/Pipeline [rises an exception | answers with the return code "wrong argument"  ] remains in obsState=IDLE. Given  an instance of PST Beam/Pipeline where obsState=READY  When PST Beam/Pipeline receives a Configure command that passes correctly specified JSON script Then PST Beam/Pipeline accepts the command,  transitions to obsState=CONFIGURING, successfully completes configuring and transitions to obsState=READY. Given  an instance of PST Beam/Pipeline where obsState=READY When PST Beam/Pipeline receives a Configure  command that passes incorrect or incomplete JSON script Then PST Beam/Pipeline [rises an exception | answers with the return code "wrong argument"  ] remains in obsState=READY  and the Subarray configuration remains unchanged.   Initially suggested behavior : Given CSP.LMC correctly connected with one component When CSP.LMC receive a configuration or assign resources command Then CSP.LMC can asses the correctness and completeness of Json argument Given CSP.LMC correctly connected with PST.LMC When CSP.LMC receive an invalid or incomplete configuration or assign resources command Then CSP.LMC [rises an exception | answer with wrong argument return code ] and does not transition to next steady state
    • 3
    • 2
    • 0

    • Sub-system Version REL-1125 Telescope model with csp-low schema and validation in Low CSP.LMC

    • Team_CREAM
    • Sprint 5
    • Hide

      The PST schema has been separated from CSP schema and it has now its own repository and interface attribute. (ska-telmodel v 0.1.14). 
      The Low CSP schema has been created in the telescope model v 0.1.14. The ska-csp-lmc-low v. 0.12.0 (REL-1125) validates the command against it.
      The Mid CSP schema has not been modified in the telescope model
      The test cases for the CSP LMC have been implemented and they are linked to this ticket:
       XTP-32654
      XTP-32655 
       XTP-32656
      XTP-32657
      XTP-32658
      XTP-32659
      XTP-32720
      XTP-32721
      XTP-32722

      Show
      The PST schema has been separated from CSP schema and it has now its own repository and interface attribute. (ska-telmodel v 0.1.14).  The Low CSP schema has been created in the telescope model v 0.1.14. The ska-csp-lmc-low v. 0.12.0 ( REL-1125 ) validates the command against it. The Mid CSP schema has not been modified in the telescope model The test cases for the CSP LMC have been implemented and they are linked to this ticket:  XTP-32654 XTP-32655   XTP-32656 XTP-32657 XTP-32658 XTP-32659 XTP-32720 XTP-32721 XTP-32722
    • 22.5
    • Stories Completed, Integrated, Solution Intent Updated, BDD Testing Passes (no errors), Outcomes Reviewed, NFRS met, Demonstrated, Satisfies Acceptance Criteria, Accepted by FO

    • PI22 - UNCOVERED

    • CSP.LMC Team_CREAM

    Description

      The telescope model library let check the format and the minimum amount of information needed to configure and assign resource for various SKA elements. This feature aims at verifying and, in case, extend those functionalities for CSP and its components.

      Attachments

        Issue Links

          Child Of

          Capability - SAFe program capability SS-117 Com-C3: Sub-system level software release & delivery improvements

          • Must have - Items labelled as "Must have" are critical to the current delivery timebox in order for it to be a success.
          • Implementing
          depends on

          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-3193 Develop LOW CBF Schema for PST/COR

          • Must have - Items labelled as "Must have" are critical to the current delivery timebox in order for it to be a success.
          • Done
          Is delivered by

          Sub-system Version - A version of a sub-system, used in the Release Management and Configuration Management process REL-1125 Telescope model with csp-low schema and validation in Low CSP.LMC

          • Released
          mentioned in

          Page Loading...

          Structure

            Activity

              People

                a.bridger Bridger, Alan
                c.baffa Carlo Baffa
                Votes:
                0 Vote for this issue
                Watchers:
                2 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
                  Complete48.5
                  Total48.5

                  Dates

                    Created:
                    Updated:
                    Resolved:

                    Structure Helper Panel