PurpleAir
The R client for PurpleAir sensors keeps finding its time-averaging was wrong.
A side-by-side editorial comparison of e2tree and lstar — 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 single-cell data store commits to Zarr v3 and range-readable hosting across four language surfaces
lstar stores single-cell data behind one C++ core with Python, R and JS/WASM bindings, and ships a browser viewer that reads the store directly. Zarr v3 is now the default on-disk format across all four surfaces, with zstd compression and sharding that packs many chunks into fewer objects. Viewer stores are compressed per field and resolved at chunk granularity, so a hosted viewer fetches only what it displays. The tag stream carries both lstar and lstar-sc releases.
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.
lstar stores single-cell data behind one C++ core with Python, R and JS/WASM bindings, and ships a browser viewer that reads the store directly. Zarr v3 is now the default on-disk format across all four surfaces, with zstd compression and sharding that packs many chunks into fewer objects. Viewer stores are compressed per field and resolved at chunk granularity, so a hosted viewer fetches only what it displays. The tag stream carries both lstar and lstar-sc releases.
The through-line is making a hosted store cheap to read. Sharding addresses the file-per-chunk explosion that makes many-chunk arrays awkward to host; per-field compression with chunk-granular resolution means colouring an embedding by one gene fetches one column rather than an array. The 0.2.x patches are the cost of maintaining four surfaces at once — a WASM heap crash that only browsers exercise, and a count-basis orientation defect where all three surfaces normalized in memory and none owned the on-disk layout.
The orientation bug's root cause — no surface owning the on-disk representation while all three normalized in memory — is the kind of gap that usually produces a validation or ownership change rather than another point fix.
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 lstar.
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 lstar alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. lstar 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. lstar 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 lstar alternatives in Analytics are ranked by recent ship velocity. Browse the "lstar alternatives" section above for the current picks, or visit /alternatives/lstar for the full list with editorial commentary on each.