Statistically defining deep branching clades in phylogenetic tree
I have a phylogenetic tree which visually has 3 major clades, one of which forks into two minor clades. I am discussing the groups in the text in regards to the metadata but I want to statistically/technically describe why the groups are seperate.
What is the best way to achieve this? The tree is UPGMA Jackknife generated, with around 150 samples. Note: These are not based on sequence similarity but community structure, so it has to be based on the tree rather than that underlying sequence or similar.
I have been looking at https://www.dendropy.org/ and the https://biopython.org/wiki/Phylo package but can't see a way to achieve this.
Thanks
0 answers
No answers yet.
Log in to answer this question.
More posts like this
-
Get support value of MRCA given a list of tip.label in R newick trees
written by pl.terzian •
-
Building a phylogenetic tree from different ortholog groups
written by timothy.kirkwood •
-
Cytoscape: Advice on best analysis methods for PPI network
written by Haley •
-
Forum: Sharing frequently asked questions about microbial genome sequencing II
written by Novogene •
-
Is variation between samples reason for DESeq2 not calling DEGs significant?
written by molbioTH •
-
Do we still really need to remove the sequence (Protein or Genome) redundancy when using deep learn…
written by kurdt325 •
-
PAML ancestral sequences reconstruction
written by ulises.rodriguez •
-
Obtain sequences to test positive selection using dN/dS statistics?
written by LauferVA
-
News: Travel and accommodation bursaries for workshops on Gene expression analysis, Metabolomics, R…
written by Daniel
-
Verifying A Quality Improvement For Multiple Sequence Aligments (Msa)
written by Aleksandr Levchuk
I’ve used Simon Harris’ script (https://github.com/simonrharris/tree_gubbins) to ‘objectively define clades’ in the past to varying degrees of success. May be of interest?
Thanks for the suggestion. I've been giving it a go but it's basically only identifying everything into one cluster. Having a look at ete but not solved it yet.