Codecov Report

Attention: Patch coverage is 92.10526% with 3 lines in your changes missing coverage. Please review.

Project coverage is 74.03%. Comparing base (e0f8eda) to head (0d85630).
Report is 665 commits behind head on main.

@@            Coverage Diff             @@
##             main   #16436      +/-   ##
==========================================
- Coverage   78.59%   74.03%   -4.56%     
==========================================
  Files         128      128              
  Lines       17138    17175      +37     
==========================================
- Hits        13469    12715     -754     
- Misses       3669     4460     +791     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

How about changing yolo info -> yolo inspect

@inisis thank you for the suggestion! We'll consider it for future updates.

@glenn-jocher What about inspecting an onnx model, we can call onnxslim --inspect model.onnx or with an inscript call to see the details

Thank you for the suggestion! We'll consider adding an inspection feature for ONNX models in future updates.

@glenn-jocher @Burhan-Q How about format summary like this

yolo info yolov8s.pt

yolo info yolov8n.pt meta=True

yolo info yolov8n-obb.onnx meta=True

yolo info yolov8n.mlpackage meta=True classes=True

Thank you for the suggestion! We'll consider enhancing the format summary for future updates.

@glenn-jocher we can also print the onnx model in details, I can submit a pr for it

Thank you for the offer! Please feel free to submit a PR, and we'll review it.

@inisis I'm guessing (not 100% certain) that ONNX detail would be specific to the format. Currently, the implementation I have is agnostic to the file format and is primarily looking for the model metadata. I like the idea of having that kind of information shown, but it would need to work for all formats, which would be a massive PR (smaller + simpler is the way to go). Also, subjectively, the alignment for the OPs numbers is triggering me 😆

I'm still waiting on feedback from the Team if this idea is of any interest to merge into the code. I'm thinking we should see what the feedback looks like before we jump in too deep with the idea and stacking features; this is intended to be an MVP.

I have created a pr #16648

Thank you for your contribution! We'll review your PR soon.

@Burhan-Q changes look good, ready for review once the conflicts are resolved.

@glenn-jocher I no longer have permissions to push to this branch.

It seems like you may need to fork the repository and submit a new pull request with your changes. Let us know if you need further guidance!

👋 Hello there! We wanted to let you know that we've decided to close this pull request due to inactivity. We appreciate the effort you put into contributing to our project, but unfortunately, not all contributions are suitable or aligned with our product roadmap.

We hope you understand our decision, and please don't let it discourage you from contributing to open source projects in the future. We value all of our community members and their contributions, and we encourage you to keep exploring new projects and ways to get involved.

For additional resources and information, please see the links below:

• Docs: https://docs.ultralytics.com
• HUB: https://hub.ultralytics.com
• Community: https://community.ultralytics.com

Thank you for your contributions to YOLO 🚀 and Vision AI ⭐

@Burhan-Q closing as too many code changes here for this feature. Thank you for the effort though!