this is for holding javascript data
David Coil edited Building a 16S rDNA Phylogenetic Tree.md
about 9 years ago
Commit id: d5949f0496791e22b914a08cf2a1ea15218b3351
deletions | additions
diff --git a/Building a 16S rDNA Phylogenetic Tree.md b/Building a 16S rDNA Phylogenetic Tree.md
index d371a01..b3f0839 100644
--- a/Building a 16S rDNA Phylogenetic Tree.md
+++ b/Building a 16S rDNA Phylogenetic Tree.md
...
We recommend viewing the tree as a phylogram which can be accomplished by clicking on the phylogram button (labeled in Figure \ref{fig:Dendroscope}). From this tree it should be possible to determine the phylogenetic placement of the candidate sequence, and in some cases to give it a name with more certainty than a simple BLAST search. Below are examples of a relatively informative tree and a relatively uninformative tree:
In tree shown in Figure \ref{fig:Tree1} (genus _Brachybacterium_), our sample of interest from an assembly is "Brachybacterium muris UCD-AY4"
\cite{Lo\_2013}. \cite{23516213}. It falls within a clade where every named member has the same name "Brachybacterium muris", and this name does not occur elsewhere on the tree. Hence, we were confident enough to name our sample as that species. In other words, this sequence falls within a well-supported monophyletic clade of _Brachybacterium muris_.
In the tree shown in Figure \ref{fig:Tree2} (genus _Tatumella_) our species of interest is _Tatumella_
sp. \cite{Bendiks_2013}. sp \cite{24762940}. In contrast to the _Brachybacterium_ example, here our species falls within a poorly defined clade containing multiple species. In this case we did not assign a species name to this isolate.