Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add prediction-level feature importances? #1144

Open
Vincent-Maladiere opened this issue Nov 18, 2024 · 2 comments
Open

Add prediction-level feature importances? #1144

Vincent-Maladiere opened this issue Nov 18, 2024 · 2 comments

Comments

@Vincent-Maladiere
Copy link
Member

Problem Description

For data scientists in the industry, explainability is crucial to build trust with other stakeholders. Marginal explainability with, e.g., permutation_importance helps, but stakeholders often ask for personalised, per-prediction feature importances, which help understand what stands out in a test sample for the model.

The two most popular librairies for this are LIME and SHAP, both having theoretical and practical pros and cons. Additionally, LIME is not maintained anymore, although fairly simple conceptually (fitting Ridge models while varying sample weights).

This raises several questions:

  1. Would having an easy way to get marginal and prediction-level feature importance make sense in the recipe or as a standalone helper in skrub?
  2. If we don't want extra dependancies, should we implement a simple version of prediction-level feat imp in skrub? @glemaitre mentioned one SLEP with a similar objective, IIUC
  3. We should probably do some benchmarking and litterature reading to choose a method which can be interpreted and explained in plain english, with clear documentation and guidelines on what can or cannot be said.

WDYT?

Feature Description

.

Alternative Solutions

.

Additional Context

.

@GaelVaroquaux
Copy link
Member

GaelVaroquaux commented Nov 18, 2024 via email

@Vincent-Maladiere
Copy link
Member Author

I agree that this raises the question of the scope, too. Skrub and the recipe already ease HP tuning, so it could be valuable for users to also facilitate model evaluation IMHO, with pragmatic guidelines. I'd also be happy to have it somewhere else, though.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants