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

Always use balanced accuracy #1

Closed
rhiever opened this issue Nov 11, 2015 · 0 comments
Closed

Always use balanced accuracy #1

rhiever opened this issue Nov 11, 2015 · 0 comments
Assignees
Labels

Comments

@rhiever
Copy link
Contributor

rhiever commented Nov 11, 2015

There is no reason not to always use balanced accuracy for the fitness function by default.

@rhiever rhiever added the bug label Nov 11, 2015
@rhiever rhiever self-assigned this Nov 11, 2015
rhiever pushed a commit that referenced this issue Jun 17, 2016
Fix operator references in _gradient_boosting export code (Fixes #1
rhiever pushed a commit that referenced this issue Jul 3, 2016
Merge with rhiever/master
@danthedaniel danthedaniel mentioned this issue Sep 9, 2016
rhiever added a commit that referenced this issue Dec 8, 2016
rhiever added a commit that referenced this issue Dec 8, 2016
Merge pull request #1 from rhiever/master
rhiever pushed a commit that referenced this issue Apr 17, 2017
weixuanfu pushed a commit that referenced this issue Jun 21, 2018
Update sample_weights documentation
weixuanfu pushed a commit that referenced this issue Oct 4, 2019
Update README.md with full name.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant