Answers.Body: <p>If 1E6 is genetic distance, this means one nucleotide difference per million base pairs, which is of course incredibly small and bootstrapping at this level doesn't really work. So what I suspect is happening is that the bootstrap is so low it is not present on the tree. You can assign a cut-off bootstrap but anything below 75% is not interpretable in any case. What might be happening is you are producing the bootstrap &quot;cladogram&quot; which is showing a default branch length, but when &lt;1E6 genetic distance it is showing a trifurcation. This simply means the bootstrap of the consensus tree is so low it is collapsing the branch and this is a function of the very small genetic distance at this node.</p>
  <hr />
  <p>Looking at your treefile I don't see any collapsed clades.</p>
  <pre><code>(Group_9:0.00000100000050002909,(Group_50:0.00507659947127924935, (.
  </code></pre>
  <p>The clade above has not been colapsed it is just a very small distance in a paraphyletic group. It looks fine to me, i.e. Group_9 is 1E6. It could look 'collapsed' simply because it is so small it is difficult to see. I hope thats ok?</p>
  
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2020-07-21T14:31:25.617Z
Answers.Text: Could you post post of the raw tree file to examine this in more detail?
Answers.UserDisplayName: M__
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2020-07-21T14:36:22.210Z
Answers.Text: My apologies, it is collapsing nodes where the genetic distance to that node is 1e-6. Here is a snippet: (((Group_40:0.00000100000050002909,(((Group_14:0.00506368298581611701,Group_5:0.00504476117481173891):0.00000100000050002909,(((((Group_6:0.00506368450410310620,Group_18:0.00503828136153215873):0.00000100000050002909,(Group_1:0.00506367795420949521,(Group_7:0.00000100000050002909,(Group_9:0.00000100000050002909,(Group_50:0.00507659947127924935, (..........       I can also provide the tree file by email if that would be helpful.
Answers.UserDisplayName: Ace8910
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2020-07-21T15:32:11.497Z
Answers.Text: It looks fine from the treefile you posted (above)
Answers.UserDisplayName: M__
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2020-07-21T20:25:56.393Z
Answers.Text: Thanks Michael, yeah the sequences were only 500 nt long, so I believe those breakpoints aren't informative in terms of mutations occurring. We are trying to map instances of mutations to a reference genome using the trees created.
Answers.UserDisplayName: Ace8910
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2020-07-21T20:48:07.400Z
Answers.Text: Thanks, please tick my answer as "accepted"  if it was useful. We can deal with other other questions separately on another day. You may need ETE3 when you scale up to automate the your search.
Answers.UserDisplayName: M__
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2020-07-21T08:26:23.357Z
Answers.LastActivityDate: 2020-07-21T17:40:09.837Z
Answers.LastEditDate: 2020-07-21T17:40:09.837Z
Answers.UserDisplayName: M__
Body: <p>I have been creating phylogenetic trees using RAxML (using Boostrap + ML) and I end up with a bestTree file, outputted in newick format. When I open up the tree in FigTree, I notice that it collapses many of the internal nodes with small values (1 x 10-6). I am working on visualizing the trees using ETE, which when I render the tree includes these small breakpoints. I was wondering if there is a standard for when to collapse nodes that are considered phylogenetically uninformative that I can apply. Thank you for any help.</p>
  
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2020-07-21T08:10:59.303Z
Comments.Text: Hi @Ace8910 what do you mean by E-6 .. are you referring to genetic distance?
Comments.UserDisplayName: M__
Tags: <phylogenetics><phylogeny>
Title: Standard for when to collapse phylogenetically uninformative nodes
ThreadText: # Standard for when to collapse phylogenetically uninformative nodes
  
  (Asked by: username_0 on 2020-07-21)
  
  I have been creating phylogenetic trees using RAxML (using Boostrap + ML) and I end up with a bestTree file, outputted in newick format. When I open up the tree in FigTree, I notice that it collapses many of the internal nodes with small values (1 x 10-6). I am working on visualizing the trees using ETE, which when I render the tree includes these small breakpoints. I was wondering if there is a standard for when to collapse nodes that are considered phylogenetically uninformative that I can apply. Thank you for any help.
  
  **Tags:** phylogenetics, phylogeny
  
  > **Comments:**
  > **username_1**: Hi @username_0 what do you mean by E-6 .. are you referring to genetic distance?  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_1 on 2020-07-21. Score: 1 | Accepted answer
  
  If 1E6 is genetic distance, this means one nucleotide difference per million base pairs, which is of course incredibly small and bootstrapping at this level doesn't really work. So what I suspect is happening is that the bootstrap is so low it is not present on the tree. You can assign a cut-off bootstrap but anything below 75% is not interpretable in any case. What might be happening is you are producing the bootstrap "cladogram" which is showing a default branch length, but when <1E6 genetic distance it is showing a trifurcation. This simply means the bootstrap of the consensus tree is so low it is collapsing the branch and this is a function of the very small genetic distance at this node.
  
  ---
  
  Looking at your treefile I don't see any collapsed clades.
  
  ```
  (Group_9:0.00000100000050002909,(Group_50:0.00507659947127924935, (.
  
  ```
  
  The clade above has not been colapsed it is just a very small distance in a paraphyletic group. It looks fine to me, i.e. Group\_9 is 1E6. It could look 'collapsed' simply because it is so small it is difficult to see. I hope thats ok?
  
  > **Comments:**
  > **username_1**: Could you post post of the raw tree file to examine this in more detail?  
  > **username_0**: My apologies, it is collapsing nodes where the genetic distance to that node is 1e-6. Here is a snippet: (((Group_40:0.00000100000050002909,(((Group_14:0.00506368298581611701,Group_5:0.00504476117481173891):0.00000100000050002909,(((((Group_6:0.00506368450410310620,Group_18:0.00503828136153215873):0.00000100000050002909,(Group_1:0.00506367795420949521,(Group_7:0.00000100000050002909,(Group_9:0.00000100000050002909,(Group_50:0.00507659947127924935, (..........       I can also provide the tree file by email if that would be helpful.  
  > **username_1**: It looks fine from the treefile you posted (above)  
  > **username_0**: Thanks Michael, yeah the sequences were only 500 nt long, so I believe those breakpoints aren't informative in terms of mutations occurring. We are trying to map instances of mutations to a reference genome using the trees created.  
  > **username_1**: Thanks, please tick my answer as "accepted"  if it was useful. We can deal with other other questions separately on another day. You may need ETE3 when you scale up to automate the your search.  
  
  ---
  
  