Retrieving or updating tip and node data in phylo4d objects
Methods to retrieve or update tip, node or all data associated with a phylogenetic tree stored as a phylo4d object
tdata(x, ...) ## S4 method for signature 'phylo4d' tdata( x, type = c("all", "tip", "internal"), label.type = c("row.names", "column"), empty.columns = TRUE ) tdata(x, ...) <- value ## S4 replacement method for signature 'phylo4d' tdata( x, type = c("all", "tip", "internal"), merge.data = TRUE, clear.all = FALSE, ... ) <- value tipData(x, ...) ## S4 method for signature 'phylo4d' tipData(x, ...) tipData(x, ...) <- value ## S4 replacement method for signature 'phylo4d' tipData(x, ...) <- value nodeData(x, ...) ## S4 method for signature 'phylo4d' nodeData(x, ...) nodeData(x, ...) <- value ## S4 replacement method for signature 'phylo4d' nodeData(x, ...) <- value
x |
A |
... |
For the |
type |
The type of data to retrieve or update: “ |
label.type |
How should the tip/node labels from the tree be returned?
“ |
empty.columns |
Should columns filled with |
value |
a data frame (or object to be coerced to one) to replace the
values associated with the nodes specified by the argument |
merge.data |
if tip or internal node data are provided and data already exists for the other type, this determines whether columns with common names will be merged together (default TRUE). If FALSE, columns with common names will be preserved separately, with “.tip” and “.node” appended to the names. This argument has no effect if tip and node data have no column names in common, or if type=“all”. |
clear.all |
If only tip or internal node data are to be replaced, should data of the other type be dropped? |
tdata
returns a data frame
signature(object="phylo4d")
: retrieve or update data
associated with a tree in a phylo4d
object
Ben Bolker, Thibaut Jombart, Francois Michonneau
data(geospiza) tdata(geospiza) tipData(geospiza) <- 1:nTips(geospiza) tdata(geospiza)
Please choose more modern alternatives, such as Google Chrome or Mozilla Firefox.