-
-
Notifications
You must be signed in to change notification settings - Fork 16.4k
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
added config files for much lighter yolov5 models #11812
Conversation
for more information, see https://pre-commit.ci
β¦yolov5 into ultralytics_cleanup
for more information, see https://pre-commit.ci
β¦yolov5 into ultralytics_cleanup
for more information, see https://pre-commit.ci
for more information, see https://pre-commit.ci
β¦yolov5 into ultralytics_cleanup
for more information, see https://pre-commit.ci
β¦yolov5 into ultralytics_cleanup
for more information, see https://pre-commit.ci
β¦yolov5 into ultralytics_cleanup
for more information, see https://pre-commit.ci
Signed-off-by: Glenn Jocher <[email protected]>
Signed-off-by: Glenn Jocher <[email protected]>
mistake, let me redo this, this code was really weird for "legacy" reasons |
@jere357 thank you for bringing this to our attention. We appreciate your effort in providing the config files for lighter YOLOv5 models. Mistakes happen, and we understand the need to make corrections. We appreciate your honesty in acknowledging the issue with the code and taking the initiative to rectify it. We will review the updated pull request (PR) you shared, and our team will carefully evaluate the changes made. We prioritize maintaining a robust and reliable codebase, so your contribution is valuable to us in improving the project. Once again, thank you for your contribution and for being proactive in addressing the issue. We appreciate your understanding and support. If you have any further questions or need assistance, please feel free to let us know. Keep up the great work! Ultralytics YOLOv5 Team |
@glenn-jocher no problem, feel free to open a discussion in how to convert the other PR into an actual PR, i think we gotta figure out where to include it in documentation, whether there is a need to mention these configs in the COCO benchmark. Also transfer them to the other yolov8 repo as future work, that is something i can do but I'd like to see how we figure things out here first. |
Thank you for your understanding. We appreciate your willingness to discuss and collaborate on converting the previous pull request into an actual one. It is important to properly integrate the changes and consider their inclusion in the documentation, as well as decide whether to mention these configs in the COCO benchmark. We also agree that transferring these configs to the other yolov8 repository as future work is a good idea. Once we have resolved the details here, we can proceed with that task. We will take our time to carefully review and discuss the changes in order to ensure a smooth and effective integration. We fully acknowledge the value of lighter models for simple object detection tasks and are excited to work towards making them more accessible to the community. Thank you once again for your contribution and patience. We look forward to collaborating with you on this matter. Ultralytics YOLOv5 Team |
mistake, let me redo this, this code was really weird for "legacy" reasons
this is the actual PR:
#11813
π οΈ PR Summary
Made with β€οΈ by Ultralytics Actions
π Summary
Optimizing and modularizing Ultralytics YOLOv5's codebase for maintainability and functionality.
π Key Changes
yolov5pico.yaml
,yolov5micro.yaml
, andyolov5femto.yaml
.attempt_load
withattempt_load_weights
for model weight initialization across multiple scripts.π― Purpose & Impact