the main server is usually working at
[1] if it is down try [2]

Phylogeny is changing with the number of sequences

This is not a real problem and fairly normal, but it is rather confusing.
The best way to do is to begin with a low number of sequences to align (30) and if necessary (the tree has no external root outside the closest species of the query) increase gradually. Be aware, more time is needed for computing !
The is an optimal number of sequences for each problem, depending of both the query (its species) and the database.

Phylogeny is changing with the gaps options

There are two options to construct the tree, each option give a different tree :

Undetermined Bug during computing

The label :

http://umr5558-mq1.univ-lyon1.fr/WIKIS/mq_wiki/attachments/bibiW2.png


indicate that a bug occurs. This is fairly rare now. This is mainly due to computing problems during the construction of the HTML tree, and the tree may be only partially computed.

No BLAST hits

The following information is given :

http://umr5558-mq1.univ-lyon1.fr/WIKIS/mq_wiki/attachments/bibiW6.png

Small DNA segment

Here is the information :

http://umr5558-mq1.univ-lyon1.fr/WIKIS/mq_wiki/attachments/bibiW1.png

No Real Tree

http://umr5558-mq1.univ-lyon1.fr/WIKIS/mq_wiki/attachments/bibiW3.png

Lack of biodiversity

In the case of :

http://umr5558-mq1.univ-lyon1.fr/WIKIS/mq_wiki/attachments/bibiW5.png

Mon Apr 16 21:42:14 2012

Valid CSS! PRABI image Valid CSS! [Python Powered]