_
___ _ __ __ _| | _____ ___
/ __| '_ \ / _` | |/ / _ \/ __|
\__ \ | | | (_| | < __/\__ \
|___/_| |_|\__,_|_|\_\___||___/ v0.1 alpha
Data integration and machine learning pipelines built on Snakemake
- Development status
- Overview
- Why Snakes
- Scope
- How Snakes works
- Example configuration
- Installation
- Planned functionality
- Feedback / suggestions
Snakes is currently undergoing active development and is likely to change significantly in the coming weeks. A more complete version of the targeted functionality is planned for Fall/Winter 2019. In the meantime, if you are interested in contributing to the effort, feel free to reach out!
Snakes is a command-line tool, written in Python/R, which aims to provide a simple approach to constructing pipelines for data integration and machine learning. Rather than re-implementing a data pipeline framework from the ground up (for which there exist many really good ones such as Snakemake, Nextflow, Ruffus, and Luigi), Snakes instead seeks to provide an easy means to generate a pipeline using such a framework (specifically, Snakemake), as well as providing some useful out-of-the-box functionality for assisting with data integration, visualization, quality assurance, and machine learning.
As mentioned above, there are already a number of great frameworks for constructing data pipelines. Why Snakes?
While each of the aforementioned frameworks provide a powerful set of tools for building modern data science pipelines, they all generally share some limitations, which Snakes seeks to overcome.
The main features of Snakes include:
- Simple configuration using YAML files.
- Out-of-the-box support for common data transformation, visualization, machine learning, etc. operations.
- A modular design, making it easy to extend Snakes to support new operations.
- Support for branching and integration / cross-data comparisons
Most pipeline frameworks, while extremely powerful and versatile, have a fair bit of a learning curve. Moreover, since they are focused on the nuts-and-bolts of designing data workflows, they do not include any built-in support for basic data science operations, and require a fair bit of coding knowledge to successfully utilize.
The goal of Snakes is to provide a set of useful building blocks for data science pipelines, and a simple means to stitch them together in order to construct a data science pipeline.
Existing / planned functionality for snakes can be dividing into the following major categories:
- Data filtering and transformations
- Visualization and summarization
- Integration and cross-dataset analysis
- Incorporation of domain-specific knowledge
- Feature selection and machine learning
The aim is this effort to produce software that is not tied to any specific research field, and is useful across a wide range of problems. My background, however, is largely in bioinformatics and, as such, the sorts of functionality that will be prioritized for inclusion will be guided by the kinds of problems that I'm currently working on - in particular, integrative modeling for precision medicine.
That said, the modular design of Snakes is aimed at making it straight-forward to add new functionality, so users are welcome to submit pull requests with additional functionality, both general, and domain-specific.
You can expect the functionality of Snakes to expand significantly in the coming months as code is migrated from a prototype workflow into the new codebase.
Snakes uses the Jinja2 templating framework in order to dynamically construct a static Snakefile from one or more YAML configuration files, which can then be executed by Snakemake.
Below is a partial example set of config files for a hypothetical multi-omics bioinformatics pipeline aimed at building models for predicting biomarkers associated with drug sensitivity.
The complete configuration can be found in the example/ directory of the repository.
Note that, as mentioned above, Snakes is currently under active development and is not considered fully-functional at this time. The functionality described above has been implemented in a separate prototype, but still needs to be incorporated into the codebase proper.
In order to increase the re-usability of Snakes-based pipelines, config files may be split up into several files including one main config (typically, "config.yml"), along with one or more additional dataset-specific config files.
Below, an example main config file is shown, along with a sub-config file for processing a
transcriptomics (RNA-Seq) dataset. The config files for
the remaining datasets can be found in the example/yml
directory.
config.yml
################################################################################
# _
# ___ _ __ __ _| | _____ ___
# / __| '_ \ / _` | |/ / _ \/ __|
# \__ \ | | | (_| | < __/\__ \
# |___/_| |_|\__,_|_|\_\___||___/
#
# Example configuration
#
################################################################################
################################################################################
#
# General settings
#
################################################################################
# analysis name and version
name: 'test pipeline'
version: '1.0'
# output directory
output_dir: 'output'
# random seed
random_seed: 1
# output verbosity
verbose: true
################################################################################
#
# Datasets
#
################################################################################
datasets:
- 'example/yml/rnaseq.yml'
- 'example/yml/cnv.yml'
- 'example/yml/variants.yml'
- 'example/yml/drug_screen.yml'
rnaseq.yml
################################################################################
#
# RNA-Seq Example Configuration
#
################################################################################
# General
name: rnaseq
xid: ensembl_gene_id
yid: sample_id
#
# Path to RNA-Seq count data
#
path: 'example/data/features/rnaseq.csv'
#
# RNA-Seq data processing steps
#
actions:
- filter_cols_name_not_in:
names: ['KMS20_JCRB']
- filter_rows_var_gt:
name: 'exclude_zero_variance'
value: 0
- filter_rows_sum_gt:
name: 'filter_min_reads'
value: 20
- filter_rows_gene_biotype_in:
name: 'filter_by_gene_type'
gene_biotypes: ['protein_coding']
- transform_cpm
- transform_log2p
- transform_zscore:
name: 'transform_row_zscores'
axis: 1
- branch:
- cluster_hclust:
num_clusters: 4
Dependencies
Optional dependencies
Depending on the types of actions you wish to perform, the below dependencies are also recommended:
Installation using conda
The recommended method for installing Snakes is to use conda environments:
To begin, clone the snakes repo and cd
into the directory:
git clone https://github.com/khughitt/snakes
cd snakes
Next, use the conda env
command to create a new conda environment, specifying the list of
dependencies that should be installed:
conda create -n snakes \
--file requirements.txt \
--channel defaults \
--channel conda-forge \
--channel bioconda
Finally, activate the new environment and install snakes in development mode using:
conda activate snakes
pip install -e .
To test out the new installation, you can try building the example workflow included with snakes, using the command:
snakes -c example/settings/config.yml
This should result in a Snakefile
being generated in your current directory. This can be executed
by simply calling snakemake:
snakemake
Most of the below have already been implemented prototype R version of software. Expect them to be added in the coming months, with a target "release date" for the major functionality of Fall/Winter 2019.
- Dimension reduction methods (PCA, NMF, t-SNE, UMAP)
- Visualization
- Additional normalization methods
- Additional clustering methods
- Pivoting transformations
- Summarization / RMarkdown report generation
- Outlier detection
- Batch adjustment
- Pathway- and gene set-based feature aggregation
- Feature selection
- Cross-data correlation
- Model training and cross-validation
- Singularity container support
- Support for working with additional / raw data formats
- Documentation
Feedback and suggestions are always welcome. Feel free to reach out if you have ideas for the project, or would like to become involved.