e2tree
The explainable-ensemble-tree package now measures whether its own explanations are faithful.
A side-by-side editorial comparison of haze and lstar — release velocity, themes, recent moves, and the top alternatives to consider.
Four dormant years end with a modernization pass and an off-by-one fix in the C++ core
haze does nearest-neighbour smoothing and k-d tree interpolation on brain surface meshes. It sat untouched from April 2022 until July 2026, when a single release modernized it for current R versions and corrected an off-by-one error in the C++ code. It is not on CRAN and never will be — the package exceeds 50MB against CRAN's 5MB ceiling, a constraint its own initial release notes acknowledge.
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.
haze does nearest-neighbour smoothing and k-d tree interpolation on brain surface meshes. It sat untouched from April 2022 until July 2026, when a single release modernized it for current R versions and corrected an off-by-one error in the C++ code. It is not on CRAN and never will be — the package exceeds 50MB against CRAN's 5MB ceiling, a constraint its own initial release notes acknowledge.
The July 2026 release arrived 56 minutes after its sibling regfusionr 0.3.0 from the same maintainer, which is the tell: this is a maintainer sweeping a set of related neuroimaging packages back into working order, not independent development on haze itself. haze is the dependency, regfusionr the consumer, and the substantive work sits on the regfusionr side. The off-by-one correction is the only change here that alters results.
Expect haze to move only when a downstream dfsp-spirit package needs it to — its cadence is driven by the sibling packages, not by its own roadmap.
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 haze or lstar.
The explainable-ensemble-tree package now measures whether its own explanations are faithful.
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.
A reliability growth package put its models behind an MCP server for AI assistants to call.
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 2.5), 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 2.5), 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 haze alternatives in Analytics are ranked by recent ship velocity. Browse the "haze alternatives" section above for the current picks, or visit /alternatives/haze 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.