CRAN release 0.9.6

Documentation

• Fixed wrong link vignette #158.

CRAN release 0.9.5

User-visible changes

• sv_waterfall() and sv_force(): The x label has been changed from "SHAP value" to "Prediction".

Documentation

• Add vignette for Tidymodels.
• Update vignettes.
• Update README.

CRAN release 0.9.4

API improvements

• Support both XGBoost 1.x.x as well as XGBoost 2.x.x, implemented in #144.

Other improvements

• New argument sort_features = TRUE in sv_importance() and sv_interaction(). Set to FALSE to show the features as they appear in your SHAP matrix. In that case, the plots will show the first max_display features, not the most important features. Implements #137.

Bug fixes

• shapviz.xgboost() would fail if a single row is passed. This has been fixed in #142. Thanks @sebsilas for reporting.

CRAN release 0.9.3

sv_dependence(): Control over automatic color feature selection

How is the color feature selected, anyway?

If no SHAP interaction values are available, by default, the color feature v' is selected by the heuristic potential_interaction(), which works as follows:

1. If the feature v (the on the x-axis) is numeric, it is binned into nbins bins.
2. Per bin, the SHAP values of v are regressed onto v' and the R-squared is calculated. Rows with missing v' are discarded.
3. The R-squared are averaged over bins, weighted by the number of non-missing v' values.

This measures how much variability in the SHAP values of v is explained by v', after accounting for v.

We have introduced four parameters to control the heuristic. Their defaults are in line with the old behaviour.

• nbin = NULL: Into how many quantile bins should a numeric v be binned? The default NULL equals the smaller of $n/20$ and $\sqrt n$ (rounded up), where $n$ is the sample size.
• color_num Should color features be converted to numeric, even if they are factors/characters? Default is TRUE.
• scale = FALSE: Should R-squared be multiplied with the sample variance of
  within-bin SHAP values? If TRUE, bins with stronger vertical scatter will get higher weight. The default is FALSE.
• adjusted = FALSE: Should adjusted R-squared be calculated?

If SHAP interaction values are available, these parameters have no effect. In sv_dependence() they are called ih_nbin etc.

This partly implements the ideas in #119 of Roel Verbelen, thanks a lot for your patient explanations!

Further plans?

We will continue to experiment with the defaults, which might change in the future. A good alternative to the current (naive) defaults could be:

• nbins = 7: Smaller than now to not overfit too strongly with factor/character color features.
• color_num = FALSE: To not naively integer encode factors/characters.
• scale = TRUE: To account for non-equal spread in bins.
• adjusted = TRUE: To not put too much weight on factors with many categories.

Other user-visible changes

• sv_dependence(): If color_var = "auto" (default) and no color feature seems to be relevant (SHAP interaction is NULL, or heuristic returns no positive value), there won't be any color scale. Furthermore, in some edge cases, a different
  color feature might be selected.
• mshapviz() objects can now be rowbinded via rbind() or +. Implemented by @jmaspons in #110.
• mshapviz() is more strict when combining multiple "shapviz" objects. These now need to have identical column names, see #114.

Small changes

• The README is shorter and easier.
• Updated vignettes.
• print.shapviz() now shows top two rows of SHAP matrix.
• Re-activate all unit tests.
• Setting nthread = 1 in all calls to xgb.DMatrix() as suggested by @jmaspons in #109.
• Added "How to contribute" to README.
• permshap() connector is now part of {kerneshap} #122.

Bug fixes

• sv_dependence2D(): In case add_vars are passed, x and/or y are removed from it in order to not use any variable twice. #116.
• split.shapviz() now drops empty levels. They launched an error because empty "shapviz" objects are currently not supported. #117, #118

CRAN release 0.9.2

User-visible changes

• sv_importance() of a "mshapviz" object now returns a dodged barplot instead of separate barplots via {patchwork}. Use the new argument bar_type to switch to a stacked barplot (bar_type = "stack"), to "facets" (via {ggplot2}), or "separate" for the old behaviour.

New features

• Added connector to permshap, a package calculating permutation SHAP values for regression and (probabilistic) classification.

Other changes

• Revised vignette on "mshapviz".
• Commenting out most unit tests as they would not pass timings measured on Debian.

CRAN release 0.9.1

New features

