← Back to home
Comparison · Analytics

soilDBdata vs susier

A side-by-side editorial comparison of soilDBdata and susier — release velocity, themes, recent moves, and the top alternatives to consider.

soilDBdata vs susier: at a glance

FeaturesoilDBdatasusier
SectorAnalyticsAnalytics
Velocity score0.00.0
Sparks · 30d00
Top themessoil data, test fixtures, nasis, data packager-package, statistical-genetics, fine-mapping, cpp-bindings
Last editorial update3h ago54m ago
WebsiteVisit →Visit →

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.

Read the full soilDBdata trajectory →

What is susier?

Fine-mapping workhorse susieR spends its releases hunting null-effect trimming bugs

susieR implements the Sum of Single Effects regression model for variable selection and fine-mapping, widely used in statistical genetics. The recent releases are a tight run of correctness work concentrated in one area: null effect trimming. Version 0.15.55 fixed trimming under the Servin-Stephens residual variance method, 0.15.56 fixed it again for non-uniform prior weights fourteen minutes later, 0.15.57 corrected an ELBO null space term for RSS with X and a matrix symmetry check, and 0.15.58 addressed an alpha0/beta0 issue. Version 0.16.0 migrates the C++ bindings from Rcpp to cpp11 with cpp11armadillo.

Read the full susier trajectory →

soilDBdata vs susier: editorial side-by-side

S
soilDBdata
ANALYTICS
0.0

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.

S
susier
ANALYTICS
0.0

Fine-mapping workhorse susieR spends its releases hunting null-effect trimming bugs

◆ Current state

susieR implements the Sum of Single Effects regression model for variable selection and fine-mapping, widely used in statistical genetics. The recent releases are a tight run of correctness work concentrated in one area: null effect trimming. Version 0.15.55 fixed trimming under the Servin-Stephens residual variance method, 0.15.56 fixed it again for non-uniform prior weights fourteen minutes later, 0.15.57 corrected an ELBO null space term for RSS with X and a matrix symmetry check, and 0.15.58 addressed an alpha0/beta0 issue. Version 0.16.0 migrates the C++ bindings from Rcpp to cpp11 with cpp11armadillo.

◆ Where it's heading

The version-number churn understates how narrow this work is — four consecutive releases touching the same trimming and residual-variance machinery suggests one area where the implementation and the intended behavior had drifted apart. The 0.16.0 binding migration is the only structural change, and it is invisible to users while mattering for build portability and long-term maintenance. Development is clearly active, with automated release tooling and dependency bumps flowing through the same stream.

◆ Prediction

With the binding migration just landed, near-term releases are likely to address fallout from it alongside continued fixes in the same trimming and residual-variance code.

Alternatives to soilDBdata and susier

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 soilDBdata or susier.

See all soilDBdata alternatives → · See all susier alternatives →

Recent activity from soilDBdata and susier

Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.

  1. 3mo agosoilDBdataMarshall Islands FY26 gSSURGO dataset added
  2. 3mo agosusierMigrates C++ bindings from Rcpp to cpp11 and cpp11armadillo
  3. 3mo agosusierFixes alpha0/beta0 handling under Servin-Stephens
  4. 4mo agosusierCorrects the null space ELBO term for RSS with X
  5. 5mo agosusierFixes null effect trimming with non-uniform prior weights
  6. 5mo agosusierFixes null effect trimming under Servin-Stephens estimation
  7. 1y agosoilDBdataMT663 fixtures refreshed for soilDB 2.8.3
  8. 1y agosoilDBdataNASIS purpose lists updated for siteothvegclass
  9. 4y agosoilDBdataSelected-set _View_1 tables enable SS=TRUE/FALSE testing
  10. 4y agosoilDBdataProof of concept: MT663 pedon and component .sqlite fixtures

Frequently asked questions

What is the difference between soilDBdata and susier?

They serve adjacent needs but don't currently overlap on shipped themes. soilDBdata and susier 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 soilDBdata better than susier?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. soilDBdata and susier 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 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.

What are the best alternatives to susier?

Top susier alternatives in Analytics are ranked by recent ship velocity. Browse the "susier alternatives" section above for the current picks, or visit /alternatives/susier for the full list with editorial commentary on each.