Skip to content
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

[CRITICAL] Regression is now broken due to legacy bugs #42

Closed
carefree0910 opened this issue Dec 8, 2020 · 0 comments
Closed

[CRITICAL] Regression is now broken due to legacy bugs #42

carefree0910 opened this issue Dec 8, 2020 · 0 comments
Labels
bug Something isn't working
Projects

Comments

@carefree0910
Copy link
Owner

This bug is caused by introducing get_outputs. Previously, when binary_threshold_outputs is not None, we know that this is definitely a binary classification task. But now it will never be None, even on regression tasks.

@carefree0910 carefree0910 added the bug Something isn't working label Dec 8, 2020
@carefree0910 carefree0910 added this to To do in v0.1.7 via automation Dec 8, 2020
v0.1.7 automation moved this from To do to Done Dec 8, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
No open projects
v0.1.7
  
Done
Development

No branches or pull requests

1 participant