-
-
Notifications
You must be signed in to change notification settings - Fork 8.7k
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
Fix handling of print period in EvaluationMonitor #6499
Fix handling of print period in EvaluationMonitor #6499
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.
LGTM.
@trivialfis Can I also get a review from you?
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 fix! Could you please help modifying the test test_callback.py::test_evaluation_monitor
to capture the fixed error?
Sure |
b78b567
to
0cfef90
Compare
Co-authored-by: Kirill Shvets <kirill.shvets@intel.com>
Currently
verbose_eval
parameter is not taking into account due simple typo in callback.pyIf we set
verbose_eval=100
print log is:[1] eval-auc:0.54791 train-auc:0.54620
...
[98] eval-auc:0.88926 train-auc:0.90105
[99] eval-auc:0.88921 train-auc:0.90110
[101] eval-auc:0.88928 train-auc:0.90114
...
After fix:
[0] eval-auc:0.53902 train-auc:0.53251
[100] eval-auc:0.88931 train-auc:0.90116
...
Similar to v1.2.0 print log