Skip to content

Execution Paths

Nil Mu edited this page Sep 23, 2026 · 1 revision

Execution paths

Check the requirements for the tools needed by each treatment.

Workflow manager Native Slurm Job arrays HyperQueue Flux Local in allocation
Nextflow Yes Yes Yes Yes Yes
Snakemake Yes Yes — — —

Nextflow. native submits eligible tasks individually, jobarray uses Nextflow's Slurm-array support, hyperqueue and flux dispatch inside fresh enclosing allocations, and local executes inside one Slurm allocation.

Snakemake. The current adapters use the official Slurm executor plugin. The array treatment additionally enables its job-array option. WfTune does not claim Snakemake support for HyperQueue, Flux, or local execution yet.

Choosing a comparison

Use the same scientific endpoint and frozen inputs across treatments. Compare backends within one workflow manager, or select the shared native and jobarray treatments for a Nextflow/Snakemake comparison.

See the campaign guide for collection and the analysis guide for cross-WMS analysis.

Clone this wiki locally