tern.rbmi
Reference-based multiple imputation tables, shipping only what CRAN checks demand.
A side-by-side editorial comparison of EvoPhylo and treespace — release velocity, themes, recent moves, and the top alternatives to consider.
EvoPhylo added BEAST2 alongside MrBayes, then went quiet for two years.
EvoPhylo handles post-processing for Bayesian evolutionary rate and fossilized birth-death analyses, originally against MrBayes output. The 0.3.2 release added BEAST2 support for both FBD functions and rates analysis, making it usable by labs on either platform. Since then there has been one clock-partition fix and, in August 2025, a release whose notes say only that there are updated functions and bug fixes.
treespace ships once every year or two, and only when CRAN or a user forces it.
treespace explores and compares sets of phylogenetic and transmission trees, including the tree-distance measures used in outbreak reconstruction. Its release history is entirely reactive: five updates across five years, each triggered by a CRAN policy change, an upstream package removal, or a bug someone reported. The most recent is an Rd cross-reference format patch plus a maintainer email change.
EvoPhylo handles post-processing for Bayesian evolutionary rate and fossilized birth-death analyses, originally against MrBayes output. The 0.3.2 release added BEAST2 support for both FBD functions and rates analysis, making it usable by labs on either platform. Since then there has been one clock-partition fix and, in August 2025, a release whose notes say only that there are updated functions and bug fixes.
The package's substantive arc ended with the 0.3.2 publication release, which arrived with peer-review revisions and three first-time contributors — the shape of software built to accompany a paper. What follows is thin: a MrBayes plotting correction in 0.3.3, then a two-year gap and a release with no described contents. The August 2025 entry may contain real work, but the notes give a reader nothing to judge.
Without release notes on the latest version there is no observable basis for predicting the next move; the two-year gap before it suggests activity tied to specific research needs rather than a maintenance cadence.
treespace explores and compares sets of phylogenetic and transmission trees, including the tree-distance measures used in outbreak reconstruction. Its release history is entirely reactive: five updates across five years, each triggered by a CRAN policy change, an upstream package removal, or a bug someone reported. The most recent is an Rd cross-reference format patch plus a maintainer email change.
The package is stable and lightly staffed rather than abandoned — bugs that affect correctness do get fixed, and CRAN deadlines are met. But the 2023 update is the telling one: rather than vendor or replace adephylo when it faced removal, the maintainers disabled two tree-vector methods and marked the loss as hopefully temporary. Two years on, nothing in the feed indicates they came back.
The next entry will most likely be another CRAN-compliance patch, on the pattern of four of the last five releases. Whether the Abouheif and sumDD methods ever return is not something these entries give any signal on.
Other Analytics products tracked by Sparkpulse, ranked by recent ship velocity. Each card links to a full editorial trajectory and lets you pivot into a head-to-head comparison with either EvoPhylo or treespace.
Reference-based multiple imputation tables, shipping only what CRAN checks demand.
An MMRM tabulation package that has published nothing since its 2024 CRAN releases.
A single-purpose ggplot2 inset tool, refining the same three arguments.
An R symbolic-maths binding whose changelog is really the C++ core's release notes.
gtfstools stopped guarding its own object model and started accepting everyone else's.
The glue package that makes R carry units and uncertainty through the same calculation.
See all EvoPhylo alternatives → · See all treespace alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — phylogenetics — within Analytics. EvoPhylo and treespace are shipping at a similar cadence (velocity 0.0 vs 0.0, both within Sparkpulse's "active" band). See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. EvoPhylo and treespace are shipping at a similar cadence (velocity 0.0 vs 0.0, both within Sparkpulse's "active" band). For your specific use case, the alternatives sections above list other Analytics products to evaluate alongside.
Top EvoPhylo alternatives in Analytics are ranked by recent ship velocity. Browse the "EvoPhylo alternatives" section above for the current picks, or visit /alternatives/evophylo for the full list with editorial commentary on each.
Top treespace alternatives in Analytics are ranked by recent ship velocity. Browse the "treespace alternatives" section above for the current picks, or visit /alternatives/treespace-r for the full list with editorial commentary on each.