MetricTracker
use higher_is_better
as default for maximize
#2545
Labels
enhancement
New feature or request
MetricTracker
use higher_is_better
as default for maximize
#2545
🚀 Feature
Change the
maximize
argument for theMetricTracker
wrapper from defaulting toTrue
to using thehigher_is_better
property of the metric(s) if nomaximize
is supplied.Motivation
Reduce boilerplate code. In 99% of use cases, you want to track the best metric rather than the worst. Most metrics you would want to track already have a
higher_is_better
property, so manually typingmaximize
is just boilerplate. Additionally, the current approach of defaulting toTrue
is kinda arbitrary, as it's roughly 50/50 whether you want to maximize or minimize a random metric.Pitch
The amount of code changes needed is minimal as it only affects the
__init__
method, leaving the rest of the implementation unchanged.Here's a suggested implementation:
Additional context
I haven't made many pull requests before, so i'm very open to suggestions and changes :)
The text was updated successfully, but these errors were encountered: