[Feature request] Common stereo metrics.
See original GitHub issue🚀 Feature
To make kornia attractive to stereo researcher, we should consider adding a set of commonly used stereo metrics as is seen in the KITTI or Middlebury benchmarks.
Metrics to consider to add:
- RootMeanSquaredError
- MeanAbsoluteError
- MeanBad{n}Error
We should consider whether we want the metrics to inherit from torchmetrics, such that the metrics can be used in Lightning
modules.
Motivation
Most new stereo research all implement their own metrics - this is a good opportunity for Kornia to get a foothold in stereo research.
Pitch
In kornia.utils.metrics
add above mentioned metrics. Discuss whether we want to inherit from torchmetric
. The metric logic should ideally be split into functions and then referenced in a class that inherits from torchmetric
in case we go that way.
Alternatives
N/A
Additional context
N/A
Issue Analytics
- State:
- Created 2 years ago
- Comments:18 (14 by maintainers)
Top Results From Across the Web
7 Steps to Measuring the Success of a Feature - Amplitude
Step 1: Measure basic usage of the new feature There are a few key metrics you should look at to get a complete...
Read more >Guide Feature Requests: Metrics and more - Zendesk help
This includes things like general discussion, product feedback, and announcements. While trying to build our community, we've noticed a few key ...
Read more >How SaaS Companies Manage Feature Requests
Feature request tracking tools allow feature requests voting and ranking to understand which of them is most requested. Feature prioritization ...
Read more >4 Essential Feature Request Prioritization Frameworks
4 Essential Feature Request Prioritization Frameworks · 1. Priority Scores · 2. Story Mapping and Opportunity Scoring · 3. Cost of Delay ·...
Read more >10 Best Customer Experience Metrics (According to the Experts)
At ProProfs, we majorly track three customer experience metrics: Net Promoter Score (NPS), Customer Satisfaction Score (CSAT), and Customer ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Not a strong objection. The term of “loss” in DL is more or less ready to be called with
loss.backward()
. If we are going for losses, we’d better have some support/tutorials/examples for that. Also, I think naming likekornia.measures
would attract some DL libraries liketorchmetrics
to use us with less burden (that we are aiming on different directions).our recent policy is just to have our (kornia non-profit org) libs dependencies except for fundamental tensor backend for now.