tern.rbmi
Reference-based multiple imputation tables, shipping only what CRAN checks demand.
A side-by-side editorial comparison of enpls and treespace — release velocity, themes, recent moves, and the top alternatives to consider.
enpls has not changed its statistics since 2016 — only its website, twice.
enpls implements ensemble partial least squares regression, with variants for feature selection, outlier detection and model applicability. Across the six most recent releases there is not one change to the modeling code. They cover a documentation website, a website URL change, a font stack, code indentation, a CI service, and most recently a GitHub Actions migration with an R CMD check note fix.
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.
enpls implements ensemble partial least squares regression, with variants for feature selection, outlier detection and model applicability. Across the six most recent releases there is not one change to the modeling code. They cover a documentation website, a website URL change, a font stack, code indentation, a CI service, and most recently a GitHub Actions migration with an R CMD check note fix.
The statistical work finished around version 5.6, which added cross-validation fold control and fixed component selection when the maximum was left unspecified. Everything since has kept the package installable and its docs online. The 2025 release arriving the same day as sibling package grex, with the same two fixes, confirms the pattern: these are maintainer sweeps across a portfolio, not attention to enpls specifically.
The next release will almost certainly be another CRAN or tooling fix. Six consecutive infrastructure-only releases across nine years give no basis for expecting new methods.
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 enpls 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 enpls 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. enpls 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. enpls 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 enpls alternatives in Analytics are ranked by recent ship velocity. Browse the "enpls alternatives" section above for the current picks, or visit /alternatives/enpls 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.