← Back to home
Comparison · Analytics

kernelshap vs NWCTrends

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

kernelshap vs NWCTrends: at a glance

FeaturekernelshapNWCTrends
SectorAnalyticsAnalytics
Velocity score0.00.0
Sparks · 30d00
Top themesshap, model explainability, sampling algorithms, numerical correctnessfisheries, state-space-models, reproducible-reporting, r-package
Last editorial update7h ago57m ago
WebsiteVisit →Visit →

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 →

What is NWCTrends?

The salmon status-review trend package, maintained one federal review cycle at a time

NWCTrends fits multivariate state-space trend models to Pacific salmon population data and generates the tables and figures used in NOAA Northwest Fisheries Science Center viability and status reviews. Its release history maps onto those review cycles rather than a development calendar: v1.0 carries the 2015 review code, v1.25 the 2020 review, v1.30 the changes since. The 2026 v1.31 is internal restructuring and a dependency swap.

Read the full NWCTrends trajectory →

kernelshap vs NWCTrends: editorial side-by-side

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.

N
NWCTrends
ANALYTICS
0.0

The salmon status-review trend package, maintained one federal review cycle at a time

◆ Current state

NWCTrends fits multivariate state-space trend models to Pacific salmon population data and generates the tables and figures used in NOAA Northwest Fisheries Science Center viability and status reviews. Its release history maps onto those review cycles rather than a development calendar: v1.0 carries the 2015 review code, v1.25 the 2020 review, v1.30 the changes since. The 2026 v1.31 is internal restructuring and a dependency swap.

◆ Where it's heading

Development is driven by reproducibility of a specific government reporting product, so most work goes into making the report generation configurable and the fitting assumptions explicit rather than into new modelling. The 2020 cycle removed hard-coded per-population hacks and made the fitting window an explicit argument; the 2023 cycle moved plot styling into package options and clarified how missing data and zeros are handled in the published tables.

◆ Prediction

The cadence suggests the next substantive release arrives with the next status review rather than before it, most likely continuing the move of report parameters out of function signatures and into structured configuration.

Alternatives to kernelshap and NWCTrends

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

See all kernelshap alternatives → · See all NWCTrends alternatives →

Recent activity from kernelshap and NWCTrends

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

  1. 7mo agoNWCTrendsReport params extracted to a list; gdata replaced with readxl
  2. 1y agokernelshapKernel weight bug fixed; parallelism moves to doFuture
  3. 1y agokernelshapSampling permutation SHAP with standard errors
  4. 1y agokernelshapBackground data now optional; ranger survival support
  5. 2y agokernelshapFactor-valued predictions dropped
  6. 2y agokernelshapadditive_shap() explains additive models exactly
  7. 2y agokernelshapFaster on plain data.frames
  8. 3y agoNWCTrendsPlot options move into package globals; figure data exported to CSV
  9. 5y agoNWCTrendsExplicit fitting window replaces implicit full-data fits
  10. 5y agoNWCTrendsInitial release packaging the 2015 status review code

Frequently asked questions

What is the difference between kernelshap and NWCTrends?

They serve adjacent needs but don't currently overlap on shipped themes. kernelshap and NWCTrends 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.

Is kernelshap better than NWCTrends?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. kernelshap and NWCTrends 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.

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.

What are the best alternatives to NWCTrends?

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