Skip to content
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

Metrics: Mean Average Recall (mAR) #1583

Open
LinasKo opened this issue Oct 9, 2024 · 3 comments
Open

Metrics: Mean Average Recall (mAR) #1583

LinasKo opened this issue Oct 9, 2024 · 3 comments
Assignees
Labels
enhancement New feature or request hacktoberfest Open for contributions during the annual Hacktoberfest event, aimed at encouraging open-source parti

Comments

@LinasKo
Copy link
Collaborator

LinasKo commented Oct 9, 2024

Metrics: Mean Average Recall (mAR)

Tip

Hacktoberfest is calling! Whether it's your first PR or your 50th, you’re helping shape the future of open source. Help us build the most reliable and user-friendly computer vision library out there! 🌱

We'd like to expand our suite of metrics with a new one - Mean Average Recall (mAR). This would involve creating it, its accompanying results class, and briefly testing it.

Note it is different from mAP in that it don't use the precision-recall curve, but recall-IoU. This affects MeanAverageRecallResult:

  • The will not be mAR@50, mAR@75, etc - only the global main mAR value.
  • Other frameworks threshold by max detections. I suggest we add this later if required.
  • mAP currently implements a single averaging method, and F1 has 3 different ones (micro, macro, weighted). The choice between those is left to PR author - we can always add more later.
  • The metric can report mAR values per-class. Do tell if that is difficult.
  • I think we should have 1.0 as the default if no value are provided. -1 is a consideration too, which should bring the same change to mAP.

Feel free to change the above if it feels better.


Helpful links:

@LinasKo
Copy link
Collaborator Author

LinasKo commented Oct 9, 2024

Contribution guidelines

If you would like to make a contribution, please check that no one else is assigned already. Then leave a comment such as "Hi, I would like to work on this issue". We're happy to answer any questions about the task even if you choose not to contribute.

Testing

Please share a Google Colab with minimal code to test the new feature. We know it's additional work, but it will speed up the review process. You may use the Starter Template. The reviewer must test each change. Setting up a local environment to do this is time-consuming. Please ensure that Google Colab can be accessed without any issues (make it public). Thank you! 🙏

@LinasKo
Copy link
Collaborator Author

LinasKo commented Oct 9, 2024

@onuralpszr, I've heard you already put some work towards this one. Shall I assign it to you?

@LinasKo LinasKo added the hacktoberfest Open for contributions during the annual Hacktoberfest event, aimed at encouraging open-source parti label Oct 9, 2024
@onuralpszr
Copy link
Collaborator

@onuralpszr, I've heard you already put some work towards this one. Shall I assign it to you?

Thank you and yes

@LinasKo LinasKo added the enhancement New feature or request label Oct 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request hacktoberfest Open for contributions during the annual Hacktoberfest event, aimed at encouraging open-source parti
Projects
None yet
Development

No branches or pull requests

2 participants