lstar
A single-cell data store commits to Zarr v3 and range-readable hosting across four language surfaces
A side-by-side editorial comparison of glmbayes and soilDBdata — release velocity, themes, recent moves, and the top alternatives to consider.
A GPU-accelerated Bayesian GLM package buys its way into the standard R Bayesian toolchain
glmbayes fits Bayesian generalized linear models with optional OpenCL acceleration. The last four months moved it from a package with its own vocabulary to one that answers the insight and bayestestR generics the rest of the R Bayesian ecosystem is built on, while pushing the OpenCL kernels out into a separate nmathopencl dependency that carries CRAN Windows binaries. It returned to CRAN in August after an archival over a configure policy issue.
soilDBdata exists so soilDB's tests can run without a NASIS connection.
soilDBdata is a data-only package supplying NASIS and gSSURGO sample datasets as .sqlite assets, installed separately by soilDB's GitHub Actions so unit tests that would otherwise need database access can run. It began as a proof of concept carrying MT663 pedon and component tables used in soil survey coursework, and its most recent release adds a Marshall Islands FY26 gSSURGO dataset. Releases are infrequent and driven by what the parent package needs to test.
glmbayes fits Bayesian generalized linear models with optional OpenCL acceleration. The last four months moved it from a package with its own vocabulary to one that answers the insight and bayestestR generics the rest of the R Bayesian ecosystem is built on, while pushing the OpenCL kernels out into a separate nmathopencl dependency that carries CRAN Windows binaries. It returned to CRAN in August after an archival over a configure policy issue.
The arc is about removing reasons not to use it. GPU support was previously blocked on Windows because the OpenCL kernels were vendored; splitting them into a CRAN package with binaries fixed that. The ecosystem work does the same thing for tooling — a glmb fit now responds to get_parameters, get_priors, simulate_prior and check_prior, so it drops into workflows built around easystats rather than requiring its own. The CRAN archival and the configure fixes that followed show how much of the effort goes into distribution rather than modelling.
get_priors() returning the full prior specification rather than a marginal table is the kind of detail that invites further bayestestR integration, and the diagnostic surface is the least built-out part of what has shipped so far.
soilDBdata is a data-only package supplying NASIS and gSSURGO sample datasets as .sqlite assets, installed separately by soilDB's GitHub Actions so unit tests that would otherwise need database access can run. It began as a proof of concept carrying MT663 pedon and component tables used in soil survey coursework, and its most recent release adds a Marshall Islands FY26 gSSURGO dataset. Releases are infrequent and driven by what the parent package needs to test.
Development follows soilDB rather than leading it: assets get bumped when a soilDB version changes, and purpose lists are updated when soilDB adds a table. The one release that changed what testing is possible was v0.1.1, which added selected-set _View_1 tables alongside whole tables so both SS=TRUE and SS=FALSE code paths could be exercised. Four-year gaps between releases are normal here and do not indicate abandonment — a fixture package only needs to move when the fixtures go stale.
The recent addition is a new geography rather than a new table structure, so further releases most likely continue broadening dataset coverage as soilDB gains regions to test against.
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 glmbayes or soilDBdata.
A single-cell data store commits to Zarr v3 and range-readable hosting across four language surfaces
Text analysis in R keeps optimising its token internals — and builds a path out to torch
The ModernDive teaching package learns to render inside the browser that runs its own textbook
USGS puts a type system over its river network toolkit so errors surface at dispatch
The chromatography file-format translator keeps absorbing vendor formats one release at a time
A year after gutting itself for a C++ rewrite, SLOPE is back to polishing the interface
See all glmbayes alternatives → · See all soilDBdata alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. glmbayes is currently shipping more aggressively (velocity 6.3 vs 0.0), with 1 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. glmbayes is currently shipping more aggressively (velocity 6.3 vs 0.0), with 1 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 glmbayes alternatives in Analytics are ranked by recent ship velocity. Browse the "glmbayes alternatives" section above for the current picks, or visit /alternatives/glmbayes for the full list with editorial commentary on each.
Top soilDBdata alternatives in Analytics are ranked by recent ship velocity. Browse the "soilDBdata alternatives" section above for the current picks, or visit /alternatives/soildbdata for the full list with editorial commentary on each.