OHPL
A 2017 chemometrics method frozen in place, visited only when CRAN changes its documentation rules.
A side-by-side editorial comparison of bpbounds and clinify — release velocity, themes, recent moves, and the top alternatives to consider.
bpbounds found the same swapped-cell bug twice and clamped its bounds back into range
bpbounds computes nonparametric Balke-Pearl bounds on the average causal effect from instrumental variable data, in the bivariate and trivariate cases. After years of pure packaging maintenance, the two 2026 releases are analytical corrections. Bounds on intervention probabilities are now clamped to [0, 1] so derived causal risk ratio bounds cannot fall outside their feasible range, and a cell-ordering error in the trivariate three-category instrument path has been repaired.
Clinical-table typesetting for R, closing the gap between R output and regulatory Word documents
clinify renders clinical trial tables into Word documents through {officer}, aiming at the layout conventions regulatory submissions expect. 0.4.0 is the current CRAN release and folds in an unreleased 0.3.1. The recent work is almost entirely about header and spacing control: which adjacent header cells merge, where the rule under a spanner starts and stops, and how much vertical space sits above, below and between header rows and the table body.
bpbounds computes nonparametric Balke-Pearl bounds on the average causal effect from instrumental variable data, in the bivariate and trivariate cases. After years of pure packaging maintenance, the two 2026 releases are analytical corrections. Bounds on intervention probabilities are now clamped to [0, 1] so derived causal risk ratio bounds cannot fall outside their feasible range, and a cell-ordering error in the trivariate three-category instrument path has been repaired.
The direction is toward agreement with the reference Stata implementation and away from silently wrong output. The clamping change is described as matching the same fix in the Stata package, which suggests the two implementations are being reconciled rather than developed independently. The cell-ordering defect is the more instructive one: it was fixed in the calculation function in 0.1.7 and then again in the constraint matrix in 0.1.8, meaning the same x=0,y=1 / x=1,y=0 swap had been written in two places.
Since the recent fixes came from an external contributor's report and both touched the trivariate three-category path, the untested corners of that path are where further corrections would surface — but the release notes give no roadmap beyond parity with the Stata package.
clinify renders clinical trial tables into Word documents through {officer}, aiming at the layout conventions regulatory submissions expect. 0.4.0 is the current CRAN release and folds in an unreleased 0.3.1. The recent work is almost entirely about header and spacing control: which adjacent header cells merge, where the rule under a spanner starts and stops, and how much vertical space sits above, below and between header rows and the table body.
The package is moving from producing a correct table toward producing one that survives an organisation's house style. 0.4.0's additions are all written to hold under a customised `clinify_table_default()` — `clin_spanner_rule()` draws after the default styling function so it persists when a house style clears the borders it started from, and takes an `officer::fp_border()` or `FALSE` so a style can decline the rule entirely. The earlier 0.3.0 line did the structural work, introducing `clindoc()` document objects that accept multiple tables plus automatic pagination.
Expect continued refinement of layout primitives that follow the table rather than fixed column numbers, since both new 0.4.0 functions were built specifically to track spanners and headers as a layout changes. The entries do not indicate a move beyond Word output.
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 bpbounds or clinify.
A 2017 chemometrics method frozen in place, visited only when CRAN changes its documentation rules.
A fast dplyr stand-in that keeps finding new places to skip work entirely.
Belgium's invasive-species indicator toolkit is in steady refinement, one plotting edge case at a time.
The ICES stock assessment client took upload away in 2024 and spent two years giving it back.
A discrete global grid generator grew cell traversal and became a usable spatial index.
Community ecology's standard toolkit is retiring the functions a generation of scripts was built on.
See all bpbounds alternatives → · See all clinify alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. 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 bpbounds alternatives in Analytics are ranked by recent ship velocity. Browse the "bpbounds alternatives" section above for the current picks, or visit /alternatives/bpbounds for the full list with editorial commentary on each.
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-r for the full list with editorial commentary on each.