Aggregate Metric Results #1731
Open
Aggregate Metric Results #1731
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
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.
Description
This PR implements issue #1707. Currently, the metric system allows you to compute a metrics result. However, it is not possible to easily compare the results from several models in the same table or plot. In this PR, it is added two new functions
aggregate_metric_resultsandplot_aggregate_metric_resultsthat solves the comparison problem.Besides, it has been added a base class
MetricResultfrom which the different results are inherited.Type of change
New feature (non-breaking change which adds functionality)
How has this change been tested, please provide a testcase or example of how you tested the change?
It has been tested using Google Colab and it can be found here. Inside the Colab it is possible to find the different use cases considered.
Any specific deployment considerations
N/A