archive:bioinformatic_tools:euler
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
archive:bioinformatic_tools:euler [2010/04/21 04:53] jstjohn |
archive:bioinformatic_tools:euler [2015/07/28 06:23] (current) ceisenhart ↷ Page moved from bioinformatic_tools:euler to archive:bioinformatic_tools:euler |
||
|---|---|---|---|
| Line 47: | Line 47: | ||
| Once I can get this one test dataset working I won't bother with the other they provided, and move on to testing on Pog. My main goals in running the program on this test data are to eliminate as many confounding variables in getting proper execution, and also to explore and better understand the format that euler expects. Here is what I have discovered about Euler's required data format so far: | Once I can get this one test dataset working I won't bother with the other they provided, and move on to testing on Pog. My main goals in running the program on this test data are to eliminate as many confounding variables in getting proper execution, and also to explore and better understand the format that euler expects. Here is what I have discovered about Euler's required data format so far: | ||
| - | * All reads need to be in a fasta file | + | * All reads need to be in a single fasta file, however this file may contain reads from different runs/technologies. |
| - | * The name of the read matters and is used by Euler to determine whether each sequence has a mate pair, what the mate pair is, and also the distance range of that mate to its pair. | + | * The name of the read matters and is used by Euler to determine whether each sequence has a mate pair, what the mate pair is, and also the distance range of that mate to its pair. This is how you differentiate between reads from different technologies or library protocols. |
| * How Fasta id lines are deciphered is defined by the user in a file called //names.rul// and this file must be placed in the directory you are running your assembly from (your cwd when you start execution). | * How Fasta id lines are deciphered is defined by the user in a file called //names.rul// and this file must be placed in the directory you are running your assembly from (your cwd when you start execution). | ||
archive/bioinformatic_tools/euler.1271825597.txt.gz · Last modified: 2010/04/21 04:53 by jstjohn
Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Noncommercial-Share Alike 3.0 Unported
