Closed 1andDone closed 1 year ago
π Hello @1andDone, 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
@SimoneGiovannini @florenttaralle @glenn-jocher
Hi, I found out some cropping transformations, like BBoxSafeRandomCrop or RandomCropFromBorders, raise an error of this kind:
RuntimeError: stack expects each tensor to be equal size, but got [3, 640, 640] at entry 0 and [3, 390, 212] at entry 2
I think this is due to the fact that augmentations are applied after the image resizing done by the algorithm. So to solve the problem one should augment before resizing, and it looks like such a change would require some work.
Hi, you are right ! But this is by design. I should have explicited this point. The sizing/cropping are managed by some complex behaviors in yolov5 code (like mosaic) The additionnal transforms you can add MUST NOT modify crop shape.
I saw your discussion in PR https://github.com/ultralytics/yolov5/pull/9628 that was related to the issue I described above. Are there currently ways to implement augmentations that re-size the image in YOLOv5?
π 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 β
@1andDone hello! Yes, you are correct. As mentioned, the additional transforms should not modify the crop shape. Resizing the image before applying augmentations is necessary to avoid the issue you encountered. You can implement augmentations that resize the image by using libraries such as albumentations or OpenCV before feeding the image into YOLOv5. Let me know if you need further assistance with the implementation.
Search before asking
YOLOv5 Component
Training
Bug
I made updates to the default
albumentations
transforms inyolov5/utils/augmentations.py
using the code highlighted in red below:When running the following in Google Colab:
This is the error I receive:
When I comment out the pixel-level transformations, everything runs smoothly.
Environment
No response
Minimal Reproducible Example
No response
Additional
No response
Are you willing to submit a PR?