Project

General

Profile

Actions

Story #3015

closed

Make gatk3 pipeline template

Added by Tom Clegg over 10 years ago. Updated over 10 years ago.

Status:
Resolved
Priority:
Normal
Assigned To:
Category:
-
Target version:
Start date:
06/24/2014
Due date:
% Done:

80%

Estimated time:
(Total: 0.00 h)
Story points:
3.0

Description

  • Create a project
  • Download and add the appropriate reference & example datasets to the project
  • Make a docker image with all of the relevant redistributable software pre-installed
  • Make a "pirs" crunch script and use it to generate the simulation dataset based on hg19 chr1
  • Make a "Single sample SNV with bwa and gatk" pipeline with no parallel/asynchronous tasks
  • Time permitting, make another pipeline that splits the inputs as described below in order to get faster turnaround time when multiple nodes are available.
The attached script and the existing GATK exome pipeline should be helpful. Notes:
  • Use FUSE mount for inputs
  • GATK3 (like attached) not GATK2 (like existing pipeline)
  • Use a docker image with redistributable tools pre-installed, assuming this makes things easier (but not GATK itself - continue to pass this tarball as a job input)
  • Use the file-select script to get appropriate bits from the GATK bundle (which we should have an entire copy of in our project), rather than downloading individual files needed.
  • Existing pipeline provides clues (not necessarily all correct with latest tool versions) about which tools are capable of reading/writing pipes rather than regular files.

Notes about parallelizing:

We can split the FASTQ into many chunks as we want, however after the mapping, we should merge the alignments from one sample into single SAM/BAM file to stack the reads on each genome position. Then we split the SAM/BAM file again by chromosome. So roughly speaking we can get 24 or 25 BAM fragments then all downstream steps could be applied on these chromosome based BAM fragments. At last, probably after annotation, we merge fragment files into one final file. To increase parallelism we can even split the BAM on positions where have very low/no coverage.


Files

Single_Sample_SNV_Pipeline.txt (6.82 KB) Single_Sample_SNV_Pipeline.txt Tom Clegg, 06/18/2014 01:04 AM

Subtasks 5 (0 open5 closed)

Task #3068: Write pipeline templateResolvedPeter Amstutz06/24/2014

Actions
Task #3107: Run on AWS instance (4xphq/qr1hi)ResolvedPeter Amstutz06/24/2014

Actions
Task #3066: Build docker imageResolvedPeter Amstutz06/24/2014

Actions
Task #3069: Run on test dataResolvedPeter Amstutz06/26/2014

Actions
Task #3067: Write scripts for each stageResolvedPeter Amstutz06/24/2014

Actions

Related issues 1 (0 open1 closed)

Related to Arvados - Bug #3373: [Sample pipelines] Improve SNV pipeline to accept example exome fastq data (2 pairs of reads) as a single input collection.ResolvedPeter Amstutz07/30/2014

Actions
Actions #1

Updated by Tom Clegg over 10 years ago

  • Target version set to 2014-07-16 Sprint
Actions #3

Updated by Tom Clegg over 10 years ago

  • Description updated (diff)
Actions #4

Updated by Peter Amstutz over 10 years ago

  • Assigned To set to Peter Amstutz
Actions #5

Updated by Peter Amstutz over 10 years ago

Ongoing notes:

  • Can't upload with arv-put to 4xphq. Got "entity too large" error from nginx.
  • if I upload something with arv-put it doesn't go into any folders by default, and there's no link to the collections table any more
Actions #6

Updated by Peter Amstutz over 10 years ago

  • No modal chooser for individual files. Workaround: select the files in a different window using the paperclip, then they show up in selection dropdown.
  • Pipelines created from pipeline templates don't get added to the same folder.
  • Job parameters passed to docker need to be JSON encoded
  • An "arv migrate" command for copying objects and collections between arvados instances seems like it would be a good idea.
  • if you try to queue a job while another one is running and it's running locally (not using slurm), it tries to run it immediately and then fails because the job directory is locked
Actions #7

Updated by Tom Clegg over 10 years ago

  • Status changed from New to In Progress
Actions #8

Updated by Peter Amstutz over 10 years ago

  • Status changed from In Progress to Resolved
Actions

Also available in: Atom PDF