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 treeshap and watina — release velocity, themes, recent moves, and the top alternatives to consider.
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.
A groundwater database client that has started doing the domain analysis too
watina is the R interface to the Watina groundwater monitoring database, and its history is mostly about making data retrieval correct: filter depths guessed conservatively when missing, spatial masking, aggregation methods per observation well, and a long series of fixes to keep the lazy database queries working across dbplyr versions. The most recent release moves past retrieval into interpretation, adding ionic ratio calculation and a Van Wirdum diagram to plot chemistry data.
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.
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.
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.
watina is the R interface to the Watina groundwater monitoring database, and its history is mostly about making data retrieval correct: filter depths guessed conservatively when missing, spatial masking, aggregation methods per observation well, and a long series of fixes to keep the lazy database queries working across dbplyr versions. The most recent release moves past retrieval into interpretation, adding ionic ratio calculation and a Van Wirdum diagram to plot chemistry data.
The package is drifting from a database client toward a domain toolkit. Early releases fought the data layer — connection handling moved to inbodb, sorting semantics changed, defunct dbplyr calls worked around. Recent work assumes retrieval is solved and adds hydrochemical analysis on top, along with defensive handling for the physically impossible inputs that analysis exposes, such as zero conductivity in the warehouse.
Expect further chemistry analysis and plotting helpers rather than new retrieval functions, since that is where the newest release invested and where the accompanying vignette points.
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 treeshap or watina.
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 treeshap alternatives → · See all watina alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. treeshap and watina 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. treeshap and watina 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 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.
Top watina alternatives in Analytics are ranked by recent ship velocity. Browse the "watina alternatives" section above for the current picks, or visit /alternatives/watina-r for the full list with editorial commentary on each.