<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xml:base="http://www.nodalpoint.org" xmlns:dc="http://purl.org/dc/elements/1.1/">
<channel>
 <title>nodalpoint.org - Phylogenetics - Comments</title>
 <link>http://www.nodalpoint.org/2007/05/22/phylogenetics</link>
 <description>Comments for &quot;Phylogenetics&quot;</description>
 <language>en</language>
<item>
 <title>MAFFT</title>
 <link>http://www.nodalpoint.org/2007/05/22/phylogenetics#comment-3620</link>
 <description>&lt;p&gt;Yep, MAFFT is fast and has excellent alignment quality. My last year&#039;s paper showed that it is the best for prtein alignment, even for distant sequences.&lt;/p&gt;
&lt;br class=&quot;clear&quot; /&gt;</description>
 <pubDate>Thu, 31 May 2007 13:04:32 -0400</pubDate>
 <dc:creator>nuin</dc:creator>
 <guid isPermaLink="false">comment 3620 at http://www.nodalpoint.org</guid>
</item>
<item>
 <title>quicktree</title>
 <link>http://www.nodalpoint.org/2007/05/22/phylogenetics#comment-3618</link>
 <description>&lt;p&gt;I&#039;d use &lt;a href=&quot;http://align.bmr.kyushu-u.ac.jp/mafft/software/&quot;&gt;MAFFT&lt;/a&gt; for aligning something this big.&lt;br /&gt;
&lt;a href=&quot;http://www.sanger.ac.uk/Software/analysis/quicktree/&quot;&gt;quicktree&lt;/a&gt; was designed for building trees from large datasets like this (&lt;a href=&quot;http://www.sanger.ac.uk/Software/Pfam/&quot;&gt;Pfam &lt;/a&gt; families).&lt;/p&gt;
&lt;br class=&quot;clear&quot; /&gt;</description>
 <pubDate>Wed, 30 May 2007 19:07:49 -0400</pubDate>
 <dc:creator>jason</dc:creator>
 <guid isPermaLink="false">comment 3618 at http://www.nodalpoint.org</guid>
</item>
<item>
 <title>Phylip</title>
 <link>http://www.nodalpoint.org/2007/05/22/phylogenetics#comment-3614</link>
 <description>&lt;p&gt;Apart from CD-HIT which is a very good software, I would try using Phylip. The sequences are not large but the actual number of sequences is the problem. Try using a Neighbor Joining approach in Phylip, it won&#039;t be blazing fast but it will do the job, eventually. &lt;/p&gt;
&lt;p&gt;I used Phylip to build a NJ tree of a set of 20000 protein sequences and it took me around 3-4 weeks to get it done on a 3GHz Xeon machine.&lt;/p&gt;
&lt;br class=&quot;clear&quot; /&gt;</description>
 <pubDate>Mon, 28 May 2007 12:07:55 -0400</pubDate>
 <dc:creator>nuin</dc:creator>
 <guid isPermaLink="false">comment 3614 at http://www.nodalpoint.org</guid>
</item>
<item>
 <title>cd-hit</title>
 <link>http://www.nodalpoint.org/2007/05/22/phylogenetics#comment-3612</link>
 <description>&lt;p&gt;For clustering, &lt;a href=&quot;http://bioinformatics.ljcrf.edu/cd-hi/&quot;&gt;CD-HIT&lt;/a&gt; is excellent.  Very fast, handles many sequences.  Used to create the non-redundant datasets in UniProt and at the PDB.&lt;/p&gt;
&lt;p&gt;Phylogeny - I&#039;ve never gone much beyond Clustal and Phylip, both of which would take hours on an average machine with any more than a few thousand sequences.  I&#039;ve heard good things about &lt;a href=&quot;http://mrbayes.csit.fsu.edu/&quot;&gt;MrBayes&lt;/a&gt; - which is MPI-enabled, so could run on a cluster if you have access to one.&lt;/p&gt;
&lt;br class=&quot;clear&quot; /&gt;</description>
 <pubDate>Sat, 26 May 2007 09:48:06 -0400</pubDate>
 <dc:creator>Neil</dc:creator>
 <guid isPermaLink="false">comment 3612 at http://www.nodalpoint.org</guid>
</item>
<item>
 <title>Huge!</title>
 <link>http://www.nodalpoint.org/2007/05/22/phylogenetics#comment-3611</link>
 <description>&lt;p&gt;Alf that is a huge requirement! Are you trying to make tree of life with 1000 base upstream of some house-keeping genes?&lt;br /&gt;
I think MUSCLE [ &lt;a href=&quot;http://www.drive5.com/muscle/&quot; title=&quot;http://www.drive5.com/muscle/&quot;&gt;http://www.drive5.com/muscle/&lt;/a&gt; ] can come to rescue, but you would need a good machine for sure. It uses log-expectation as profile function which is faster and accurate as well [ &lt;a href=&quot;http://www.biomedcentral.com/1471-2105/5/113/table/T2&quot; title=&quot;http://www.biomedcentral.com/1471-2105/5/113/table/T2&quot;&gt;http://www.biomedcentral.com/1471-2105/5/113/table/T2&lt;/a&gt; ]. General algorithm is  &lt;a href=&quot;http://nar.oxfordjournals.org/content/vol32/issue5/images/large/gkh340f2.jpeg&quot; title=&quot;http://nar.oxfordjournals.org/content/vol32/issue5/images/large/gkh340f2.jpeg&quot;&gt;http://nar.oxfordjournals.org/content/vol32/issue5/images/large/gkh340f2...&lt;/a&gt; .&lt;br /&gt;
More details in the paper &lt;a href=&quot;http://nar.oxfordjournals.org/cgi/content/full/32/5/1792&quot; title=&quot;http://nar.oxfordjournals.org/cgi/content/full/32/5/1792&quot;&gt;http://nar.oxfordjournals.org/cgi/content/full/32/5/1792&lt;/a&gt; .&lt;/p&gt;
&lt;p&gt;______________________&quot;The Answer Lies in Genome&quot;______________________&lt;br /&gt;
 &lt;a href=&quot;http://computationalbiologynews.blogspot.com/&quot; title=&quot;http://computationalbiologynews.blogspot.com/&quot;&gt;http://computationalbiologynews.blogspot.com/&lt;/a&gt;&lt;/p&gt;
&lt;br class=&quot;clear&quot; /&gt;</description>
 <pubDate>Sat, 26 May 2007 01:25:17 -0400</pubDate>
 <dc:creator>Animesh</dc:creator>
 <guid isPermaLink="false">comment 3611 at http://www.nodalpoint.org</guid>
</item>
<item>
 <title>Phylogenetics</title>
 <link>http://www.nodalpoint.org/2007/05/22/phylogenetics</link>
 <description>&lt;p&gt;If you had 100,000 DNA sequences, each 1000 nucleotides long, and you wanted to cluster them or create a phylogeny, which software would you use?&lt;/p&gt;
&lt;p&gt;Also, what if they were amino acid sequences, rather than nucleotides?&lt;/p&gt;
&lt;br class=&quot;clear&quot; /&gt;</description>
 <comments>http://www.nodalpoint.org/2007/05/22/phylogenetics#comments</comments>
 <category domain="http://www.nodalpoint.org/forums/discussion/bioinformatics_0">Bioinformatics</category>
 <category domain="http://www.nodalpoint.org/nodalpoint_tags/software">software</category>
 <pubDate>Tue, 22 May 2007 10:06:51 -0400</pubDate>
 <dc:creator>alf</dc:creator>
 <guid isPermaLink="false">2245 at http://www.nodalpoint.org</guid>
</item>
</channel>
</rss>
