soilDBdata
soilDBdata exists so soilDB's tests can run without a NASIS connection.
A side-by-side editorial comparison of rmediation and Rho — release velocity, themes, recent moves, and the top alternatives to consider.
RMediation shipped a three-normal CDF, then found it was silently wrong.
RMediation is a long-standing CRAN package for confidence intervals on mediated effects, now built on an S7 class hierarchy. Over eight weeks it added ProductNormal3 for serial indirect effects of the form a1*a2*b, folded the engine into the existing pprodnormal naming family, and then replaced that engine outright after finding it returned wrong probabilities without warning. The dev branch is at 1.7.0; CRAN still serves 1.6.1.
Rho's release machinery is now more rigorous than the product it ships.
Rho is an R IDE in open prerelease, and its public feed is almost entirely release engineering. The one substantive entry, 0.4.0-dev.39, described capability-based model routing across providers and durable project-scoped agent conversations with per-file Apply/Undo. Everything around it is build candidates and acceptance targets, each gated behind an explicit acceptance record that fails closed.
RMediation is a long-standing CRAN package for confidence intervals on mediated effects, now built on an S7 class hierarchy. Over eight weeks it added ProductNormal3 for serial indirect effects of the form a1*a2*b, folded the engine into the existing pprodnormal naming family, and then replaced that engine outright after finding it returned wrong probabilities without warning. The dev branch is at 1.7.0; CRAN still serves 1.6.1.
The package is moving from a hand-rolled numerical layer to one that checks itself: the new default integrator escalates its node count until successive rules agree, warns when it hits the cap instead of returning a number, and exposes a diagnostics argument for the convergence estimate. The correctness fix went to dev ahead of the CRAN window rather than being held for it, which suggests wrong-answer bugs are treated as release-blocking regardless of cadence. Serial mediation is where the new surface area is concentrated.
1.7.0 exists specifically to land before CRAN's 2026-08-21 update window, so the next move is a CRAN submission promoting it to main; whether hcubature survives past that as a cross-check option is the open question.
Rho is an R IDE in open prerelease, and its public feed is almost entirely release engineering. The one substantive entry, 0.4.0-dev.39, described capability-based model routing across providers and durable project-scoped agent conversations with per-file Apply/Undo. Everything around it is build candidates and acceptance targets, each gated behind an explicit acceptance record that fails closed.
The project is building an agentic R IDE but publishing like a regulated release process: signed evidence, CONDITIONAL_GO records, checksums bound to exact commits, limitations named out loud rather than buried. dev.41 exists solely to rehearse the native updater across Windows and macOS, which is the last piece of distribution infrastructure between a dev train and something installable by people who won't build from source. Feature work and shipping work are advancing on separate tracks.
The updater acceptance target points at a 0.4.0 line that can update itself, so the next entry that matters is either dev.40's real publication or the first build not labelled evaluation-only. Whether Windows signing moves off the SignPath trial certificate is the open question these entries leave unanswered.
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 rmediation or Rho.
soilDBdata exists so soilDB's tests can run without a NASIS connection.
collinear has broken its API twice to stop making the user pick thresholds.
nert put fourteen TERN datasets behind one dispatcher and called it stable.
scTypeEval judges single-cell annotations without needing a ground truth to judge them against.
medrobust made its partial-identification bounds usable by giving them confidence intervals.
probmed went from one probabilistic effect size to a family of them in sixteen days.
See all rmediation alternatives → · See all Rho alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. Rho is currently shipping more aggressively (velocity 6.3 vs 3.8), with 1 editorial sparks in the last 30 days against 1. 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. Rho is currently shipping more aggressively (velocity 6.3 vs 3.8), with 1 editorial sparks in the last 30 days against 1. For your specific use case, the alternatives sections above list other Analytics products to evaluate alongside.
Top rmediation alternatives in Analytics are ranked by recent ship velocity. Browse the "rmediation alternatives" section above for the current picks, or visit /alternatives/rmediation for the full list with editorial commentary on each.
Top Rho alternatives in Analytics are ranked by recent ship velocity. Browse the "Rho alternatives" section above for the current picks, or visit /alternatives/yulab-smu-rho for the full list with editorial commentary on each.