-
-
Notifications
You must be signed in to change notification settings - Fork 16.5k
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
Evolve failing with wandb activated due to model not being saved #4604
Comments
👋 Hello @adrigrillo, 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 Glenn Jocher at glenn.jocher@ultralytics.com. RequirementsPython>=3.6.0 with all requirements.txt installed including PyTorch>=1.7. To get started: $ git clone https://github.com/ultralytics/yolov5
$ cd yolov5
$ pip install -r requirements.txt 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. |
@adrigrillo thanks for the bug report! To answer your question weights are not saved because the output of evolution is the maximum fitness evolved hyperparameters (in @AyushExel can you look into this? We probably want to filter the upload artifact list to prevent attempting uploading non-existing files, or simply place the upload under an yolov5/utils/loggers/__init__.py Lines 130 to 138 in b894e69
This is effectively silent error handling, so maybe a warning would be appropriate. |
Thanks to you for the fast response and this great repo. With regard to the checkpoint saving, saving 300 Thanks again for the support 😄 |
@glenn-jocher I'll put up a fix for this today |
@AyushExel thanks! |
@glenn-jocher every evolve operation should start a new wandb run right? So the logic in the logger class should be like this:
Here, we're starting a new run if the job type is |
@AyushExel yes each generation should be a new W&B run, i.e. like this more or less from earlier https://wandb.ai/glenn-jocher/COCO128_evolve |
@adrigrillo good news 😃! Your original issue may now be fixed ✅ in PR #4611 by @AyushExel . 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 🚀! |
Thanks for the support!! Great work! ❤️ |
Hello again, I have started to train a network using evolution with the last fixes, however, I am seeing in W&B panel some entries, which last around 6 seconds, that are not real trainings and that have the same hyperparameters as the following training (which is the proper training). I attach the current status of the W&B panel: In this case, I am running my fourth evolution training, but there are this other entries (the ones with a tick) that have the same hyperparameters that the one being trained. |
@adrigrillo I think these are runs from a previous evolution. By default, the evolution runs are all logged in the project called @glenn-jocher I think this is related to train.py more that W&B. The evolve operation project name is hardcoded to |
@AyushExel this is my first evolution execution, I removed all the data of previous ones. |
@AyushExel
|
🐛 Bug
The evolution process fails at the end of the first iteration due to wandb failing to found
last.pt
, which does not exist. The problem is originated in the callback to end the training, that calls the wandb logger and which tries to upload the weight files.Here a doubt arises, why is the model not saved, I mean the
last.pt
, during the evolution process. In this way, the trained model cannot be recovered after training.To Reproduce (REQUIRED)
Input:
Just execute the training process with the 'evolve' flag activated and wandb configured.
Output:
Expected behavior
I expect the
last.pt
to be saved and the training to continue.Environment
The text was updated successfully, but these errors were encountered: