AssignResourcesLow

The AssignResources command allocates telescope resources to a specific subarray in the SKA-Low telescope configuration.

1. Central Node provides API for AssignResources workflow.

2. Input JSON is as per schema detailed at - https://developer.skao.int/projects/ska-schemas/en/latest/schemas/tmc/ska-low-tmc-assignres.html

3. The Central Node accepts the AssignResources command with a JSON input which specifies the sub-array ID and resource specifications for MCCS, CSP, and SDP.

4. The Central Node accepts the command if :-

   1. Admin mode reported by each of the system - CSP,SDP,MCCS controller are in ONLINE/ENGINEERING/RESERVED

   2. Operational state of central node is ON/OFF/INIT/STANDBY/ALARM

5. The Central Node rejects the command if :-

   1. Admin mode reported by each of the system - CSP,SDP,MCCS controller are in OFFLINE or NOT FITTED.

   2. Operational state of central node is FAULT/UNKNOWN/DISABLE .

6. The Input JSON is validated as below, and Command is ‘Rejected’ with exception message if they are not met :-

   1. JSON should not be empty or malformed

   2. JSON validation against the schema specified in the Telescope Model (https://developer.skao.int/projects/ska-schemas/en/latest/schemas/tmc/ska-low-tmc-assignres.html)

7. CentralNode validates the pss beam_ids in assign json:

   • If already assigned to different SubarrayNode: Command is rejected with ‘RESULT_CODE - REJECTED’ with a message mentioning the exact pss beam ids that are already assigned to different subarray.

   • If not already assigned to different SubarrayNode: Command execution continues

8. The following state requirements are applied for the command execution :-

   1. TMC Subarray is in ‘observation state’ EMPTY or IDLE . If not, the command is rejected with ‘ResultCode - NOT_ALLOWED’.

   2. telescopeAvailability is checked to ensure the subsystems (SubarryNode, CSP, SDP and MCCS) are available

9. The command execution involves below key operations :-

   1. ‘transaction ID’ is removed from the input JSON

   2. The command is then invoked on the relevant TMC Subarray Node.

      • If TMC Subarray node rejects assign resources command , command failure is reported as ‘RESULT_CODE - FAILED’ on Long Running Command Result attribute of the central node.

      • If TMC Subarray node accepts command , central node will wait for command completion.

10. The Central Node monitors the progress of command via the subarray ObsState transitions and the long running command results :-

    • Command is successful when the TMC Subarray Node transitions to IDLE ObsState. This is reported as ‘RESULT_CODE - OK’ on Long Running Command Result attribute of the central node.

    • Command failure is reported in any of the below cases as ‘RESULT_CODE - FAILED’ on Long Running Command Result attribute of the central node:

      1. The TMC subarray node reports ‘RESULT_CODE - FAILED’ on its Long Running Command Result attribute

      2. The command times out if TMC SubarrayNode does not transition to IDLE within the timeout period specified by CommandTimeOutDefault property specified in helm chart of TMC central node .