ReleaseAllResources#

  1. The subarray Node provides API for ReleaseAllResources workflow.

  2. The SubarrayNode accepts the command if :-

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

    2. Operational state of the SubarrayNode is ON/OFF/INIT/STANDBY/ALARM

  3. The SubarrayNode rejects the command if :-

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

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

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

    1. TMC Subarray is in ‘observation state’ EMPTY or IDLE .

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

  5. The command execution involves below key operations :-

    1. Only for MCCS, interface is added in input JSON. For CSP and SDP, no JSON is sent to leaf nodes.

    2. The command is then invoked on the relevant TMC CSP, SDP, MCCS leaf Nodes.

      • If leaf node rejects release resources command , command failure is reported as ‘RESULT_CODE - FAILED’ on Long Running Command Result attribute of the TMC Subarray node.Command will not be sent to remaining subsystems in this case if multiple subsystems are involved .

      • If all leaf node accept command , the TMC Subarray node will wait for command completion.

  6. The SubarrayNode monitors the progress of command via the SubarrayNode ObsState transitions and the long running command results.

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

    2. Command failure is reported in any of the below cases as ‘RESULT_CODE - FAILED’ on Long Running Command Result attribute of the Subarray node.

      • The CSP Leaf node/SDP Leaf node/MCCS Leaf node reports ‘RESULT_CODE - FAILED’ on its Long Running Command Result attribute

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

  7. On success the system is ready for fresh observation; on failure it may revert to IDLE or FAULT depending on severity.

  8. When all targeted subsystems report successful completion, cleanup on the TMC subarray node proceeds.Stored science block ID, subarray ID, and internal resource caches are cleared. Assigned resources attribute is reset.

Show Source