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
FIX correct NeighborhoodComponentsAnalysis (NCA) _n_features_out
value
#28306
Conversation
@glemaitre friendly ping here: is this fix still needed? |
I have to make a deeper review but we need to add a new non-regression test to reproduce the failure seen in the issue and make sure that the changes are fixing it. We also need to add an entry in the changelog under the 1.4.2 version. I'll add the milestone. |
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.
So you can add this entry in the 1.4.2 changelog:
:mod:`sklearn.neighbors`
........................
- |Fix| Fixes :class:`neighbors.NeighborhoodComponentsAnalysis` such that
`get_feature_names_out` returns the correct number of feature names.
:pr:`28306` by :user:`Brendan Lu <brendanlu>`.
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. Thanks @brendanlu
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. Thanks @brendanlu
Reference Issues/PRs
Fixes #28293
What does this implement/fix? Explain your changes.
Implements the changes as suggested by @johentsch, similar to the base pca class.
Any other comments?
Adjusted the (faulty?) existing test logic to pick this issue up.