Chord
Chord's assistant can now write to the team's knowledge base, not just read from it.
A side-by-side editorial comparison of kernelshap and lpjmlkit — release velocity, themes, recent moves, and the top alternatives to consider.
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.
The LPJmL toolkit finally reads NetCDF, closing a gap against the format its field uses.
lpjmlkit is the R toolkit for running the LPJmL dynamic global vegetation model and reading its output. The 1.8.0 release adds direct NetCDF reading, either straight or via .nc.json metafiles, alongside the package's own binary formats. Before that, 1.7.3 sped up read_io(), reworked the LPJmLGridData implementation and added reservoir input support. Releases are infrequent, roughly one every 12 to 18 months.
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.
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.
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.
lpjmlkit is the R toolkit for running the LPJmL dynamic global vegetation model and reading its output. The 1.8.0 release adds direct NetCDF reading, either straight or via .nc.json metafiles, alongside the package's own binary formats. Before that, 1.7.3 sped up read_io(), reworked the LPJmLGridData implementation and added reservoir input support. Releases are infrequent, roughly one every 12 to 18 months.
The work concentrates on the I/O layer rather than the modeling interface, and it is moving toward the formats the wider earth-system community already exchanges. The gap between 1.7.3 and 1.8.0 is over a year, so this is a research-group package released when the science requires it, not on a schedule. The changelog itself is thin — several entries are merge-commit text or CRAN resubmissions.
Further I/O breadth is the likeliest direction now that NetCDF is supported, though the entries give no schedule; the release cadence has not been regular enough to predict timing.
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 kernelshap or lpjmlkit.
Chord's assistant can now write to the team's knowledge base, not just read from it.
tidytransit tracks the GTFS spec as it grows, one reader and one router feature at a time.
A tiny grid renderer for oblique-projection cubes, complete since its first release.
BioCro swapped an unstable iteration for real root finders, changing what its crop models compute.
redist keeps rewriting the sampler underneath a district-drawing API it has held stable since 4.0.
epiflows has shipped four releases in eight years, none of which changed the code.
See all kernelshap alternatives → · See all lpjmlkit alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. kernelshap and lpjmlkit are shipping at a similar cadence (velocity 0.0 vs 0.0, both within Sparkpulse's "active" band). 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. kernelshap and lpjmlkit are shipping at a similar cadence (velocity 0.0 vs 0.0, both within Sparkpulse's "active" band). For your specific use case, the alternatives sections above list other Analytics products to evaluate alongside.
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.
Top lpjmlkit alternatives in Analytics are ranked by recent ship velocity. Browse the "lpjmlkit alternatives" section above for the current picks, or visit /alternatives/lpjmlkit-r for the full list with editorial commentary on each.