8000 [WIP] Resolve #157 - Allow NaNs in Random*Samplers by chkoar · Pull Request #167 · scikit-learn-contrib/imbalanced-learn · GitHub
[go: up one dir, main page]

Skip to content

[WIP] Resolve #157 - Allow NaNs in Random*Samplers #167

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

Closed
wants to merge 1 commit into from

Conversation

chkoar
Copy link
Member
@chkoar chkoar commented Oct 24, 2016

With this PR I tried to address the #157 issue, but doing this the check_estimator test is falling because internally calls the check_estimators_nan_inf which desn't accept NaNs if name not in ['Imputer'] and raises error.

We could skip the two tests that failing for this reason and open an issue in the scikit-learn repository to get feedback like this scikit-learn/scikit-learn#6981. Thoughts @dvro @glemaitre ?

@glemaitre
Copy link
Member

We can check what are the thoughts from the scikit-learn community. In fact, I am not a big fan to let NaN to get it in, even if sometimes those values are valid. But if several people think that it is something which need to be addressed, we can go for it and skip those tests.

@chkoar Can you open an issue to get a feedback?

@chkoar
Copy link
Member Author
chkoar commented Oct 24, 2016

I am not a big fan to let NaN to get it in, even if sometimes those values are valid.

@glemaitre Actually I agree with that. I was thinking that we should be consistent with all samplers.
I wouldn't say that the values are valid. I think that the values are irrelevant to the procedure of Random*Sampling. I mean the values of X.

I saw the ticket opened and tried to solve it. We could just label the issue as wontfix and close it.

@glemaitre
Copy link
Member

I saw the ticket opened and tried to solve it. We could just label the issue as wontfix and close it.

As you suggested, I would see what are the thoughts in scikit-learn community. If we find out that it will not change because they want to keep it not flexible, we can close for that reason and document the issue.

@chkoar
Copy link
Member Author
chkoar commented Nov 7, 2016

How should we handle this PR? scikit-learn/scikit-learn#7737

@glemaitre
Copy link
Member

I would not include this for the moment

@dvro
Copy link
Member
dvro commented Nov 14, 2016

I would not include this for the moment [2]

@chkoar
Copy link
Member Author
chkoar commented Nov 14, 2016

I still think that we could try this #157 (comment) like in Decision Trees in scikit-learn (https://github.com/scikit-learn/scikit-learn/blob/a5ab948/sklearn/tree/tree.py#L380)

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

Successfully merging this pull request may close these issues.

3 participants
0