-
-
Notifications
You must be signed in to change notification settings - Fork 26k
MAINT Deprecate scoring='max_error' and replace it by scoring='neg_max_error' #29462
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
MAINT Deprecate scoring='max_error' and replace it by scoring='neg_max_error' #29462
Conversation
Thanks for your PR, I edited your description and PR title to help potential reviewers! |
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, thanks!
Co-authored-by: Loïc Estève <loic.esteve@ymail.com>
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, and it seems consistent with the other work we've done.
Reference Issues/PRs
Fixes #29417 8000
This deprecates
scoring='max_error
and replaces it withscoring='neg_max_error'
.This is very similar to #14898 that did a similar thing for
scoring='brier_score_loss'
=>scoring='neg_brier_score'
What does this implement/fix? Explain your changes.
Renames the
max_error
scorer toneg_max_error
in order to make it consistent with other scorers that havegreater_is_better = False
(and consistent with the documentation as well). Deprecatesmax_error
with a deprecation warning message stating that it will be removed in v1.8.Any other comments?
Please remove the deprecation warning, deprecation test case and the two comment lines I added (which start with
XXX
) once the old scorer is removed.