nflreadr
The nflverse data loader, whose releases are dictated by the NFL calendar and CRAN's archive policy
A side-by-side editorial comparison of atrrr and e2tree — release velocity, themes, recent moves, and the top alternatives to consider.
The R client for Bluesky adds a firehose and stops assuming Bluesky is the server
atrrr wraps the AT Protocol for R, covering posting, search, profiles, lists, direct messages and starter packs. The latest release adds an experimental firehose implementation and allows connecting to personal data servers other than Bluesky's — Eurosky is the example given. Earlier releases built out the posting surface: videos, multiple images, link preview cards, hashtags, and ggplot2 objects posted directly.
The explainable-ensemble-tree package now measures whether its own explanations are faithful.
e2tree builds a single interpretable tree that approximates a fitted ensemble, working from the proximity structure the ensemble induces between observations. The 1.0.0 release added the piece that had been missing: a Goodness of Interpretability index quantifying how well the approximating tree reconstructs the ensemble's own proximity matrix, with a permutation test for significance. Interactive visualisation and a C++ backend with OpenMP parallelism arrived alongside, and support now spans ranger and CatBoost as well as the original targets.
atrrr wraps the AT Protocol for R, covering posting, search, profiles, lists, direct messages and starter packs. The latest release adds an experimental firehose implementation and allows connecting to personal data servers other than Bluesky's — Eurosky is the example given. Earlier releases built out the posting surface: videos, multiple images, link preview cards, hashtags, and ggplot2 objects posted directly.
Two years of work made atrrr a capable REST client for one network. This release starts undoing that second part. The firehose is a different access mode — a stream rather than a request — which is what researchers doing collection at scale need, and PDS-agnosticism means the package addresses the protocol rather than the company. The rest of the changelog is steadily maintenance-shaped: repeated httr2 compatibility work, endpoint changes tracked as they happen.
The firehose is labelled experimental, so the next release most likely stabilises it rather than opening another front — though the notes give no detail on what remains unfinished.
e2tree builds a single interpretable tree that approximates a fitted ensemble, working from the proximity structure the ensemble induces between observations. The 1.0.0 release added the piece that had been missing: a Goodness of Interpretability index quantifying how well the approximating tree reconstructs the ensemble's own proximity matrix, with a permutation test for significance. Interactive visualisation and a C++ backend with OpenMP parallelism arrived alongside, and support now spans ranger and CatBoost as well as the original targets.
Development has moved from producing an explanation to defending it. The GoI index and its permutation test change the package's claim from here is a tree that resembles your ensemble to here is how closely it resembles it and whether that could have happened by chance — the question a reviewer asks of any surrogate model. Around that, the work is engineering: the proximity matrix construction moved from R-level parallel loops into C++ with thread-level parallelism, and recent releases have been absorbing the awkwardness of supporting multiple ensemble backends, where a multi-class CatBoost objective returns a score matrix where a vector was expected. Interactive visNetwork output and standalone HTML export point at explanations meant to be shared rather than only inspected.
Given how much recent effort has gone into per-backend adapters, expect further work on ensemble compatibility; the entries do not indicate whether the interpretability index is heading toward comparing surrogate trees against each other.
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 atrrr or e2tree.
The nflverse data loader, whose releases are dictated by the NFL calendar and CRAN's archive policy
Fine-mapping workhorse susieR spends its releases hunting null-effect trimming bugs
A rank-based gene signature scorer that has grown by adapting to whatever object format single-cell R uses next
A diagnostic package that generalized past its own name, then learned to say which kind of separation it found
A bias-reduction package reaches 1.0 by adding an estimator built for high-dimensional logistic regression
The JAGS toolkit under RoBMA, shipping the standardization machinery its downstream rewrite needed
See all atrrr alternatives → · See all e2tree alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — r-package — within Analytics. atrrr and e2tree 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. atrrr and e2tree 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 atrrr alternatives in Analytics are ranked by recent ship velocity. Browse the "atrrr alternatives" section above for the current picks, or visit /alternatives/atrrr for the full list with editorial commentary on each.
Top e2tree alternatives in Analytics are ranked by recent ship velocity. Browse the "e2tree alternatives" section above for the current picks, or visit /alternatives/e2tree for the full list with editorial commentary on each.