[ML] Extend default evaluation metrics to all available #63939
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This commit extends the set of default metrics for the data frame analytics evaluation API to all available metrics. The motivation is that if the user skips setting an explicit set of metrics, they get most of the evaluation offering.
|
Pinging @elastic/ml-core (:ml) |
|
@szabosteve Perhaps it would be worth adding to our docs an explanation about which metrics are included by default. If you agree let's discuss it offline. |
benwtrent
approved these changes
Oct 20, 2020
dimitris-athanasiou
deleted the
extend-default-metrics-to-all-available
branch
dimitris-athanasiou
added a commit
to dimitris-athanasiou/elasticsearch
that referenced
this pull request
Oct 21, 2020
…#63939) This commit extends the set of default metrics for the data frame analytics evaluation API to all available metrics. The motivation is that if the user skips setting an explicit set of metrics, they get most of the evaluation offering. Backport of elastic#63939
pugnascotia
pushed a commit
to pugnascotia/elasticsearch
that referenced
this pull request
Oct 21, 2020
This commit extends the set of default metrics for the data frame analytics evaluation API to all available metrics. The motivation is that if the user skips setting an explicit set of metrics, they get most of the evaluation offering.
| @@ -76,7 +76,7 @@ public Regression(String actualField, String predictedField, @Nullable List<Eval | |||
| } | |||
|
|
|||
| private static List<EvaluationMetric> defaultMetrics() { | |||
| return Arrays.asList(new MeanSquaredError(), new RSquared()); | |||
| return Arrays.asList(new MeanSquaredError(), new RSquared(), new Huber()); | |||
There was a problem hiding this comment.
Was it on purpose not to include MSLE here? Is it because we cannot set offset automagically for the user?
There was a problem hiding this comment.
It was intentional indeed. The reason is because we cannot calculate MSLE for negative values.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This commit extends the set of default metrics for the
data frame analytics evaluation API to all available metrics.
The motivation is that if the user skips setting an explicit
set of metrics, they get most of the evaluation offering.