genomic_interval_pipeline

Crates.iogenomic_interval_pipeline
lib.rsgenomic_interval_pipeline
version0.1.3
sourcesrc
created_at2020-11-28 22:19:31.982191
updated_at2020-12-03 23:29:51.024263
descriptionA pipeline for creating HDF5 databases from genomic intervals.
homepagehttps://github.com/Chris1221/genomic_interval_pipeline
repositoryhttps://github.com/Chris1221/genomic_interval_pipeline
max_upload_size
id317588
size60,087
Christopher Cole (Chris1221)

documentation

README

A Pipeline for Building Genomic Annotation Datasets for Deep Learning

Crates.io Crates.io Docs

This is a pipeline for creating HDF5 input to Keras from genomic regions and annotations in Rust. It is a (somewhat) drop-in replacement for Basset's preprocessing pipeline, intended to transform a list of BED files into annotated one-hot encoded sequences for use in a deep learning model. The input and output of both pipelines should be similar, with this one being substantially faster for larger datasets.

To install, use cargo or alternatively build from source.

cargo install genomic_interval_pipeline

Building from source

Ensure that you have installed cargo and Rust on your system, then clone this repository.

git clone git@github.com:Chris1221/genomic_interval_pipeline.rs.git
cd genomic_interval_pipeline.rs

Use cargo to build the executable. It should figure out all the dependencies for you.

cargo build --release

The binary will be in target/release/genomic_interval_pipeline.

Usage

You must provide:

  1. A newline seperated list of gzipped BED files.
  2. Path to the reference genome. This must be compressed with bgzip and indexed by samtools faidx.

An example of the first can be found in data/metadata.txt:

data/file1.bed.gz
data/file2.bed.gz

To create the relevant reference genome is straightforward.

  1. Download your reference genome of choice, for example hg19. Here, I just used the UCSC genome browser.
wget https://hgdownload.soe.ucsc.edu/goldenPath/hg19/bigZips/hg19.fa.gz
  1. Compress your reference genome with bgzip (if this is already true, skip this step.)
gunzip hg19.fa.gz
bgzip hg19.fa
  1. Index with samtools.
samtools faidx hg19.fa.gz

Running the pipeline

Invoke the binary with the paths to the metadata of BED files and the reference genome (you don't have to specify where the index is).

genomic_interval_pipeline -i data/metadata.txt -f hg19.fa.gz -o small_dataset

This will create your dataset at small_dataset.h5.

Arguments

Short Long Value Description
-i --input String Path to a newline seperated list of bed files to process.
-f --fastq String Path to faidx indexed, bgzip compressed reference FASTQ file
-o --output String Path to the output .h5 file.
-m --min_overlap Number Minimum overlap required to merge segments (default: 200)
-e --exclusive Bool Perform multiclass learning rather than multilabel (i.e. exclude cases where multiple cell types are annotated, only writing unique values) (defaul: false)
--length Number Standardised length of regions (default: 600)
--test_chr String Comma seperated list of chromosomes to use in the test set (default: chr19,chr20)
--valid_chr String Comma seperated list of chromosomes to use in the validation set (default: chr21,chr22)
--loglevel String Level of logging (default: info)

Dataset Format

HDF5 files are essentially directories of data. There are six tables within the dataset corresponding to the training, test, and validation sequences and their labels.

Sequences are 3D arrays with dimenions (batch, length, 4) where length is optionally specified when building th dataset and refers to the standardized length of the segments.

Labels are 2D arrays with dimensions (batch, number_of_labels) where number of labels is the length of the metadata file. You can easily recode this dataset inside the HDF5 file for more bespoke training outputs.

Nonstandard Labels

Labels are given to bed file sequentially (as a SERIAL ID would be given in a SQL table), however this behaviour can be overriden. Instead of one column metadata file, you may have a two column metadata file seperated by spaces. The second column is the numeric label of this file.

path/to/file1.bed.gz numeric_label_1
path/to/file2/bed.gz numeric_label_2

See the example in data/metadata_custom.txt.

Using the dataset in Keras

You can use this data in your own neural network with the TensorFlow I/O API. Here is an example in Python.

import tensorflow     as tf
import tensorflow_io  as tfio

dataset = "small_dataset.h5"

train_x = tfio.Dataset.from_hdf5(dataset, "training_sequences")
train_y = tfio.Dataset.from_hdf5(dataset, "training_labels")
train_dataset = tf.data.Dataset.zip((train_x, train_y))

Pass this train_dataset (and similarly test and validation) to model.fit.

Commit count: 33

cargo fmt