lstar
A single-cell data store commits to Zarr v3 and range-readable hosting across four language surfaces
Comparison · Analytics
medrobust vs soilDBdata
A side-by-side editorial comparison of medrobust and soilDBdata — release velocity, themes, recent moves, and the top alternatives to consider.
Shared themes:r package
medrobust vs soilDBdata: at a glance
What is medrobust?
medrobust made its partial-identification bounds usable by giving them confidence intervals.
medrobust computes partial-identification bounds for mediation effects when exposure or mediator is differentially misclassified, part of the Data-Wise mediationverse. Its 0.2.0 release corrected three estimator defects against population oracles and added Imbens-Manski confidence intervals for the bounds; the two releases since have paired each identification path with a real public-domain dataset and a worked vignette. CRAN is deferred, with distribution through GitHub and r-universe.
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.
medrobust vs soilDBdata: editorial side-by-side
medrobust
0.0ANALYTICS
medrobust made its partial-identification bounds usable by giving them confidence intervals.
◆ Current state
medrobust computes partial-identification bounds for mediation effects when exposure or mediator is differentially misclassified, part of the Data-Wise mediationverse. Its 0.2.0 release corrected three estimator defects against population oracles and added Imbens-Manski confidence intervals for the bounds; the two releases since have paired each identification path with a real public-domain dataset and a worked vignette. CRAN is deferred, with distribution through GitHub and r-universe.
◆ Where it's heading
The pattern is deliberate and symmetric: 0.3.0 shipped the mediator-side example on NCHS natality data, 0.4.0 its exposure-side mirror on NHANES, each demonstrating what the bounds do when reporting accuracy is allowed to depend on the outcome. Alongside that runs a consistent concern with failing usefully rather than loudly — bound_ne() returns NA bounds with a machine-readable reason and a typed condition instead of aborting, so a simulation replicate is recorded rather than lost, and non-finite endpoint standard errors produce a documented NA rather than a silent one. That is a package expecting to be run thousands of times inside someone else's loop.
◆ Prediction
Both identification paths now have a dataset, a vignette and interval coverage, so the next release is most likely the deferred CRAN submission rather than new methodology.
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 medrobust 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 medrobust or soilDBdata.
quanteda
Text analysis in R keeps optimising its token internals — and builds a path out to torch
moderndive
The ModernDive teaching package learns to render inside the browser that runs its own textbook
glmbayes
A GPU-accelerated Bayesian GLM package buys its way into the standard R Bayesian toolchain
hydroloom
USGS puts a type system over its river network toolkit so errors surface at dispatch
chromConverter
The chromatography file-format translator keeps absorbing vendor formats one release at a time
See all medrobust alternatives → · See all soilDBdata alternatives →
Recent activity from medrobust and soilDBdata
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 2mo agomedrobustNHANES exposure-side misclassification example dataset
- 2mo agomedrobustNatality example dataset; bounds degrade instead of aborting
- 2mo agomedrobustBounds corrected against oracles; Imbens-Manski intervals added ⚡
- 3mo agosoilDBdataMarshall Islands FY26 gSSURGO dataset added
- 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 medrobust and soilDBdata?
Both compete on the same themes — r package — within Analytics. medrobust 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 medrobust better than soilDBdata?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. medrobust 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 medrobust?
Top medrobust alternatives in Analytics are ranked by recent ship velocity. Browse the "medrobust alternatives" section above for the current picks, or visit /alternatives/medrobust 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.