soilDBdata
soilDBdata exists so soilDB's tests can run without a NASIS connection.
A side-by-side editorial comparison of clinify and collinear — 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.
collinear has broken its API twice to stop making the user pick thresholds.
collinear removes multicollinearity from predictor sets through pairwise correlation and VIF filtering, with a preference order deciding which variable survives each conflict. Two major versions in thirteen months each rewrote the interface: 2.0.0 extended every function to any combination of categorical and numeric responses and predictors, and 3.0.0 moved to multiple responses, restructured the output into classed objects, and made both filtering thresholds adaptive by default. Version 3.0.1 is the first release since that is purely repair.
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.
collinear removes multicollinearity from predictor sets through pairwise correlation and VIF filtering, with a preference order deciding which variable survives each conflict. Two major versions in thirteen months each rewrote the interface: 2.0.0 extended every function to any combination of categorical and numeric responses and predictors, and 3.0.0 moved to multiple responses, restructured the output into classed objects, and made both filtering thresholds adaptive by default. Version 3.0.1 is the first release since that is purely repair.
The through-line is removing decisions the user was never well placed to make. Preference-order functions were renamed twice — first onto a metric-and-model scheme in 2.0.0, then onto a response-type scheme in 3.0.0 — and f_auto() picks one when none is given; target encoding went from automatic to opt-in; max_cor and max_vif now default to NULL and trigger a data-driven threshold derived from the 75th percentile of pairwise correlations through a sigmoid and a fitted correlation-to-VIF mapping. Each change is defensible and each one broke callers, which is the cost of this approach.
3.0.1 moved the example datasets out into a separate spatialData package and fixed four crashes rather than adding anything, so the next release is most likely more consolidation on the 3.0 surface than a fourth interface.
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 collinear.
soilDBdata exists so soilDB's tests can run without a NASIS connection.
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.
fluxnet keeps swapping its own plumbing — first a Python downloader, now a DuckDB backend.
See all clinify alternatives → · See all collinear alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — r package — within Analytics. clinify is currently shipping more aggressively (velocity 2.5 vs 0.0), with 0 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. clinify is currently shipping more aggressively (velocity 2.5 vs 0.0), with 0 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 collinear alternatives in Analytics are ranked by recent ship velocity. Browse the "collinear alternatives" section above for the current picks, or visit /alternatives/collinear for the full list with editorial commentary on each.