tern.rbmi
Reference-based multiple imputation tables, shipping only what CRAN checks demand.
A side-by-side editorial comparison of protr and treespace — release velocity, themes, recent moves, and the top alternatives to consider.
protr's feature set is finished; the work now is surviving Bioconductor's churn.
protr generates numerical descriptors from protein sequences for machine learning, plus alignment-based similarity between sequences. The descriptor functions have been stable for years. Recent releases divide cleanly into two kinds: extending the similarity computations to work under memory constraints, and absorbing the Bioconductor split that moved pairwise alignment out of Biostrings into pwalign.
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.
protr generates numerical descriptors from protein sequences for machine learning, plus alignment-based similarity between sequences. The descriptor functions have been stable for years. Recent releases divide cleanly into two kinds: extending the similarity computations to work under memory constraints, and absorbing the Bioconductor split that moved pairwise alignment out of Biostrings into pwalign.
The similarity side is where the remaining engineering goes, and it follows a consistent pattern — whatever parSeqSim() gained, crossSetSim() eventually gets. Batching, verbose progress and a disk-backed variant all arrived for the single-set case first and were mirrored for the cross-set case in 1.7-1. That is a maintainer closing feature-parity gaps rather than opening new directions, and the two most recent releases contain no user-facing change at all.
Expect the next release to react to another Bioconductor or R CMD check change, which accounts for three of the last four. The similarity functions now have parity, so there is no obvious internal backlog left.
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 protr 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 protr alternatives → · See all treespace alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — maintenance-mode — within Analytics. protr 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. protr 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 protr alternatives in Analytics are ranked by recent ship velocity. Browse the "protr alternatives" section above for the current picks, or visit /alternatives/protr-r 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.