Snakemake SLURM Workflow Architecture FAQs

Question 1

Is this skill compatible with Snakemake 8.0?

Accepted Answer

Yes, it is designed for Snakemake 8.0 and above, specifically leveraging the snakemake-executor-plugin-slurm for modern cluster interactions.

Question 2

Can this architecture handle both GPU and CPU jobs?

Accepted Answer

Yes, it supports both. However, it prioritizes GPU-only scheduling for intensive tasks like BaSiC fitting to avoid the 15-20x performance penalty of CPU fallbacks.

Question 3

How does this skill handle multi-account SLURM routing?

Accepted Answer

It uses lambda functions within the Snakemake 'resources' block to dynamically assign the correct slurm_account and partition based on the job's requirements and wildcard values.

Question 4

Why are sentinel files used instead of standard file outputs?

Accepted Answer

In workflows like image stitching that produce hundreds of files per cycle, declaring every file as an output creates a fragile and slow DAG. Sentinel files provide a single source of truth for step completion.

Question 5

What happens if a multi-channel job is interrupted?

Accepted Answer

The workflow includes internal wrapper logic that checks for completed channels before processing, allowing jobs to resume exactly where they left off even if the Snakemake sentinel wasn't written.

Snakemake SLURM Workflow Architecture

Key Features

Use Cases

Snakemake SLURM Workflow Architecture

Key Features

Use Cases