Skip to content
/ smrtmake Public

Hackable smrtpipe workflows using makefiles instead of smrtpipe.py

Notifications You must be signed in to change notification settings

pbjd/smrtmake

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

13 Commits
 
 
 
 

Repository files navigation

smrtmake

Hackable smrtpipe workflows using makefiles instead of smrtpipe.py. Mostly self contained, they offer benefits over smrpipe in several respects:

  1. Restartable. If something fails in the middle, you can (in many cases) restart where you left off.
  2. No XML. The configuration and workflow is all contained in the Makefile.
  3. Piecemeal execution. Only execute the parts of the workflow you care about.
  4. More freedom to organize outputs.
  5. Customizable to your needs. Take out stuff you don't want or add stuff that you do want. Just write adapters to manage the interfacing.

Some downsides.

  1. Make syntax is not exactly user friendly and you need to understand how command line works.
  2. Command line only, no integration with SMRT Portal.
  3. Limited support.

NOTE: These have only been tested on SGE clusters. You can probably find ways to run on other cluster setups with a little modification.

Running

You'll need a smrtanalysis installation and SGE cluster manager in order to run the Makefile workflows, although it would be trivial to modify them to run on a single compute node.

All you need is two files: Makefile and input.fofn.

> ls
Makefile input.fofn
> make

That's it!

It can also be parallelized using the '-j' option to make

> make -j 8

NOTE: There are some assumptions builtin to this workflow that may not hold in your environment, e.g., metadata.xml file locations. While fixable, it's not always obvious what you need to do. Send me an email and I can try to help you get unstuck.

hgap3.mk

HGAP.3 workflow tuned for larger genomes. It doesn't generate reports (though they may be added in the future) and the output is organized much differently, but better IMHO, than smrtpipe.

This was built and run using PacBio's internal cluster, which uses SGE. The nodes were fairly sizeable with 48 CPU, 200GB RAM. Consider modifying the Makefile to suite your needs:

> head hgap3.mk
# SGE queue name to submit jobs to
QUEUE ?= huasm
# Estimated size of the genome to assemble
GENOME_SIZE ?= 700000000
# Splits data into this many chunks, each chunk processed independently
CHUNK_SIZE ?= 15
# How many threads a process will use (also how many SGE slots will be requested)
NPROC ?= 32
# Local temp root directory, must have write access and a decent amount of space (~100GB)
LOCALTMP ?= /scratch

The default recipe will run the HGAP.3 workflow to completion, i.e.:

> make -j 15

However, you may only want to run it to a certain step. You can also continue where you left off.

# runs the workflow to get corrected reads
> make -j 15 correction

# runs (or continues) the workflow to get a draft assembly
> make draft

Dry-run is also supported, when you want to double check what will be run.

# displays the list of commands that will be run in order
> make -n

About

Hackable smrtpipe workflows using makefiles instead of smrtpipe.py

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published