Closed Anthonia2001 closed 8 months ago
π Hello @Anthonia2001, 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 a minimum reproducible example to help us debug it.
If this is a custom training β Question, please provide as much information as possible, including dataset image examples and training logs, and verify you are following our Tips for Best Training Results.
Python>=3.8.0 with all requirements.txt installed including PyTorch>=1.8. To get started:
git clone https://github.com/ultralytics/yolov5 # clone
cd yolov5
pip install -r requirements.txt # install
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, validation, inference, export and benchmarks on macOS, Windows, and Ubuntu every 24 hours and on every commit.
We're excited to announce the launch of our latest state-of-the-art (SOTA) object detection model for 2023 - YOLOv8 π!
Designed to be fast, accurate, and easy to use, YOLOv8 is an ideal choice for a wide range of object detection, image segmentation and image classification tasks. With YOLOv8, you'll be able to quickly and accurately detect objects in real-time, streamline your workflows, and achieve new levels of accuracy in your projects.
Check out our YOLOv8 Docs for details and get started with:
pip install ultralytics
@Anthonia2001 hi there! It seems like the issue you're encountering could be due to the camera resource being already in use. This particular error can sometimes occur if the camera resource is not released properly elsewhere in the application or if another process is holding onto it. Since it works on Windows, it's possible that there's an underlying system difference causing the discrepancy.
To resolve this, you might want to check for any other processes or scripts that might be using the camera resource and ensure that they release it properly. You could also try restarting the system to ensure that the camera resource is freed up.
If the issue persists, you could look into any specific device locking mechanisms for the Intel Realsense camera on Ubuntu. It's also worth checking if there are any specific device permissions that need to be set for accessing the camera on Ubuntu.
I hope this helps! Let me know if you have any other questions or if there's anything else I can assist you with.
π Hello there! We wanted to give you a friendly reminder that this issue has not had any recent activity and may be closed soon, but don't worry - you can always reopen it if needed. If you still have any questions or concerns, please feel free to let us know how we can help.
For additional resources and information, please see the links below:
Feel free to inform us of any other issues you discover or feature requests that come to mind in the future. Pull Requests (PRs) are also always welcomed!
Thank you for your contributions to YOLO π and Vision AI β
Search before asking
YOLOv5 Component
No response
Bug
Hi! I am a Ubuntu user to run Yolov5 with my ROS node. At the beginnings, I used the code in yolov5s to detect object and provide x,y,z from Intel Realsense Camera D435. The program is running without any errors.
After I changed to yolov5s-seg for the segmentation task. The code predict.py still works but then I modified it into the code below:
And it gave me this error:
The camera image window still appeared, but when it could detect the objects, it crashed and informed the device is busy even though I didn't use the realsense in another apps. Is there the problem with threading or Ubuntu with Windows problem because when I running it on Windows, it works?
Environment
Minimal Reproducible Example
No response
Additional
No response
Are you willing to submit a PR?