-
-
Notifications
You must be signed in to change notification settings - Fork 26k
FIX Incorrect warning when clustering boolean data #19046
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
Conversation
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 @Prakashsur , this looks good so far. Could you please also need a non-regression test making sure that:
- no warning is raised if the data passed o fit is already converted to
bool
- a single warning (the one you just added) is raised if the data passed to fit isn't converted to
bool
thanks!
Co-authored-by: Nicolas Hug <contact@nicolas-hug.com>
@NicolasHug Thanks |
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.
Thank you @jdsurya ! made some minor comments but LGTM
Co-authored-by: Nicolas Hug <contact@nicolas-hug.com>
Co-authored-by: Nicolas Hug <contact@nicolas-hug.com>
Co-authored-by: Nicolas Hug <contact@nicolas-hug.com>
Co-authored-by: Nicolas Hug <contact@nicolas-hug.com>
Hi @jdsurya , thanks for your pull request.
|
Hi @cmarmo, ntmu! Thanks for sharing the details! The two linting issues have been fixed and are passing now. |
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.
Thank you for the PR @jdsurya !
LGTM
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.
Please add an entry to the change log at doc/whats_new/v1.0.rst
with tag |Fix|. Like the other entries there, please reference this pull request with :pr:
and credit yourself (and other contributors if applicable) with :user:
.
Thank you for details regarding the entry into 'whats_new' Thomas @thomasjpfan! The same has been added. |
Co-authored-by: Nicolas Hug <contact@nicolas-hug.com>
Fixes #18996
Input X was being converted to float at the beginning of fit() method. However when a pairwise boolean metric was requested, X was again converted to boolean with multiple warning.
This caused were two issues:
As a FIX, a check has been put in place in the fit() method itself to let boolean data pass as such. However, when the data needs to be converted to boolean, it is done at this level only with the same warning that was printed earlier, but only once.