Any way to rerun the aborted task after bug fixes(mostly last task) without starting from square one

Cylc Cylc Support
1

Hi :
As I am putting more and more tasks into my workflow, starting workflow from very beginning is very time consuming. Generally, I do “cylc vip .”, which always start from task#1. Is there any way to rerun the aborted task in the same run directory?
-Similarly in cylc gui, is it possible to do :

  1. see all my tasks of workflow at the same time on current screen as it is running. Currently it is showing only last one or 2, on which it working i.e. completed one disappeared. May suggest to display all tasks of workflow in the beginning, and show the activity(colour changes) as time goes along.
  2. how can I restart aborted task in same run after fixes# i.e. workflow, which is already played.
  3. Is it possible to replay in GUI same workflow again and again. Currently it allows only once. Useful, when you are giving demo to someone. Currently, one has to reinstall into different directory to replay.
  4. Not sure, this functionality already there or not… you click on a task, it gives menu with different options such as a) see job listing b) resubmit task c)what machine running, its wall clock time, memory, #of cpus etc. d) give a terminal so that one can fix task script etc.
2

Hi,

There are two ways in which you can edit a task’s configuration on-the-fly:

  1. Edit and reload the workflow’s flow.cylc file:
    • Edit the task’s definition in the flow.cylc file.
    • Run the cylc vr command to reinstall the workflow and reload its configuration.
    • To run the task again (with the newly amened configuration), trigger it.
  2. Edit the task configuration in the GUI:
    • This functionality is currently only available for tasks which are visible in the GUI.
    • Click on the task and select “Edit Runtime”.
    • This brings up a form displaying the task’s full configuration, which you can then edit.
    • Any changes made apply just to the specific instance of the selected task(s), i.e, the changes made don’t propagate forward to future cycles.
    • This makes it a good feature for trying out changes e.g, during workflow development, for debugging, or dev-ops work.

FYI: You might find the interventions section of the docs helpful here, it provides examples of common Cylc interventions, with screen recordings of how to perform them.

Answers to the remaining points above:

see all my tasks of workflow at the same time on current screen as it is running

  • The GUI provides a “live” view which doesn’t presently offer the ability to go “all the way back” through the workflow’s history.
  • However, you can use the “n=” selector in the toolbar to widen/shrink the view Cylc presents.
  • But you can still operate on tasks even if you can’t see them (see this example, then enter the cycle/family/task you want to operate on).

i.e. workflow, which is already played.

  • A workflow which has reached the end of the graph is said to have run to completion.
  • If you restart a “completed” workflow, the GUI will (initially) be blank as there are no tasks left for Cylc to schedule.
  • But you can still (re)trigger tasks, you’ll just have to enter the cycle / family or task name(s) you want to trigger manually (like this).

Is it possible to replay in GUI same workflow again and again

  • “Replaying” in this way, causes the workflow to re-run over the top of the previously data, so is generally advised against.
  • However, cylc trigger '<workflow>//^' --flow=new will do the job if desired.
    • ^ is an alias for the initial cycle point
    • --flow=new will cause Cylc to “run on” from the triggered tasks.

Cheers,
Oliver

2 Likes