Closed HighMans closed 2 years ago
π Hello @HighMans, 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.
Python>=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
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.
@HighMans yes that's correct, zero initial values will stay zero. If you want to mutate values initalize these to non-zero values. See 'intiial conditions' section of hyperparameter tutorial:
Good luck π and let us know if you have any other questions!
Search before asking
YOLOv5 Component
Evolution
Bug
When doing evolutions based off the hyp.scratch-high.yaml, I noticed that the degrees, shear, perspective and flipud parameters always stayed zero, despite having a non-zero mutation scale.
What I think is happening is if the initial starting condition of the evolution and the lower limit defined in the meta dictionary is zero, then the parameter will always be zero.
Then when it comes time to do the mutation, since the mutation is based only on a multiplied scalar, any value that is zero stays zero forever.
https://github.com/ultralytics/yolov5/blob/91a81d48fa4e34dbdbaf0e45a1f841c11216aab5/train.py#L598
I'm also not sure if it's possible for a zero to be the output of the mutation process, but if it is -- I think it's possible that it could also be stuck at zero forever too.
https://github.com/ultralytics/yolov5/blob/91a81d48fa4e34dbdbaf0e45a1f841c11216aab5/train.py#L575-L599
Environment
No response
Minimal Reproducible Example
Additional
Example code produced from snippit in train.py.
https://github.com/ultralytics/yolov5/blob/91a81d48fa4e34dbdbaf0e45a1f841c11216aab5/train.py#L529-L605
Are you willing to submit a PR?