Abort

1. Dish Leaf Node provides API for Abort workflow.

2. The Dish Leaf Node accepts the command unconditionally :-

   1. No checks on DishMode, PointingState, or current operation.

   2. Designed to interrupt any ongoing activity and force the system into a safe ABORTED state.

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

   1. Dish Master must be responsive (TANGO device proxy and adapter must initialize successfully).

   2. No dependency on current dish operating mode or pointing state.

4. No input JSON validation is performed :-

   1. The Abort command requires no input arguments.

   2. No JSON parsing or schema validation is needed.

5. The command execution involves the following key operations :-

   1. Trigger global abort signal

      • abort_event is set to notify all background tasks and observers.

      • TANGO clients are notified of state changes via attribute update.

      • abort_event is cleared immediately after.

   2. Terminate all ongoing internal tasks

      • All background operations (e.g., tracking, configuration) are aborted.

      • Progress is reported in two phases:

        1. 0-50%: Completion of internal task termination.

        2. 50-100%: Completion of Abort on Dish Master and track table stop.

   3. Invoke Abort on Dish Master (conditional)

      • If is_dish_abort_commands_enabled == True:

        1. Abort() command is sent to Dish Master via adapter.

        2. A unique command ID is recorded for tracking.

      • If Dish Master returns REJECTED, NOT_ALLOWED, or ABORTED → command fails immediately with same result.

      • Otherwise, execution continues (long-running command).

   4. Stop ProgramTrackTable generation

      • StopProgramTrackTable() is invoked on the Dish LN Pointing Device.

      • On failure:

        1. Error is logged.

        2. Health state is updated to DEGRADED.

        3. Command fails with ResultCode.FAILED.

   5. Clear residual track table errors

      Any stored track table errors are reset.

6. The TMC Dish Leaf Node monitors progress via task callbacks and timeout tracking :-

   1. Command reports ResultCode.STARTED immediately after:

      1. Adapter initialization.

      2. Issuing Abort (if enabled) and StopProgramTrackTable.

      3. Final success/failure is reported asynchronously.

   2. Success criteria (reported as TaskStatus.COMPLETED)

      1. All internal tasks are terminated.

      2. StopProgramTrackTable completes without error.

      3. Abort command (if sent) is accepted by Dish Master.

      4. Progress reaches 100% via callback.

   3. Failure is reported in any of the following cases (TaskStatus.FAILED)

      1. Dish Master adapter fails to initialize.

      2. StopProgramTrackTable() raises an exception → health DEGRADED.

      3. Internal task abortion fails.

      4. Timeout: Command exceeds command_timeout (configured via TimeKeeper) → automatic failure.

7. No input JSON schema

   • The Abort command accepts no input.

   • No reference to external schema (unlike Configure command).

   • Schema URL: Not applicable