Skip to content

1. Installation

Jump to bottom
Breon Schmidt edited this page May 31, 2017 · 22 revisions

Auto Installation

It's coming, I promise... but it's not too hard to follow the below!

Manual Installation

I recommend creating a separate environment from which you can exclusively control dependencies for Clinker. My preferred method is to use the Anaconda platform, but feel free to use any other method (or none at all) and just skip to step 2.

Create Clinker Environment With Anaconda

Install Anaconda

Follow the install instructions at continuum, but pretty much just:

  1. Download Anaconda (you can use wget)
  2. Navigate to downloaded file
  3. bash Anaconda-latest-Linux-x86_64.sh
  4. conda update conda

Activate bioconda

Enter the below in order (!important)

  1. conda config --add channels conda-forge
  2. conda config --add channels defaults
  3. conda config --add channels r
  4. conda config --add channels bioconda

Create Clinker Environment

Now with Anaconda installed, we can simply just create a new environment with Python 2.7 (I know) enabled.

  1. conda create --name clinker python=2.7 anaconda

You can always remove this by simply entering

conda remove --name clinker --all

Activate Clinker Environment

  1. source activate clinker

All done! Let's start installing the dependencies.

Install Dependencies

Install R, Samtools, STAR

  1. conda install -c r r-essentials
  2. conda install samtools
  3. conda install -c bioconda star=2.5.3a

Install Gviz

Start R and then enter

  1. source("https://bioconductor.org/biocLite.R")
  2. biocLite("Gviz")

Close R, that's it for dependencies.

Clone latest Clinker

Now we're ready to download the Clinker source!

  1. Create a new folder for your Clinker program to reside, navigate there.
  2. git clone https://github.com/Oshlack/Clinker.git

You're all done! Ready to work through some examples?

Run Clinker on a bigger scale

Have many researchers who want to use Clinker, but only want to use a single installation? Try the following.

  1. Create a new folder, globally accessible by those who you wish to use Clinker.
  2. Navigate to this folder and clone a copy of Clinker
    • git clone https://github.com/Oshlack/Clinker.git
  3. Most institutions have a method of managing software on their servers (e.g. Modules), whatever method you choose, ensure that all the Clinker dependencies are loaded and the workflow folder is added to the users path as a variable like $CLINKERPATH.
  4. Whenever somebody wants to run clinker, they can do so with the usual snippet, but with the following bolded change:

bpipe -p out="/path/to/clinker/output" -p caller="/path/to/jaffa_results.csv" -p col="3,4,5,6" -p del="c" -p genome="19" -p print="true" -p fusions="BCR:ABL1" -p pdf_width="9" -p pdf_height="16" -p sizing="1,3,1,2,4,2" -p competitive="false" $CLINKERPATH/clinker.pipe /path/to/*.fastq.gz

NOTE: There are many ways to manage a server, this may not be the best method for you. Let us know if you come across another solution and we will add it to the wiki.

Clone this wiki locally