b-brankovics/smkwf-STRAf-typing
Snakemake workflow for STRAf typing Aspergillus fumigatus genome assemblies
Overview
Latest release: None, Last update: 2026-03-13
Share link: https://snakemake.github.io/snakemake-workflow-catalog?wf=b-brankovics/smkwf-STRAf-typing
Quality control: linting: failed formatting: failed
Wrappers: bio/fastqc bio/multiqc
Deployment
Step 1: Install Snakemake and Snakedeploy
Snakemake and Snakedeploy are best installed via the Conda package manager. It is recommended to install conda via Miniforge. Run
conda create -c conda-forge -c bioconda -c nodefaults --name snakemake snakemake snakedeploy
to install both Snakemake and Snakedeploy in an isolated environment. For all following commands ensure that this environment is activated via
conda activate snakemake
For other installation methods, refer to the Snakemake and Snakedeploy documentation.
Step 2: Deploy workflow
With Snakemake and Snakedeploy installed, the workflow can be deployed as follows. First, create an appropriate project working directory on your system and enter it:
mkdir -p path/to/project-workdir
cd path/to/project-workdir
In all following steps, we will assume that you are inside of that directory. Then run
snakedeploy deploy-workflow https://github.com/b-brankovics/smkwf-STRAf-typing . --tag None
Snakedeploy will create two folders, workflow and config. The former contains the deployment of the chosen workflow as a Snakemake module, the latter contains configuration files which will be modified in the next step in order to configure the workflow to your needs.
Step 3: Configure workflow
To configure the workflow, adapt config/config.yml to your needs following the instructions below.
Step 4: Run workflow
The deployment method is controlled using the --software-deployment-method (short --sdm) argument.
To run the workflow using apptainer/singularity, use
snakemake --cores all --sdm apptainer
To run the workflow using a combination of conda and apptainer/singularity for software deployment, use
snakemake --cores all --sdm conda apptainer
To run the workflow with automatic deployment of all required software via conda/mamba, use
snakemake --cores all --sdm conda
Snakemake will automatically detect the main Snakefile in the workflow subfolder and execute the workflow module that has been defined by the deployment in step 2.
For further options such as cluster and cloud execution, see the docs.
Step 5: Generate report
After finalizing your data analysis, you can automatically generate an interactive visual HTML report for inspection of results together with parameters and code inside of the browser using
snakemake --report report.zip
Configuration
The following section is imported from the workflow’s config/README.md.
Workflow overview
This workflow extracts PCR amplicon regions from genomes, and then can process them for STR typing. The workflow is built using snakemake and consists of the following steps:
Need to update
Running the workflow
Input data
This workflow extracts PCR amplicon regions from genomes, and then can process them for STR typing. You need to specify four tables (TSVs) and a yaml file (primers.yaml) as inputs:
accessions.tsv:
sample |
assembly |
|---|---|
Af293 |
GCF_000002655.1 |
A1160 |
GCA_024220425.1 |
W72310 |
GCA_040167795.1 |
ATCC46645 |
GCA_040142955.1 |
local.tsv:
sample |
assembly_file |
|---|---|
sample1 |
data/genomes/sample1_contigs.fasta |
sample2 |
data/genomes/sample2_contigs.fasta |
sample3 |
data/genomes/sample3_contigs.fasta |
STR.tsv:
locus |
flanking_len |
repeat_len |
repeat_seq |
|---|---|---|---|
STRAf-2A |
143 |
2 |
GA |
STRAf-2B |
107 |
2 |
AG |
STRAf-2C |
139 |
2 |
CA |
STRAf-3A |
106 |
3 |
TCT |
STRAf-3B |
134 |
3 |
AAG |
STRAf-3C |
62 |
3 |
TAG |
STRAf-4A |
145 |
4 |
TTCT |
STRAf-4B |
145 |
4 |
CTAT |
STRAf-4C |
141 |
4 |
ATGT |
primers.tsv:
Locus |
Description |
Name |
Sequence |
OligoType |
Reference |
|---|---|---|---|---|---|
STRAf-2A |
Microsatellite locus 2A |
STRAf-2AF |
AAGGGTTATGGCCATTAGGG |
F |
DOI:10.1128/jcm.43.8.4112-4120.2005 |
STRAf-2A |
Microsatellite locus 2A |
STRAf-2AR |
GACCTCCAGGCAAAATGAGA |
R |
DOI:10.1128/jcm.43.8.4112-4120.2005 |
STRAf-2B |
Microsatellite locus 2B |
STRAf-2BF |
TATTGGATCTGCTCCCAAGC |
F |
DOI:10.1128/jcm.43.8.4112-4120.2005 |
STRAf-2B |
Microsatellite locus 2B |
STRAf-2BR |
GAGATCATGCCCAAGGATGT |
R |
DOI:10.1128/jcm.43.8.4112-4120.2005 |
STRAf-2C |
Microsatellite locus 2C |
STRAf-2CF |
TCGGAGTAGTTGCAGGAAGG |
F |
DOI:10.1128/jcm.43.8.4112-4120.2005 |
STRAf-2C |
Microsatellite locus 2C |
STRAf-2CR |
AACGCGTCCTAGAATGTTGC |
R |
DOI:10.1128/jcm.43.8.4112-4120.2005 |
STRAf-3A |
Microsatellite locus 3A |
STRAf-3AF |
GCTTCGTAGAGCGGAATCAC |
F |
DOI:10.1128/jcm.43.8.4112-4120.2005 |
STRAf-3A |
Microsatellite locus 3A |
STRAf-3AR |
GTACCGCTGCAAAGGACAGT |
R |
DOI:10.1128/jcm.43.8.4112-4120.2005 |
STRAf-3B |
Microsatellite locus 3B |
STRAf-3BF |
CAACTTGGTGTCAGCGAAGA |
F |
DOI:10.1128/jcm.43.8.4112-4120.2005 |
STRAf-3B |
Microsatellite locus 3B |
STRAf-3BR |
GAGGTACCACAACACAGCACA |
R |
DOI:10.1128/jcm.43.8.4112-4120.2005 |
STRAf-3C |
Microsatellite locus 3C |
STRAf-3CF |
GGTTACATGGCTTGGAGCAT |
F |
DOI:10.1128/jcm.43.8.4112-4120.2005 |
STRAf-3C |
Microsatellite locus 3C |
STRAf-3CR |
GTACACAAAGGGTGGGATGG |
R |
DOI:10.1128/jcm.43.8.4112-4120.2005 |
STRAf-4A |
Microsatellite locus 4A |
STRAf-4AF |
TTGTTGGCCGCTTTTACTTC |
F |
DOI:10.1128/jcm.43.8.4112-4120.2005 |
STRAf-4A |
Microsatellite locus 4A |
STRAf-4AR |
GACCCAGCGCCTATAAATCA |
R |
DOI:10.1128/jcm.43.8.4112-4120.2005 |
STRAf-4B |
Microsatellite locus 4B |
STRAf-4BF |
CGTAGTGACCTGAGCCTTCA |
F |
DOI:10.1128/jcm.43.8.4112-4120.2005 |
STRAf-4B |
Microsatellite locus 4B |
STRAf-4BR |
GGAAGGCTGTACCGTCAATCT |
R |
DOI:10.1128/jcm.43.8.4112-4120.2005 |
STRAf-4C |
Microsatellite locus 4C |
STRAf-4CF |
CATATTGGGAAACCCACTCG |
F |
DOI:10.1128/jcm.43.8.4112-4120.2005 |
STRAf-4C |
Microsatellite locus 4C |
STRAf-4CR |
ACCAACCCATCCAATTCGTAA |
R |
DOI:10.1128/jcm.43.8.4112-4120.2005 |
Parameters
This table lists all parameters that can be used to run the workflow.
parameter |
type |
details |
default |
|---|---|---|---|
accessions |
path |
path to sample sheet of accessions, mandatory |
“config/accessions.tsv” |
local_samples |
path |
path to sample sheet of local assemblies, mandatory |
“config/local.tsv” |
Workflow parameters
The following table is automatically parsed from the workflow’s config.schema.y(a)ml file.
Parameter |
Type |
Description |
Required |
Default |
|---|---|---|---|---|
accessions |
string |
path to sample-sheet for accessions TSV file |
yes |
|
local_samples |
string |
path to sample-sheet for local assemblies TSV file |
yes |
Linting and formatting
Linting results
1Using workflow specific profile profiles/default for setting default command line arguments.
2Cloning github.com/b-brankovics/smkwf-oligo-screening to /home/runner/.cache/snakemake/snakemake/source-cache/snakemake-git-cache/github.com/b-brankovics/smkwf-oligo-screening
3KeyError in file "/tmp/tmpoa9qbq57/workflow/Snakefile", line 32:
4'https://:raw.githubusercontent.com/b-brankovics/smkwf-oligo-screening/setup/workflow/Snakefile'
5 File "https://:raw.githubusercontent.com/b-brankovics/smkwf-oligo-screening/setup/workflow/Snakefile", line 30, in <module>
Formatting results
1[DEBUG]
2[DEBUG]
3[DEBUG] In file "/tmp/tmpoa9qbq57/workflow/Snakefile": Formatted content is different from original
4[DEBUG]
5[DEBUG] In file "/tmp/tmpoa9qbq57/workflow/rules/common.smk": Formatted content is different from original
6[INFO] 2 file(s) would be changed 😬
7[INFO] 1 file(s) would be left unchanged 🎉
8
9snakefmt version: 0.11.4