Basically, the pipeline goes like this:
ABYSS - the single-end assembler
AdjList - finds overlaps of length k-1 between contigs
PopBubbles - collapses variation
----o-----
KAligner - aligns reads to contigs
ParseAligns - finds pairs of reads in alignments
DistanceEst - estimates distances between contigs
Overlap - find overlaps between blunt contigs
SimpleGraph - finds paths between pairs of contigs
MergePaths - merges consistent paths
MergeContigs
If you have unpaired reads, then ABYSS will be run creating contigs. If
you have paired reads, abyss-pe is a makefile that first, will assemble
as your reads as unpaired with ABYSS and then, mapped them back to the
contigs continuing the pipeline from KAligner to the creation of the
consensus.
There is a README in the abyss directory that is pretty clear on how to
run it.
Cheers.
--
The Wellcome Trust Sanger Institute is operated by Genome Research
Limited, a charity registered in England with number 1021457 and a
company registered in England with number 2742969, whose registered
office is 215 Euston Road, London, NW1 2BE.
You can use the driver script abyss-pe to run the component programs of
ABySS. The option -n,--dry-run of abyss-pe is useful to display the
commands that abyss-pe would run without actually running them.
In actual fact, abyss-pe is a Makefile script and -n,--dry-run is an
option of make.
Cheers,
Shaun