jianhong/pairedtag

A snakemake workflow for single-cell multiomic data analysis pipeline

Overview

Latest release: None, Last update: 2023-07-19

Share link: https://snakemake.github.io/snakemake-workflow-catalog?wf=jianhong/pairedtag

Quality control: linting: failed formatting: failed

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/jianhong/pairedtag . --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 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.

General configuration

To configure this workflow, modify config/config.yaml according to your needs, following the explanations provided in the file.

Sample and unit setup

The sample and unit setup is specified via tab-separated tabular files (.tsv). Missing values can be specified by empty columns or by writing NA.

sample sheet

The default sample sheet is config/samples.tsv (as configured in config/config.yaml). Each sample refers to an actual physical sample, and replicates (both biological and technical) may be specified as separate samples. For each sample, you will always have to specify a sample_name.

unit sheet

The default unit sheet is config/units.tsv (as configured in config/config.yaml). For each sample, add one or more sequencing units (for example if you have several runs or lanes per sample).

.fastq file source

For each unit, you will have to define a source for your .fastq files. This can be done via the columns fq1, fq2, with two .fastq files for paired-end reads.

adapter trimming

TODO

Linting and formatting

Linting results

 1Workflow defines that rule get_genome is eligible for caching between workflows (use the --cache argument to enable this).
 2Workflow defines that rule get_annotation is eligible for caching between workflows (use the --cache argument to enable this).
 3Workflow defines that rule genome_faidx is eligible for caching between workflows (use the --cache argument to enable this).
 4Workflow defines that rule bwa_index is eligible for caching between workflows (use the --cache argument to enable this).
 5Workflow defines that rule cellranger_index is eligible for caching between workflows (use the --cache argument to enable this).
 6Lints for snakefile /tmp/tmp8w84n72k/workflow/rules/common.smk:
 7    * Path composition with '+' in line 9:
 8      This becomes quickly unreadable. Usually, it is better to endure some
 9      redundancy against having a more readable workflow. Hence, just repeat
10      common prefixes. If path composition is unavoidable, use pathlib or
11      (python >= 3.6) string formatting with f"...".
12      Also see:
13
14
15Lints for snakefile /tmp/tmp8w84n72k/workflow/rules/ref.smk:
16    * Path composition with '+' in line 3:
17      This becomes quickly unreadable. Usually, it is better to endure some
18      redundancy against having a more readable workflow. Hence, just repeat
19      common prefixes. If path composition is unavoidable, use pathlib or
20      (python >= 3.6) string formatting with f"...".
21      Also see:
22
23    * Deprecated singularity directive used for container definition in line 70.:
24      Use the container directive instead (it is agnostic of the underlying
25      container runtime).
26      Also see:
27      https://snakemake.readthedocs.io/en/latest/snakefiles/deployment.html#running-jobs-in-containers
28
29Lints for snakefile /tmp/tmp8w84n72k/workflow/rules/qc.smk:
30    * Path composition with '+' in line 5:
31      This becomes quickly unreadable. Usually, it is better to endure some
32      redundancy against having a more readable workflow. Hence, just repeat
33      common prefixes. If path composition is unavoidable, use pathlib or
34      (python >= 3.6) string formatting with f"...".
35      Also see:
36
37
38Lints for rule remap_barcode (line 3, /tmp/tmp8w84n72k/workflow/rules/remap_barcode.smk):
39    * Shell command directly uses variable config from outside of the rule:
40      It is recommended to pass all files as input and output, and non-file
41      parameters via the params directive. Otherwise, provenance tracking is
42      less accurate.
43      Also see:
44      https://snakemake.readthedocs.io/en/stable/snakefiles/rules.html#non-file-parameters-for-rules
45    * Shell command directly uses variable config from outside of the rule:
46      It is recommended to pass all files as input and output, and non-file
47      parameters via the params directive. Otherwise, provenance tracking is
48      less accurate.
49      Also see:
50      https://snakemake.readthedocs.io/en/stable/snakefiles/rules.html#non-file-parameters-for-rules
51    * Shell command directly uses variable config from outside of the rule:
52      It is recommended to pass all files as input and output, and non-file
53      parameters via the params directive. Otherwise, provenance tracking is
54      less accurate.
55      Also see:
56      https://snakemake.readthedocs.io/en/stable/snakefiles/rules.html#non-file-parameters-for-rules
57    * Shell command directly uses variable config from outside of the rule:
58      It is recommended to pass all files as input and output, and non-file
59      parameters via the params directive. Otherwise, provenance tracking is
60      less accurate.
61      Also see:
62      https://snakemake.readthedocs.io/en/stable/snakefiles/rules.html#non-file-parameters-for-rules

Formatting results

 1[DEBUG] 
 2[DEBUG] In file "/tmp/tmp8w84n72k/workflow/rules/remap_barcode.smk":  Formatted content is different from original
 3[DEBUG] 
 4[DEBUG] In file "/tmp/tmp8w84n72k/workflow/rules/cellranger.smk":  Formatted content is different from original
 5[DEBUG] 
 6[DEBUG] In file "/tmp/tmp8w84n72k/workflow/rules/common.smk":  Formatted content is different from original
 7[DEBUG] 
 8[DEBUG] In file "/tmp/tmp8w84n72k/workflow/rules/qc.smk":  Formatted content is different from original
 9[DEBUG] 
10[DEBUG] In file "/tmp/tmp8w84n72k/workflow/rules/ref.smk":  Formatted content is different from original
11[DEBUG] 
12[DEBUG] In file "/tmp/tmp8w84n72k/workflow/Snakefile":  Formatted content is different from original
13[INFO] 6 file(s) would be changed 😬
14
15snakefmt version: 0.8.4