Repository navigation
Feature types and explainability #220
Replies: 4 comments 5 replies
|
|
Thank you for the quick answer! 3- No. I am evaluating the autoML-ness of many solutions and regarding their explainability I found out that they all use SHAP values to explain predictions. |
|
Hello, Yes. From my point of view, autoML solutions should definetely be able to explain their outputs, especially when used in critical applications: Today, most of the existing solutions (Google autoML tables, Prevision.io, H2O, etc) use shapley values which are not very trustworthy. Moreover, what I think should be provided to the user is: 1) a global interpretation (for example, by providing him/her with a feature importance plot) and 2) a local interpretation (by computing the importance of each feature in every prediction). Cheers Yassine |
|
Hi Yasslight90 and Kevin (@kevball2), Thank you for your insightful comments. There are several related TODOs included in our roadmap:
Thank you! |
Uh oh!
There was an error while loading. Please reload this page.
Hi there,
I have three questions:
1- What feature types does FLAML support? I am sure it supports at least numerical and categorical features. Any other types?
2- Is it possible to force the type for a given feature?
3- Does FLAML provide an explanation for predictions? I am thinking of shap values for example.
Thank you so much
Yassine - Data scientist
All reactions