You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello, While using model_survshap() for global interpretation with shaps, I found that this function seems to be unable to distinguish between continuous variables and categorical variables, which has caused my concern. Even though I added a list of categorical variables, is the calculation of shap values the same for different variables? This seems to change the order of importance of the variables.
My code can run, but the results seem unreliable. Previously unimportant variables such as categorical variables like sex seem to have become more important
The text was updated successfully, but these errors were encountered:
Hi @lzxcvn, where did you find the categorical_variables parameter?
In most cases, SHAP does not distinguish between continuous and categorical variables. It might be important when conditional imputation is used for feature marginalization (instead of the default marginal feature distribution). For details, refer to the shapr R package https://github.com/NorskRegnesentral/shapr, and the related research e.g. https://doi.org/10.1007/s10618-024-01016-z.
Moreover, KernelSHAP is an approximation algorithm that includes randomness, which can lead to changes in the order of importance of the variables.
Hello, While using model_survshap() for global interpretation with shaps, I found that this function seems to be unable to distinguish between continuous variables and categorical variables, which has caused my concern. Even though I added a list of categorical variables, is the calculation of shap values the same for different variables? This seems to change the order of importance of the variables.
My code can run, but the results seem unreliable. Previously unimportant variables such as categorical variables like sex seem to have become more important
The text was updated successfully, but these errors were encountered: