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

[BUG] MAP@50 is too low #5493

Open
1 of 3 tasks
stevensagaert opened this issue Feb 17, 2025 · 0 comments
Open
1 of 3 tasks

[BUG] MAP@50 is too low #5493

stevensagaert opened this issue Feb 17, 2025 · 0 comments
Labels
bug Bug fixes

Comments

@stevensagaert
Copy link

Instructions

Thank you for submitting an issue. Please refer to our
issue policy
for information on what types of issues we address.

  1. Please fill in this template to ensure a timely and thorough response
  2. Remove the section instructions but leave the section header
  3. Place an "x" between the brackets next to an option if it applies. For
    example:
    • Selected option
  4. Please delete everything above this line before submitting the issue

Describe the problem

When evaluating a Utralytics yolo model on a dataset the reported map@50 is way lower than the one from ultralytics

Code to reproduce issue

here is a snippet of code for the eval (of course you still need to define your datasets & model & train it)

data.apply_model(model, label_field="predictions",confidence_thresh=conf)

results = data.evaluate_detections(
    "predictions",
    gt_field="detections",
    classes=['car'],
    eval_key="eval",
    iou=0.5, #threshold for map@50
    compute_mAP=True,
    use_boxes=False #use bounding boxes to calculate IoU
)

results.print_report()
map=results.mAP()
print("mAP@50:", map) 
# commands and/or screenshots here

System information

  • OS Platform and Distribution (e.g., Linux Ubuntu 22.04): ubuntu 24.04
  • Python version (python --version): 3.12.3
  • FiftyOne version (fiftyone --version): 1.3.0
  • FiftyOne installed from (pip or source): pip

Other info/logs

Include any logs or source code that would be helpful to diagnose the problem.
If including tracebacks, please include the full traceback. Large logs and
files should be attached. Please do not use screenshots for sharing text. Code
snippets should be used instead when providing tracebacks, logs, etc.

Willingness to contribute

The FiftyOne Community encourages bug fix contributions. Would you or another
member of your organization be willing to contribute a fix for this bug to the
FiftyOne codebase?

  • Yes. I can contribute a fix for this bug independently
  • Yes. I would be willing to contribute a fix for this bug with guidance
    from the FiftyOne community
  • [ x] No. I cannot contribute a bug fix at this time
@stevensagaert stevensagaert added the bug Bug fixes label Feb 17, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Bug fixes
Projects
None yet
Development

No branches or pull requests

1 participant