← Back to home
Comparison · Analytics

clinify vs kernelshap

A side-by-side editorial comparison of clinify and kernelshap — release velocity, themes, recent moves, and the top alternatives to consider.

clinify vs kernelshap: at a glance

Featureclinifykernelshap
SectorAnalyticsAnalytics
Velocity score2.50.0
Sparks · 30d00
Top themesclinical-trials, r-package, document-generation, table-formattingshap, model explainability, sampling algorithms, numerical correctness
Last editorial update1h ago46m ago
WebsiteVisit →Visit →

What is clinify?

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.

Read the full clinify trajectory →

What is kernelshap?

kernelshap makes permutation SHAP practical past eight features, then fixes the kernel weights it had wrong.

kernelshap computes model-agnostic SHAP values in R through Kernel SHAP, permutation SHAP and an exact additive explainer. Version 0.8.0 added a sampling permutation-SHAP algorithm with standard errors and early stopping, lifting the practical feature ceiling past what the exact method allows. Version 0.9.0 then corrected a bug in how kernel weights were computed — exact Kernel SHAP now agrees with exact permutation SHAP — and moved parallelism from foreach to doFuture.

Read the full kernelshap trajectory →

clinify vs kernelshap: editorial side-by-side

C
clinify
ANALYTICS
2.5

Clinical-table typesetting for R, closing the gap between R output and regulatory Word documents

◆ Current state

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.

◆ Where it's heading

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.

◆ Prediction

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.

K
kernelshap
ANALYTICS
0.0

kernelshap makes permutation SHAP practical past eight features, then fixes the kernel weights it had wrong.

◆ Current state

kernelshap computes model-agnostic SHAP values in R through Kernel SHAP, permutation SHAP and an exact additive explainer. Version 0.8.0 added a sampling permutation-SHAP algorithm with standard errors and early stopping, lifting the practical feature ceiling past what the exact method allows. Version 0.9.0 then corrected a bug in how kernel weights were computed — exact Kernel SHAP now agrees with exact permutation SHAP — and moved parallelism from foreach to doFuture.

◆ Where it's heading

Two concerns drive this package: making exact methods reach further, and being demonstrably right. The first shows in the additive explainer, the optional background dataset and the sampling permutation algorithm; the second in unit tests written against Python's shap, credited fixes from outside contributors, and a willingness to ship a correctness fix that changes numbers people have already published. Speed work runs continuously underneath — direct solves replacing the Moore-Penrose pseudo-inverse, roughly 10% less memory.

◆ Prediction

The 0.6.0 and 0.7.0 notes each promised a stable 1.0.0 that has not arrived; with the weighting bug fixed and parallelism reworked, a 1.0 release is the most plausible next step.

Alternatives to clinify and kernelshap

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 kernelshap.

See all clinify alternatives → · See all kernelshap alternatives →

Recent activity from clinify and kernelshap

Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.

  1. 13d agoclinifyFiner header merging, spanner rules and header padding
  2. 1y agokernelshapKernel weight bug fixed; parallelism moves to doFuture
  3. 1y agokernelshapSampling permutation SHAP with standard errors
  4. 1y agoclinifyclindoc document objects and automatic pagination
  5. 1y agokernelshapBackground data now optional; ranger survival support
  6. 2y agokernelshapFactor-valued predictions dropped
  7. 2y agokernelshapadditive_shap() explains additive models exactly
  8. 2y agokernelshapFaster on plain data.frames

Frequently asked questions

What is the difference between clinify and kernelshap?

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.

Is clinify better than kernelshap?

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.

What are the best alternatives to clinify?

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.

What are the best alternatives to kernelshap?

Top kernelshap alternatives in Analytics are ranked by recent ship velocity. Browse the "kernelshap alternatives" section above for the current picks, or visit /alternatives/kernelshap for the full list with editorial commentary on each.