Skip to content
/ dREG Public
forked from Danko-Lab/dREG

Detecting Regulatory Elements using GRO-seq and PRO-seq

Notifications You must be signed in to change notification settings

tinyi/dREG

 
 

Repository files navigation

dREG

Detection of Regulatory DNA Sequences using GRO-seq Data.

Abstract

Identification of the genomic regions that regulate transcription remains an important open problem. We have recently shown that global run-on and sequencing (GRO-seq) with enrichment for 5-prime-capped RNAs reveals patterns of divergent transcription that accurately mark active transcriptional regulatory elements (TREs), including enhancers and promoters. Here, we demonstrate that active TREs can be identified with comparable accuracy by applying sensitive machine-learning methods to standard GRO-seq and PRO-seq data, allowing TREs to be assayed together with transcription levels, elongation rates, and other transcriptional features, in a single experiment. Our method, called discriminative Regulatory Element detection from GRO-seq (dREG), summarizes GRO-seq read counts at multiple scales and uses support vector regression to predict active TREs. The predicted TREs are strongly enriched for marks associated with functional elements, including H3K27ac, transcription factor binding sites, eQTLs, and GWAS-associated SNPs. Using dREG, we survey TREs in eight cell types and provide new insights into global patterns of TRE assembly and function.

Installation instructions:

dREG will ultimately be availiable in the R repository CRAN to ease installation, and source code will be availiable on GitHub (https://github.com/Danko-Lab/dREG).

Supported OS:

Linux and Mac OSX are currently supported.

Required software

This software is already installed on many UNIX systems. Users can install the most appropriate version of these files for Ubuntu using:

sudo apt-get r-base-core
sudo apt-get install libmysqlclient-dev
sudo apt-get install libssl1.0.0 libssl-dev

Users who are not sure how to install the proper dependencies on their system should check with their system administrator for help.

dREG also has several dependencies within R. These include rphast, grid, boot, e1071, and parallel. These packages are all availiable on the CRAN repository. For convenience, users can install these packages using the makefile:

make R_dependencies

If users run into any problems they should contact the package author for assistance.

Install dREG

Users should change to the directory containing this README.md file, and can then install dREG by typing the following:

(1a) Install R dependencies

make R_dependencies

(1b) Install dREG

make dreg

Usage instructions:

dREG takes three files as input, and outputs one file. Input files include the PRO-seq read distributions on the plus and minus strand (which are separate files), and parameters of the pre-trained support vector regression (SVR) model.

  • PRO-seq files are required to be in the bigWig format standard created by the UCSC (more information can be found here: http://genome.ucsc.edu/goldenPath/help/bigWig.html).
  • The SVR model is included in this package (under dREG_model/asvm.RData). Users are advised to use that when possible.

To use dREG, type:

bash dREG.bsh plus_strand.bw minus_strand.bw out_prefix asvm.RData [nthreads]

plus_strand.bw	-- PRO-seq data (plus strand) formatted as a bigWig file.
minus_strand.bw	-- PRO-seq data (plus strand) formatted as a bigWig file.
out_prefix		-- The prefix of the output file.
asvm.RData		-- The path to the RData file containing the pre-trained SVM.
[nthreads]		-- [optional, default=1] The number of threads to use.

For example, to run dREG on the example data (PRO-seq from chr21 in K562 cells), use:

bash run_dREG.bsh example/K562.chr21.plus.bw example/K562.chr21.minus.bw k562.test dREG_model/asvm.RData 2

That command takes ~2-3 hours to execute on Ubuntu on a core i5 desktop computer.

dREG outputs a bedGraph file of scores. If desired, users can convert this file into a merged file of dREG 'peaks', or regions which fit the profile of a transcribed regulatory element. For convenience, users can use the included bash script (writeBed.bsh) to identify dREG peaks. This script is used as follows:

bash writeBed.bsh 0.8 out_prefix.bedGraph.gz

Here 0.8 denotes the threshold to call a regulatory element, and the out_prefix.bedGraph.gz is the output of the dREG run. Note that this feature requires the bedOps package (https://bedops.readthedocs.org/en/latest/).

dREG is an R package, and that provides some additional flexibility for users familiar with R. We are actively working to document each function in the package.

About

Detecting Regulatory Elements using GRO-seq and PRO-seq

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published

Languages

  • R 64.2%
  • Shell 28.0%
  • C 5.3%
  • Perl 1.1%
  • Other 1.4%