tEDM
The temporal half of the stscl EDM pair, tracking its spatial sibling
Comparison · Analytics
bayestools vs soilDBdata
A side-by-side editorial comparison of bayestools and soilDBdata — release velocity, themes, recent moves, and the top alternatives to consider.
bayestools vs soilDBdata: at a glance
What is bayestools?
The JAGS toolkit under RoBMA, shipping the standardization machinery its downstream rewrite needed
BayesTools provides the shared JAGS fitting, prior and summary infrastructure that the author's meta-analysis packages build on. The 0.2.x line filled in modeling primitives — prior_mixture() and mixed-posterior objects in 0.2.18, expression-valued priors and lme4-style uncorrelated random effects in 0.2.20, then a run of small diagnostic fixes for mixture and spike-and-slab priors. Version 0.3.0 in May 2026 adds automatic standardization of continuous predictors, default priors for unspecified factor and continuous terms, and functions to transform prior and posterior samples back to the original scale.
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.
bayestools vs soilDBdata: editorial side-by-side
bayestools
0.0ANALYTICS
The JAGS toolkit under RoBMA, shipping the standardization machinery its downstream rewrite needed
◆ Current state
BayesTools provides the shared JAGS fitting, prior and summary infrastructure that the author's meta-analysis packages build on. The 0.2.x line filled in modeling primitives — prior_mixture() and mixed-posterior objects in 0.2.18, expression-valued priors and lme4-style uncorrelated random effects in 0.2.20, then a run of small diagnostic fixes for mixture and spike-and-slab priors. Version 0.3.0 in May 2026 adds automatic standardization of continuous predictors, default priors for unspecified factor and continuous terms, and functions to transform prior and posterior samples back to the original scale.
◆ Where it's heading
This package's releases are best read against what depends on them. The 0.2.x fixes track features appearing in RoBMA one version later, and 0.3.0 landed a single day before RoBMA 4.0.0 — the standardization and sample-transformation functions are the substrate that rewrite needed. The direction of the work is toward sensible defaults: default priors by predictor type, automatic standardization for sampling stability, and transformation back to interpretable scale so the convenience does not cost the user their units.
◆ Prediction
Given how tightly its releases track downstream needs, the next version is most likely driven by gaps surfacing in RoBMA 4.0.x rather than by independent feature work.
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 bayestools 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 bayestools or soilDBdata.
spEDM
Spatial causal discovery in R, one exposed method per release
sccore
Shared plumbing for the Kharchenko single-cell stack, updated once a year
rdataone
The R client for DataONE ships slow, correctness-focused maintenance
tall
A Shiny text-mining GUI grows into a full NLP workbench at 1.0.0
nflreadr
The nflverse data loader, whose releases are dictated by the NFL calendar and CRAN's archive policy
See all bayestools alternatives → · See all soilDBdata alternatives →
Recent activity from bayestools and soilDBdata
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 3mo agobayestoolsAdds automatic predictor standardization and type-based default priors
- 3mo agosoilDBdataMarshall Islands FY26 gSSURGO dataset added
- 8mo agobayestoolsBayesTools 0.2.23
- 8mo agobayestoolsBayesTools 0.2.22
- 11mo agobayestoolsBayesTools 0.2.21
- 1y agobayestoolsBayesTools 0.2.20
- 1y agobayestoolsBayesTools 0.2.19
- 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 bayestools and soilDBdata?
They serve adjacent needs but don't currently overlap on shipped themes. bayestools 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 bayestools better than soilDBdata?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. bayestools 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 bayestools?
Top bayestools alternatives in Analytics are ranked by recent ship velocity. Browse the "bayestools alternatives" section above for the current picks, or visit /alternatives/bayestools 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.