You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have searched the YOLOv5 issues and found no similar bug report.
YOLOv5 Component
Multi-GPU
Bug
First thank you for your great work!
In the latest verson, when i make the opt parameter device="0", it also use all GPUs.
When I check the function select_device, I found that the potision of 'os.environ['CUDA_VISIBLE_DEVICES'] = device' has an effect on the results. When I put it on the first line of the 'elif device' section, then it works, I dont know why ?
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.
YOLOv5 may be run in any of the following up-to-date verified environments (with all dependencies including CUDA/CUDNN, Python and PyTorch preinstalled):
If 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.
@Ethan-niu thanks for the bug report! I'm able to reproduce the same bug, yes you are right the location in the if statement seems to affect the behavior, it's strange, I'm not sure why either.
Activity
github-actions commentedon Jan 26, 2022
👋 Hello @Ethan-niu, 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.
Requirements
Python>=3.7.0 with all requirements.txt installed including PyTorch>=1.7. To get started:
Environments
YOLOv5 may be run in any of the following up-to-date verified environments (with all dependencies including CUDA/CUDNN, Python and PyTorch preinstalled):
Status
If 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.
glenn-jocher commentedon Jan 26, 2022
@Ethan-niu thanks for the bug report! I'm able to reproduce the same bug, yes you are right the location in the if statement seems to affect the behavior, it's strange, I'm not sure why either.
Fix `select_device()` for Multi-GPU
Fix `select_device()` for Multi-GPU
Fix `select_device()` for Multi-GPU (#6434)
Update Neuralmagic-YoloV5 integration to v6.1 (#29)
Fix `select_device()` for Multi-GPU (ultralytics#6434)
Fix `select_device()` for Multi-GPU (#6434)
Fix `select_device()` for Multi-GPU (#6434)