• dimnames.shapviz() has received a replacement method. You can thus change the column names of SHAP matrix and feature data (as well as SHAP interactions) by colnames(x) <- ..., see #98

Maintenance

• Fix for #100 (package_version() applied to numeric value will be deprecated in the future)

CRAN release 0.9.0

New features

• New plot function sv_dependence2D(): x and y coordinates are two features, while their summed SHAP values are shown on the color scale. If interaction = TRUE, SHAP interaction values are shown on the color scale instead. The function is vectorized in x and/or y. This visualization is especially useful for models with geographic components.
• split(x, f) splits a "shapviz" object x into a "mshapviz" object.

Documentation

• Slight improvements in help/docu.
• New vignette on models with geographic components.
• Added a fantastic house price dataset with about 14,000 houses sold in Miami-Date County, thanks Steven C. Bourassa.

API improvements

• "mshapviz" object created from multioutput "kernelshap" object retains names.

CRAN release 0.8.0

API improvement

• For (upcoming) {fastshap} version >0.0.7, fastshap::explain() offers the option shap_only. To conveniently construct the "shapviz" object, use shapviz(fastshap::explain(..., shap_only = FALSE)). This not only passes the SHAP matrix but also the feature data and the baseline. Thanks, Brandon @bgreenwell !

Documentation

• Better help files
• Switched from "import ggplot2" to "ggplot2::function" code style
• Vignette "Multiple 'shapviz' objects": Fixed mistake in Random Forest + Kernel SHAP example

CRAN release 0.7.0

Milestone: Working with multiple 'shapviz' objects

Sometimes, you will find it necessary to work with several "shapviz" objects at the same time:

• To visualize SHAP values of a multiclass or multi-output model.
• To compare SHAP plots of different models.
• To compare SHAP plots between subgroups.

To simplify the workflow, {shapviz} introduces the "mshapviz" object ("m" like "multi"). You can create it in different ways:

• Use shapviz() on multiclass XGBoost or LightGBM models.
• Use shapviz() on "kernelshap" objects created from multiclass/multioutput models.
• Use c(Mod_1 = s1, Mod_2 = s2, ...) on "shapviz" objects s1, s2, ...
• Or mshapviz(list(Mod_1 = s1, Mod_2 = s2, ...))

The sv_*() functions use the {patchwork} package to glue the individual plots together.

See the new vignette for more info and specific examples.

Other new features

• sv_dependence() now allows multiple v and/or color_var to be plotted (glued via {patchwork}).
• {DALEX}: Support for "predict_parts" objects from {DALEX}, thanks to Adrian Stando.
• Aggregated SHAP values: The argument row_id of sv_waterfall() and sv_force() now also allows a vector of integers or a logical vector. If more than one row is selected, SHAP values and predictions are averaged before plotting (aggregated SHAP values in {DALEX}).
• Row bind: "shapviz" objects x1, x2 can now be concatenated in rowwise manner using x1 + x2 or rbind(x1, x2), again thanks to Adrian.
• colnames(): "shapviz" objects x have received a dimnames() function, so you can now, e.g., use colnames(x) to see the feature names.
• Subsetting: "shapviz" x can now be subsetted using x[cond, features].

Maintenance

• We have a new contributor: Adrian Stando - welcome on the SHAP board.
• To be close to my sister package {kernelshap}, I have moved to https://github.com/ModelOriented/shapviz
• Webpage created with "pgkdown"
• New dependency: {patchwork}

Other changes

• Color guides are closer to the plot area. This affects sv_dependence(), sv_importance(kind="bee"), and sv_interaction().
• The lengthy y axis title "SHAP interaction value" in sv_dependence() has been shortened to "SHAP interaction".
• As announced, the argument show_other of sv_importance() has been removed.
• Slightly less picky checks on S_inter.
• print.shapviz() is much more compact, use summary.shapviz() for more info.

Bug fixes

• sv_waterfall(): Using order_fun() would not work as expected with max_display. This has been fixed.
• sv_dependence(): Passing viridis_args = NULL would hide the color guide title. This has been fixed. But please pass viridis_args = list() instead.

CRAN release 0.6.0

Change in defaults

• sv_dependence() now uses color_var = "auto" instead of color_var = NULL.
• sv_dependence() now uses "SHAP value" as y label (instead of the more verbose "SHAP value of [feature]").