PurpleAir
The R client for PurpleAir sensors keeps finding its time-averaging was wrong.
A side-by-side editorial comparison of b3gbi and e2tree — release velocity, themes, recent moves, and the top alternatives to consider.
b3gbi pulled confidence intervals out of its indicator workflow and handed them to dubicube.
b3gbi computes biodiversity indicators from GBIF occurrence cubes for the B-Cubed project, and sits at 0.9.4 in a JOSS review run-up. The 0.9 release decoupled uncertainty from indicator calculation: confidence intervals are no longer produced inline but added afterward with add_ci(), backed by whole-cube bootstrapping from the sibling dubicube package. Everything since has been grid-parsing and compatibility repair around that split.
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.
b3gbi computes biodiversity indicators from GBIF occurrence cubes for the B-Cubed project, and sits at 0.9.4 in a JOSS review run-up. The 0.9 release decoupled uncertainty from indicator calculation: confidence intervals are no longer produced inline but added afterward with add_ci(), backed by whole-cube bootstrapping from the sibling dubicube package. Everything since has been grid-parsing and compatibility repair around that split.
Two forces are shaping releases. Internally, the uncertainty split produced an indicator-specific rule book — species-level indicators bootstrap the whole cube, raw counts resample within year, evenness gets a logit transform — and that rule book is where the statistical thinking now lives. Externally, GBIF's taxonomic backbone migration to the Catalogue of Life forced string taxon keys through process_cube() and the plotting paths, while recurring EEA and MGRS grid-code fixes mark coordinate parsing as the least settled area.
The 0.9.4 notes are entirely JOSS review items — contributors, examples, tracked datasets — so the next release is most likely a JOSS-accepted 1.0 rather than new indicator work.
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 b3gbi or e2tree.
The R client for PurpleAir sensors keeps finding its time-averaging was wrong.
A board game graphics package runs one of the most disciplined deprecation cycles in R.
The discrete-data FDR package is being pared into one piece of a larger multiple-testing suite.
A scientific-text analysis package moved from counting citations to classifying argument structure.
The teaching arm of an R reliability suite keeps pace with whatever its analysis siblings ship.
The Weibull plotting package renamed itself, then handed its charts to AI assistants.
See all b3gbi alternatives → · See all e2tree alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. b3gbi is currently shipping more aggressively (velocity 2.5 vs 0.0), with 0 editorial sparks in the last 30 days against 0. 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. b3gbi is currently shipping more aggressively (velocity 2.5 vs 0.0), with 0 editorial sparks in the last 30 days against 0. For your specific use case, the alternatives sections above list other Analytics products to evaluate alongside.
Top b3gbi alternatives in Analytics are ranked by recent ship velocity. Browse the "b3gbi alternatives" section above for the current picks, or visit /alternatives/b3gbi 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.