phylo
-class) from object.phylo
-class) from
a phyloseq-class
. Like other accessors (see
See Also, below), the default behavior of this method is
to stop with an error if physeq
is a
phyloseq-class
but does not contain a phylogenetic
tree (the component data you are trying to access in this
case).
phy_tree(physeq, errorIfNULL=TRUE)
NULL
)? Default TRUE
.phylo
-class object contained
within physeq
; or NULL if physeq
does not
have a tree. This method stops with an error in the
latter NULL case be default, which can be over-ridden by
changing the value of errorIfNULL
to FALSE
.
taxa_names
of the other objects to which it is
going to be paired. The phyloseq
constructor automatically checks for exact agreement in
the set of species described by the phlyogenetic tree and
the other components (taxonomyTable, otu_table), and
trims as-needed. Thus, the tip.labels in a phylo object
must be named to match the results of
taxa_names
of the other objects to which it
will ultimately be paired.
otu_table
, sample_data
,
tax_table
refseq
,
phyloseq
, merge_phyloseq
data(GlobalPatterns)
phy_tree(GlobalPatterns)
Run the code above in your browser using DataLab