randomwalk
randomwalk spent every release getting an R simulation to run in the browser, not on a server.
A side-by-side editorial comparison of gcube and lstar — release velocity, themes, recent moves, and the top alternatives to consider.
gcube's recent releases are all packaging metadata, not simulation code
gcube simulates biodiversity data cubes — generating occurrence points, sampling them under configurable detection bias, and designating them to a grid — as a testbed for the B-Cubed project's indicator tooling. The visible release history is almost entirely metadata and release-automation work: Zenodo grant IDs, ROR URL fixes, publisher fields, funder and rights-holder descriptions. The simulation functionality itself is not what these entries are about.
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.
gcube simulates biodiversity data cubes — generating occurrence points, sampling them under configurable detection bias, and designating them to a grid — as a testbed for the B-Cubed project's indicator tooling. The visible release history is almost entirely metadata and release-automation work: Zenodo grant IDs, ROR URL fixes, publisher fields, funder and rights-holder descriptions. The simulation functionality itself is not what these entries are about.
The February 2026 cluster reads as a package wiring up its archival identity rather than developing: four releases in four days, one of them explicitly a test of the GitHub release path. That is characteristic of research software preparing to be cited — a Zenodo DOI, correct funder attribution and a checklist-compliant description are the deliverables when the funder requires them. Substantive work on mapping functions and grid designation appears earlier and only through tutorial fixes.
With the Zenodo integration and metadata now settled, expect attention to return to the simulation functions themselves, most likely driven by what the sibling indicator packages need to test against.
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 gcube or lstar.
randomwalk spent every release getting an R simulation to run in the browser, not on a server.
fastml added survival modelling and leakage-proof resampling, moving past classification and regression.
abclass built out angle-based classifiers in 2022, then went quiet except for CRAN upkeep.
churon is spending its entire release history getting a Rust ONNX binding through CRAN.
firatheme woke up after four years and started fixing what ggplot2 changed underneath it.
bagyo reached CRAN as a Philippine tropical cyclone dataset, with its tags stamped out of order.
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 gcube alternatives in Analytics are ranked by recent ship velocity. Browse the "gcube alternatives" section above for the current picks, or visit /alternatives/gcube 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.