n2kanalysis
n2kanalysis has spent eight years wiring INLA models to an S3 bucket.
Comparison · Analytics
icesSAG vs treeshap
A side-by-side editorial comparison of icesSAG and treeshap — release velocity, themes, recent moves, and the top alternatives to consider.
icesSAG vs treeshap: at a glance
What is icesSAG?
The ICES stock assessment client took upload away in 2024 and spent two years giving it back.
icesSAG is the R client for the ICES Stock Assessment Graphs database, used by fisheries scientists to retrieve and publish stock assessment summaries and figures. The 1.5.0 release repointed every function at a new API, replaced token authentication with JWT via icesConnect, and dropped file upload entirely. Upload returned in 1.6.2, now routing through icesDatsu to check file format and validate data before submission.
What is treeshap?
treeshap keeps widening its tree-model coverage while the SHAP math stays put.
treeshap computes exact SHAP values for tree ensembles in R, reaching each modelling framework through a per-framework unify() adapter. Since returning to CRAN in 2023 it has added GPBoost, ranger survival forests and multi-output models to that adapter layer. Four releases in three years, each dominated by adapter work contributed by users of one specific framework.
icesSAG vs treeshap: editorial side-by-side
icesSAG
0.0ANALYTICS
The ICES stock assessment client took upload away in 2024 and spent two years giving it back.
◆ Current state
icesSAG is the R client for the ICES Stock Assessment Graphs database, used by fisheries scientists to retrieve and publish stock assessment summaries and figures. The 1.5.0 release repointed every function at a new API, replaced token authentication with JWT via icesConnect, and dropped file upload entirely. Upload returned in 1.6.2, now routing through icesDatsu to check file format and validate data before submission.
◆ Where it's heading
The package is consolidating onto the shared ices-tools stack rather than carrying its own machinery — authentication moved to icesConnect, validation to icesDatsu, and the icesVocab dependency was dropped once it was no longer needed. Alongside that, redundant graph functions were deprecated and caching was added to reduce load on the server. Releases are infrequent and driven by upstream API changes.
◆ Prediction
Expect the next release to follow whatever the ICES service or the sibling ices-tools packages change next, rather than introducing new analysis capability of its own.
treeshap
0.0ANALYTICS
treeshap keeps widening its tree-model coverage while the SHAP math stays put.
◆ Current state
treeshap computes exact SHAP values for tree ensembles in R, reaching each modelling framework through a per-framework unify() adapter. Since returning to CRAN in 2023 it has added GPBoost, ranger survival forests and multi-output models to that adapter layer. Four releases in three years, each dominated by adapter work contributed by users of one specific framework.
◆ Where it's heading
The direction is breadth of model support rather than new explanation methods: every release since the first CRAN submission adds or repairs a unify() backend. Maintenance is community-driven, with named contributors fixing the framework they personally use. Nothing in these entries points at work on the SHAP algorithms themselves.
◆ Prediction
Expect the next release to add or repair another unify() adapter as a contributor brings their own framework, rather than to change how explanations are computed.
Alternatives to icesSAG and treeshap
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 icesSAG or treeshap.
n1qn1c
A Fortran-descended optimizer got thread-safe, then found two flags that never worked.
ggstatsplot
ggstatsplot reached 1.0 by adding tests, having outsourced its statistics years ago.
collapse
collapse got a JSS paper and a 7x fmean speedup in the same release.
gtsummary
gtsummary is quietly rebuilding itself around analysis results data, one table verb at a time.
broadcast
broadcast is filling in NumPy-style array broadcasting for R, operator by operator.
See all icesSAG alternatives → · See all treeshap alternatives →
Recent activity from icesSAG and treeshap
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
- 3mo agotreeshapGPBoost support lands; xgboost adapter repaired
- 3mo agoicesSAGStock upload restored with pre-submission validation
- 1y agoicesSAGEvery function repointed at a new API, with JWT auth ⚡
- 2y agotreeshapFixes broken lightgbm.unify examples
- 2y agotreeshapMulti-output model explanations added
- 2y agotreeshapFirst CRAN release consolidates the unify() adapters ⚡
- 6y agoicesSAGlocal release 1.3-5
Frequently asked questions
What is the difference between icesSAG and treeshap?
They serve adjacent needs but don't currently overlap on shipped themes. icesSAG and treeshap 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 icesSAG better than treeshap?
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. icesSAG and treeshap 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 icesSAG?
Top icesSAG alternatives in Analytics are ranked by recent ship velocity. Browse the "icesSAG alternatives" section above for the current picks, or visit /alternatives/icessag for the full list with editorial commentary on each.
What are the best alternatives to treeshap?
Top treeshap alternatives in Analytics are ranked by recent ship velocity. Browse the "treeshap alternatives" section above for the current picks, or visit /alternatives/treeshap for the full list with editorial commentary on each.