PurpleAir
The R client for PurpleAir sensors keeps finding its time-averaging was wrong.
A side-by-side editorial comparison of e2tree and scimesh — release velocity, themes, recent moves, and the top alternatives to consider.
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.
A C++ mesh renderer grinding through CRAN's gate, one policy fix at a time
scimesh is a C++ scientific mesh rendering library with an R binding, released in tight bursts by the dfsp-spirit neuroimaging group. The last month is dominated by CRAN admission work: stripped debug symbols, assert removal in vendored third-party code, vignette index fixes. Around that compliance grind sit genuine additions — an rgl-to-scimesh auto-conversion path, a camera_orbit helper for video, contrast as a render option.
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.
scimesh is a C++ scientific mesh rendering library with an R binding, released in tight bursts by the dfsp-spirit neuroimaging group. The last month is dominated by CRAN admission work: stripped debug symbols, assert removal in vendored third-party code, vignette index fixes. Around that compliance grind sit genuine additions — an rgl-to-scimesh auto-conversion path, a camera_orbit helper for video, contrast as a render option.
The tag stream is non-monotonic — 0.2.5, 0.2.3 and 0.2.6 land within 40 seconds of each other, and 0.2.8 precedes nothing — so version order here says nothing about what shipped when. Read as a whole, the arc is a C++ codebase being domesticated for R distribution: the rendering features are largely settled, and the effort has moved to making an >5MB-adjacent C++ package survive R CMD check --as-cran. The R vignette has been restructured twice in three weeks.
Expect continued CRAN-review round-trips at 0.3.x until acceptance, with feature work confined to the CLI renderer examples rather than the core library.
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 e2tree or scimesh.
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 e2tree alternatives → · See all scimesh alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. scimesh is currently shipping more aggressively (velocity 5.0 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. scimesh is currently shipping more aggressively (velocity 5.0 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 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.
Top scimesh alternatives in Analytics are ranked by recent ship velocity. Browse the "scimesh alternatives" section above for the current picks, or visit /alternatives/scimesh for the full list with editorial commentary on each.