-
-
Notifications
You must be signed in to change notification settings - Fork 26.3k
FEAT allow RFE(CV) be used with pemutation_importance
#32251
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
base: main
Are you sure you want to change the base?
Conversation
pemutation_importance
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the PR. This is very useful. Please indeed update the example and add a changelog entry.
EDIT: here are the instructions for the changelog entry: https://github.com/scikit-learn/scikit-learn/blob/main/doc/whats_new/upcoming_changes/README.md
This allows methods like :func:`permutation_importance` to extract the relevant features | ||
from its test set. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This allows methods like :func:`permutation_importance` to extract the relevant features | |
from its test set. | |
This allows methods like :func:`permutation_importance` and similar tools to | |
iteratively extract the previously selected features from a test set. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yeah I realized it was not very clear so I planned to change it to:
" This allows methods that need a test set, like :func:permutation_importance
, to know which
features of to use in their predictions."
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM besides the following:
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I found a small problem in the example + small suggestions for further improvement in the docstrings.
Also @ArturoAmorQ might be interested in reviewing this PR (the updated example in particular).
If `callable`, overrides the default feature importance getter. | ||
The callable is passed with the fitted estimator and it should | ||
return importance for each feature. | ||
return importance for each feature. When it accepts it, the callable is passed |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
return importance for each feature. When it accepts it, the callable is passed | |
return importance for each feature. When it accepts it, the callable is passed |
return importance for each feature. | ||
return importance for each feature. When it accepts it, the callable is passed | ||
`feature_indices` which stores the index of the features in the full dataset | ||
that have not been eliminated yet. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
that have not been eliminated yet. | |
that have not yet been eliminated in previous iterations. |
return importance for each feature. | ||
return importance for each feature. When it accepts it, the callable is passed | ||
`feature_indices` which stores the index of the features in the full dataset | ||
that have not been eliminated yet. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
that have not been eliminated yet. | |
that have not yet been eliminated in previous iterations. |
shown at the end of | ||
:ref:`sphx_glr_auto_examples_feature_selection_plot_rfe_with_cross_validation.py`. | ||
.. versionadded:: 0.24 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think we should add a .. versionchanged:: 1.8
and mention that support for passing feature_indices
to the callable when part of its signature.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
And similarly for the docstring of the other class.
n_classes=8, | ||
n_clusters_per_class=1, | ||
class_sep=0.8, | ||
random_state=0, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We need to make sure that we do not sample from the training set:
random_state=0, | |
random_state=1, # Use a different seed to sample different points. |
Reference Issues/PRs
Fixes #32201
What does this implement/fix? Explain your changes.
To be used in RFE and RFECV,
permutation_importance
needs to be aware of which features were already eliminated by the procedure to reduce its test dataset.This PR adds a
feature_indices
parameter tosklearn.feature_selection._base._get_feature_importances
that is given to theimportance_getter
so that it is aware of which features to compute the importance of.Any other comments?
The new feature is added to the test suite and illustrated in the
RFECV
doc example.@glemaitre @ogrisel