From 326be00670c46532eb84a0b8db4139bc0dddacb1 Mon Sep 17 00:00:00 2001 From: "Michael R. Crusoe" Date: Tue, 11 Jul 2023 11:05:02 +0200 Subject: [PATCH] Monitoring a running toil-cwl-runner --- docs/computing/running/toil-cwl-runner.md | 9 ++++++--- 1 file changed, 6 insertions(+), 3 deletions(-) diff --git a/docs/computing/running/toil-cwl-runner.md b/docs/computing/running/toil-cwl-runner.md index 0cad2d3a71..9e7809bc58 100644 --- a/docs/computing/running/toil-cwl-runner.md +++ b/docs/computing/running/toil-cwl-runner.md @@ -21,10 +21,10 @@ This page describes how run CWL worklflows on Puhti using `toil-cwl-runner`, inc ## Strengths of `toil-cwl-runner` - Supports sending jobs to Slurm, translating CWL resource requirements to Slurm resources specifications. +- Even when using Slurm, (sub-)tasks do not have to have identical resource requirements. - Can also run on other batch systems: Grid Engine, Torque, LSF, HTCondor. -- Launches and monitors Slurm jobs for you. Also constructs the apptainer commands. - -## Disadvantages for using CWL +- Launches and monitors Slurm jobs for you. Also constructs the `apptainer` commands (or some other software container engine as appropriate: `docker`, `podman`, `singularity`, `udocker`). +- No database needs to be setup. ## Disadvantages for using `toil-cwl-runner` - Just a workflow runner. Won't manage your data, or keep track of previous workflow runs. @@ -114,3 +114,6 @@ sbatch workflow.sh ``` ## Monitoring a running workflow + +Check the output logs from the main Toil job or +run `toil status $WORKDIR/`.