This shows you the differences between two versions of the page.
Both sides previous revision Previous revision | Next revision Both sides next revision | ||
archive:bioinformatic_tools:allpaths [2010/04/07 17:11] jstjohn |
archive:bioinformatic_tools:allpaths [2010/04/08 16:20] jstjohn Better version of the allpaths manual where the text is readable and the filesize is simaller. |
||
---|---|---|---|
Line 1: | Line 1: | ||
===== ALLPATHS ===== | ===== ALLPATHS ===== | ||
- | Attached is the Allpaths3 version 1.0 documentation converted from .docx format to .pdf. You can download this file by clicking the following link: {{:bioinformatic_tools:allpathsv3_manual_r1.0.pdf|allpathsv3_manual_r1.0.pdf}}. | + | Attached is the Allpaths3 version 1.0 documentation converted from .docx format to .pdf. You can download this file by clicking the following link: {{:bioinformatic_tools:allpathsv3_manual_r1.0_2.pdf|allpathsv3_manual}}. |
====Potential Pitfalls==== | ====Potential Pitfalls==== | ||
Designed to work with 100+ bp paired end reads from a *minimum of one short and one long set of libraries. Also the program expects 40X coverage from each of those libraries! Additionally they say it requires a minimum of 32Gb of ram which I assume means shared memory, so it may not work on our cluster. Maybe it would be useful to run on small portions of our data though? | Designed to work with 100+ bp paired end reads from a *minimum of one short and one long set of libraries. Also the program expects 40X coverage from each of those libraries! Additionally they say it requires a minimum of 32Gb of ram which I assume means shared memory, so it may not work on our cluster. Maybe it would be useful to run on small portions of our data though? |