Class bammdata

[macroevolution]

Class bammdata

[drabosky]

this is probably a good idea. the main reason I originally did this was so that someone could have a quick view of the tree itself by using regular class phylo operations, especially plot.phylo. But maybe it would just be best to have plot.dtrates be the default method for the data object.

I'm trying to think of anything else that might be affected by this but can't really.

~D

On Dec 10, 2013, at 7:22 PM, blueraleigh wrote:

Thoughts on changing the class of the object returned by getEventData to "bammdata" only? One advantage would be that a number of functions could dispatch methods on the bammdata object directly. So, for example,

x <- getEventData(phy, eventdata);
class(x);
[1] "bammdata" ##rather than [1] "phylo" "bamm-data"
plot(x) ##rather than calling plot.dtrates(x);
would immediately plot the dynamic rates tree if plot.dtrates is renamed to plot.bammdata. Because BAMMtools has the function as.phylo.bammdata is there a compelling reason to have two class names attached to the bammdata object?

—
Reply to this email directly or view it on GitHub.