-
-
Notifications
You must be signed in to change notification settings - Fork 25.9k
KBinsDiscretizer : Support inverse_transform for encode other than ordinal #11489
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
Comments
Hi, can I try this? |
welcome to contribute :) |
I'm having a small problem with the test test_non_meta_estimators. It fail an assertion due to the fact that on the fit process I'm storing the OHE and therfore
|
It's not uncommon to set attributes in fit? I don't think it will cause a test failure. Maybe you can submit a PR for us to review. |
…n#11489] This PR introduce inverse_transform in KBinsDiscretizer for encoder other than ordinal.
Is the issue still open ? Like can i try this? |
@divayjindal95 @ggc87 has submitted a PR. Please try other issues without an active PR. |
@qinhanmin2014 Sure thanks :) |
@qinhanmin2014 , sorry to ask such a silly question, but i am unable to find any good first issue with no active pr, is there any particular way i could find that out ? |
@divayjindal95 Try searching for |
But no, it's not easy to find that out. GitHub doesn't provide a API for
tracking whether an issue is referenced by a PR, and we don't have the
personnel availability to track this with manual labels. One useful manual
label is "stalled" on a pull request, which might not need much work to
complete.
|
Resolved in #11489 |
Currently, we only support
encode='ordinal'
ininverse_transform
. Since we've supportedinverse_transform
inOnehotEncoder
, it's natural to supportinverse_transform
forencode='onehot'
andencode='onehot-dense'
. Store the fitted encoder will be a reasonable solution here. (See #11467 (comment))The text was updated successfully, but these errors were encountered: