mev
An extreme-value toolkit reorganised its whole API into prefixed families and tripled its estimator count.
Comparison · Analytics
randomwalk vs soilDBdata
A side-by-side editorial comparison of randomwalk and soilDBdata — release velocity, themes, recent moves, and the top alternatives to consider.
Shared themes:r package
randomwalk vs soilDBdata: at a glance
What is randomwalk?
randomwalk spent every release getting an R simulation to run in the browser, not on a server.
A random walk and fractal-growth simulation package whose entire visible history is about its browser deployment. Six releases in four weeks moved a Shinylive dashboard from a blank black page to a working app — WebAssembly mounted from GitHub releases, CORS resolved by same-origin serving, missing plotting dependencies installed in-browser, then an async version using crew workers with its own debug log. A correctness fix followed, adding termination-position validation so simulations stop producing isolated pixels, and the most recent release publishes the package itself as a webR binary repository.
What is soilDBdata?
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.
randomwalk vs soilDBdata: editorial side-by-side
randomwalk
0.0ANALYTICS
randomwalk spent every release getting an R simulation to run in the browser, not on a server.
◆ Current state
A random walk and fractal-growth simulation package whose entire visible history is about its browser deployment. Six releases in four weeks moved a Shinylive dashboard from a blank black page to a working app — WebAssembly mounted from GitHub releases, CORS resolved by same-origin serving, missing plotting dependencies installed in-browser, then an async version using crew workers with its own debug log. A correctness fix followed, adding termination-position validation so simulations stop producing isolated pixels, and the most recent release publishes the package itself as a webR binary repository.
◆ Where it's heading
The package is being built as a browser artifact first and an R package second: the readme, the vignettes and the release notes all point at a hosted dashboard rather than at library(). The last release completes that by making the compiled WebAssembly build installable by anyone via webr::install(), which turns the deployment work into something reusable outside this project. Version numbers are unreliable here — v0.2.0 was published two weeks after v1.0.2 — so read the dates, not the tags.
◆ Prediction
With the webR repository published, the next work most likely moves back to the simulation itself, though the entries give no direct evidence of planned features.
soilDBdata
0.0ANALYTICS
soilDBdata exists so soilDB's tests can run without a NASIS connection.
◆ Current state
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.
◆ Where it's heading
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.
◆ Prediction
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.
Alternatives to randomwalk and soilDBdata
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 randomwalk or soilDBdata.
nflseedR
nflseedR rewrote its simulator from scratch and put the original on a deprecation clock.
TLF-Library
The Open Systems Pharmacology plotting layer spent 2025 absorbing a ggplot2 major break.
skylight
A frozen astronomical model quietly became the inner loop of its sibling's optimizer.
fastml
fastml added survival modelling and leakage-proof resampling, moving past classification and regression.
abclass
abclass built out angle-based classifiers in 2022, then went quiet except for CRAN upkeep.
See all randomwalk alternatives → · See all soilDBdata alternatives →
Recent activity from randomwalk and soilDBdata
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 3mo agosoilDBdataMarshall Islands FY26 gSSURGO dataset added
- 8mo agorandomwalkPackage published as an installable webR binary repository
- 8mo agorandomwalkTermination validation removes isolated pixels from simulations
- 8mo agorandomwalkAsync dashboard with crew workers running under WebR
- 9mo agorandomwalkBrowser dashboard working end to end
- 9mo agorandomwalkMissing plot dependency and parameter display fixed
- 9mo agorandomwalkDashboard mounts WebAssembly from GitHub releases
- 1y agosoilDBdataMT663 fixtures refreshed for soilDB 2.8.3
- 1y agosoilDBdataNASIS purpose lists updated for siteothvegclass
- 4y agosoilDBdataSelected-set _View_1 tables enable SS=TRUE/FALSE testing
- 4y agosoilDBdataProof of concept: MT663 pedon and component .sqlite fixtures
Frequently asked questions
What is the difference between randomwalk and soilDBdata?
Both compete on the same themes — r package — within Analytics. randomwalk and soilDBdata are shipping at a similar cadence (velocity 0.0 vs 0.0, both within Sparkpulse's "active" band). See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.
Is randomwalk better than soilDBdata?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. randomwalk and soilDBdata are shipping at a similar cadence (velocity 0.0 vs 0.0, both within Sparkpulse's "active" band). For your specific use case, the alternatives sections above list other Analytics products to evaluate alongside.
What are the best alternatives to randomwalk?
Top randomwalk alternatives in Analytics are ranked by recent ship velocity. Browse the "randomwalk alternatives" section above for the current picks, or visit /alternatives/randomwalk for the full list with editorial commentary on each.
What are the best alternatives to soilDBdata?
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.