-
Notifications
You must be signed in to change notification settings - Fork 3.8k
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
[python] Bug fix for first_metric_only on earlystopping. #2209
[python] Bug fix for first_metric_only on earlystopping. #2209
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.
@matsuken92 Thank you very much for continuing the work on this PR! Unfortunately, I hadn't had a chance to take a closer look yet, but below are some comments which I can leave after a brief glance.
@matsuken92 Seems that I've managed to relax |
Yes, of course, please! |
Done! Please take a look at the latest commit. Also, it seems to me that something is wrong with sklearn wrapper ( |
Below is the example about what I was saying.
Output for
And here are results for 9387197 (the latest commit in this PR), just add
|
@matsuken92 Also, here is another one thing which should be updated for the consistent behavior of LightGBM/python-package/lightgbm/sklearn.py Line 526 in dace050
|
@StrikerRUS |
5316ff4
to
c3fbf6b
Compare
@matsuken92 Thanks a lot for your hard work! I pushed some commits in which I simplified code a little bit, moved initialization to |
@matsuken92 The one (and the last one, I hope 😄 ) thing needed to fix is that in case of LightGBM/python-package/lightgbm/callback.py Lines 228 to 232 in b310fb4
In other words, message is not printed and |
I checked it with the following settings (just change
|
I'm sorry, I was not clear enough! That
I'm not sure, but it seems to me that it's the only case when it is possible. |
@StrikerRUS Thanks. I got it, now I can reproduce the behavior. I will investigate it. |
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.
@matsuken92 Thank you very much for fixing bug with final iteration! And of course many thanks for the whole work!
I'm really excited to approve this PR finally! 🎉
@guolinke @chivee @henry0312 Can you please review this? |
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.
LGTM
@StrikerRUS is this ready? |
Yep! As no one else don't want to leave a review, I'm merging. |
@StrikerRUS I’m happy to be merged this PR! Thank you for your a lot of supports!!! |
@matsuken92 Awesome work and great patience from your side! Thanks! I hope you'll find some time and we'll see a PR for #2105 in the future as you've already dug deep into Python code. |
(This PR is latest version of #2127. Once this PR is activated #2127 should be closed.)