soilDBdata
soilDBdata exists so soilDB's tests can run without a NASIS connection.
A side-by-side editorial comparison of clinify and Rho — release velocity, themes, recent moves, and the top alternatives to consider.
clinify is closing the gap between flextable defaults and regulatory table specs.
clinify shapes clinical trial tables into the Word deliverables regulatory submissions require, wrapping flextable and officer. Version 0.4.0 is on CRAN and is almost entirely typographic control: spanner rules that follow the header instead of hard-coded column numbers, header padding named for where the space actually sits, and explicit row pitch. The structural release was 0.3.0, which introduced document objects and broke three APIs to get there.
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.
clinify shapes clinical trial tables into the Word deliverables regulatory submissions require, wrapping flextable and officer. Version 0.4.0 is on CRAN and is almost entirely typographic control: spanner rules that follow the header instead of hard-coded column numbers, header padding named for where the space actually sits, and explicit row pitch. The structural release was 0.3.0, which introduced document objects and broke three APIs to get there.
The package is working through the places where flextable's defaults and a statistical reporting spec disagree, and the notes are unusually explicit about why each default is wrong — a cell's bottom border draws below its bottom padding, so space under a header moves the rule rather than opening a gap beneath it; flextable leaves rows at a nominal quarter inch when the spec names an exact pitch. Each addition is built to survive an organisation's own clinify_table_default() rather than assuming clinify's styling runs last.
Header, spanner and row-pitch control all landed together, so the next gap in the same series is title and footnote geometry — the remaining page furniture that 0.3.0's two-part split left roughly specified.
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 clinify 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.
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 2.5), with 1 editorial sparks in the last 30 days against 0. 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 2.5), with 1 editorial sparks in the last 30 days against 0. For your specific use case, the alternatives sections above list other Analytics products to evaluate alongside.
Top clinify alternatives in Analytics are ranked by recent ship velocity. Browse the "clinify alternatives" section above for the current picks, or visit /alternatives/clinify 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.