Difference between revisions of "Snakemake"
Jump to navigation
Jump to search
Moskalenko (talk | contribs) |
|||
| Line 5: | Line 5: | ||
<!--CONFIGURATION: OPTIONAL (|1}} means it's ON)--> | <!--CONFIGURATION: OPTIONAL (|1}} means it's ON)--> | ||
|{{#vardefine:conf|}} <!--CONFIGURATION--> | |{{#vardefine:conf|}} <!--CONFIGURATION--> | ||
| − | |{{#vardefine:exe|}} <!--ADDITIONAL INFO--> | + | |{{#vardefine:exe|1}} <!--ADDITIONAL INFO--> |
|{{#vardefine:job|}} <!--JOB SCRIPTS--> | |{{#vardefine:job|}} <!--JOB SCRIPTS--> | ||
|{{#vardefine:policy|}} <!--POLICY--> | |{{#vardefine:policy|}} <!--POLICY--> | ||
| Line 31: | Line 31: | ||
<!--Run--> | <!--Run--> | ||
{{#if: {{#var: exe}}|==Additional Information== | {{#if: {{#var: exe}}|==Additional Information== | ||
| − | + | Caveats of running snakemake with SLURM job submission: | |
| − | + | * If you specify a sub-directory for job log file(s) in the snakemake config make sure to create that sub-directory before submitting the main snakemake job as the scheduled jobs will fail immediately if the job log file's directory does not exist. | |
|}} | |}} | ||
Revision as of 15:20, 5 July 2022
Description
The Snakemake workflow management system is a tool to create reproducible and scalable data analyses. Workflows are described via a human readable, Python based language. They can be seamlessly scaled to server, cluster, grid and cloud environments, without the need to modify the workflow definition. Finally, Snakemake workflows can entail a description of required software, which will be automatically deployed to any execution environment.
Environment Modules
Run module spider Snakemake to find out what environment modules are available for this application.
System Variables
- HPC_SNAKEMAKE_DIR - installation directory
Additional Information
Caveats of running snakemake with SLURM job submission:
- If you specify a sub-directory for job log file(s) in the snakemake config make sure to create that sub-directory before submitting the main snakemake job as the scheduled jobs will fail immediately if the job log file's directory does not exist.