-
-
Notifications
You must be signed in to change notification settings - Fork 15.9k
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
Torch v1.12 fixes bug to train a model, but YoloV5 rejects the version. #8609
Comments
👋 Hello @Exortions, thank you for your interest in YOLOv5 🚀! Please visit our ⭐️ Tutorials to get started, where you can find quickstart guides for simple tasks like Custom Data Training all the way to advanced concepts like Hyperparameter Evolution. If this is a 🐛 Bug Report, please provide screenshots and minimum viable code to reproduce your issue, otherwise we can not help you. If this is a custom training ❓ Question, please provide as much information as possible, including dataset images, training logs, screenshots, and a public link to online W&B logging if available. For business inquiries or professional support requests please visit https://ultralytics.com or email support@ultralytics.com. RequirementsPython>=3.7.0 with all requirements.txt installed including PyTorch>=1.7. To get started: git clone https://github.com/ultralytics/yolov5 # clone
cd yolov5
pip install -r requirements.txt # install EnvironmentsYOLOv5 may be run in any of the following up-to-date verified environments (with all dependencies including CUDA/CUDNN, Python and PyTorch preinstalled):
StatusIf this badge is green, all YOLOv5 GitHub Actions Continuous Integration (CI) tests are currently passing. CI tests verify correct operation of YOLOv5 training (train.py), validation (val.py), inference (detect.py) and export (export.py) on macOS, Windows, and Ubuntu every 24 hours and on every commit. |
It seems that they intentionally exclude torch 1.12.0 because the version has a serious bug in multi-GPU environments. TL; DR: The only thing we users can do is wait for the new release of torch (1.12.1, presumably). |
@Exortions @equal-l2 good news 😃! Your original issue may now be fixed ✅ in PR #8621. torch==1.12.0 installs are now allowed, and an assert torch!=1.12.0 has been inserted into a new smart_DDP() function. The Docker image is using torch nightly and trains DDP correctly. To receive this update:
Thank you for spotting this issue and informing us of the problem. Please let us know if this update resolves the issue for you, and feel free to inform us of any other issues you discover or feature requests that come to mind. Happy trainings with YOLOv5 🚀! |
Thank you so much! |
@Exortions you're very welcome! 🎉 Kudos to the persevering and passionate YOLO community - and the incredible Ultralytics team who made this update possible. Please don't hesitate to reach out if you have any more questions or need further assistance. Good luck with your YOLOv5 adventures! |
Search before asking
YOLOv5 Component
Training
Bug
Recently, training in YOLOv5 would crash because of an error in PyTorch. (See this issue: pytorch/pytorch#74016)
PyTorch released a fix in version 1.12, but YOLOv5 doesn't train with this error:
requirements: torch!=1.12.0,>=1.7.0 not found and is required by YOLOv5, attempting auto-update...
It then downgrades PyTorch to v1.11.0, which once again crashes the training process when ran with it.
How can I get PyTorch v1.12 to run with YOLOv5?
Environment
Minimal Reproducible Example
Additional
No response
Are you willing to submit a PR?
The text was updated successfully, but these errors were encountered: