epigen/spilterlize_integrate
A Snakemake workflow and MrBiomics module to split, filter, normalize, integrate and select highly variable features of count matrices resulting from next-generation sequencing (NGS) experiments (e.g., RNA-seq, ATAC-seq, ChIP-seq, Methyl-seq, miRNA-seq,…) including confounding factor analysis and diagnostic visualizations.
Overview
Topics: atac-seq batch-effect chip-seq count-matrix dimensionality-reduction integration ngs normalization rna-seq bioinformatics biomedical-data-science pipeline snakemake visualization workflow confounding-effects
Latest release: v3.0.0, Last update: 2025-03-04
Linting: linting: failed, Formatting:formatting: failed
Deployment
Step 1: Install Snakemake and Snakedeploy
Snakemake and Snakedeploy are best installed via the Mamba package manager (a drop-in replacement for conda). If you have neither Conda nor Mamba, it is recommended to install Miniforge. More details regarding Mamba can be found here.
When using Mamba, run
mamba create -c conda-forge -c bioconda --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
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/epigen/spilterlize_integrate . --tag v3.0.0
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
.
You only need one configuration file to run the complete workflow. You can use the provided example as starting point. If in doubt read the comments in the config, the documentation of the respective methods and/or try the default values.
configuration (config/config.yaml): Different for every project/dataset and configures the analyses to be performed, specifically the desired methods and their parameters. The fields are described within the file.
Set workflow-specific resources
or command line arguments (CLI) in the workflow profile workflow/profiles/default.config.yaml
, which supersedes global Snakemake profiles.
Linting and formatting
Linting results
Using workflow specific profile workflow/profiles/default for setting default command line arguments.
FileNotFoundError in file /tmp/tmpsgmxoeyh/epigen-spilterlize_integrate-10da520/workflow/Snakefile, line 28:
[Errno 2] No such file or directory: '/path/to/metadata.csv'
File "/tmp/tmpsgmxoeyh/epigen-spilterlize_integrate-10da520/workflow/Snakefile", line 28, in <module>
File "/home/runner/micromamba/envs/snakemake-workflow-catalog/lib/python3.12/site-packages/pandas/io/parsers/readers.py", line 1026, in read_csv
File "/home/runner/micromamba/envs/snakemake-workflow-catalog/lib/python3.12/site-packages/pandas/io/parsers/readers.py", line 620, in _read
File "/home/runner/micromamba/envs/snakemake-workflow-catalog/lib/python3.12/site-packages/pandas/io/parsers/readers.py", line 1620, in __init__
File "/home/runner/micromamba/envs/snakemake-workflow-catalog/lib/python3.12/site-packages/pandas/io/parsers/readers.py", line 1880, in _make_engine
File "/home/runner/micromamba/envs/snakemake-workflow-catalog/lib/python3.12/site-packages/pandas/io/common.py", line 873, in get_handle
Formatting results
[DEBUG]
[DEBUG] In file "/tmp/tmpsgmxoeyh/epigen-spilterlize_integrate-10da520/workflow/rules/visualize.smk": Formatted content is different from original
[DEBUG]
[DEBUG] In file "/tmp/tmpsgmxoeyh/epigen-spilterlize_integrate-10da520/workflow/rules/normalize.smk": Formatted content is different from original
[DEBUG]
[DEBUG] In file "/tmp/tmpsgmxoeyh/epigen-spilterlize_integrate-10da520/workflow/rules/envs_export.smk": Formatted content is different from original
[DEBUG]
[DEBUG] In file "/tmp/tmpsgmxoeyh/epigen-spilterlize_integrate-10da520/workflow/rules/process.smk": Formatted content is different from original
[DEBUG]
[DEBUG] In file "/tmp/tmpsgmxoeyh/epigen-spilterlize_integrate-10da520/workflow/rules/integrate.smk": Formatted content is different from original
[DEBUG]
[DEBUG] In file "/tmp/tmpsgmxoeyh/epigen-spilterlize_integrate-10da520/workflow/Snakefile": Formatted content is different from original
[INFO] 6 file(s) would be changed 😬
snakefmt version: 0.10.2