-
-
Notifications
You must be signed in to change notification settings - Fork 16.2k
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
wandb: Network error (ReadTimeout), entering retry loop. See wandb\debug-internal.log for full traceback. #2840
Comments
👋 Hello @Zigars, 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://www.ultralytics.com or email Glenn Jocher at glenn.jocher@ultralytics.com. RequirementsPython 3.8 or later with all requirements.txt dependencies installed, including $ 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), testing (test.py), inference (detect.py) and export (export.py) on MacOS, Windows, and Ubuntu every 24 hours and on every commit. |
also, when I switch to yolov5s.yaml, I still can not train normally, if there have some way that I can close wandb so that I can train normally, I used have login in wandb, and my network can't open wandb.ai too. |
I uninstall the wandb and solve this bug... |
@Zigars hi sorry to hear about your logging issues! Sometimes network interruptions can prevent logging to wandb, though this should not cause an error. @AyushExel, our W&B contact may have some more info. I saw you have a VisDrone.yaml. I've seen this dataset is pretty popular, please consider submitting a Pull Request to add your VisDone.yaml and if possible a get_visdrone.sh file to help future users auto-download this dataset. Thank you! |
@glenn-jocher I'm so happy to get your reply! I enjoy using your yolov5 code to train object detection task, it's a great rep! Recently ,I was doing some research that use yolo to detect VisDrone dataset. I'm sorry that I'm not familiar with git and scratch, So PR or a get_visdrone.sh is a difficult things for me.If you want the VisDrone.yaml and the ready-made VisDrone dataset(I download it from VisDrone, and transform it to coco form), I can send these to your email. |
@Zigars hey great! I think you can attach files directly to these messages, so maybe you can just attach your visdrone yaml and the code you used to download and convert to YOLO format and I could do the PR. |
Hi, @glenn-jocher ,I spend some times to rewrite my convert code, because the original code is a little ugly. :( And I will give you the visdrone.yaml, the code trans_yolo.py and a VisDrone-test.zip dataset zip. visdrone.yaml include the data path, nc=10 and class names; you can convert visdrone to YOLO format by use trans_yolo.py; because the original dataset is too large, you can download the VisDrone-DET in github, and put the annotaions and images in one directory VisDrone-DET like the VisDrone-test.zip. VisDrone-test.zip is test for convert code, include test-dev, train and val data, 3 data type each 10 images and annotations. you can delate the other file except annotations and images, than |
@Zigars Thanks for filing this issue. As @glenn-jocher said, network interruptions can cause wandb to not log data to the dashboard but it should not cause errors. Can you please confirm what version of the wandb client you're using(
|
@AyushExel Sorry, I solve this bug by uninstall the wandb, I remember I update the latest version of wandb? and the terminal could be stick, train.py still do not work in that times. I can show you a debug-internal.log so that you can fix this bug, thank you for your replay! |
@Zigars awesome thanks! I'll see if I can convert this into a PR so future users can autodownload VisDrone more easily. TODO: VisDrone autodownload PR |
@Zigars actually, even better, could you update this line in the PR with a better explanation for this? Then you will also show up as an official PR author for the repo, giving you credit for your work! |
@glenn-jocher hi! I‘m SOOOO happy to give the PR for yolov5! thanks so much! and I can answer your question, this line is because original VisDrone-DET have 12 classes! it include 'ignored regions' and 'others' two classes ,with original annotations |
@Zigars ah I understand now! Yes the dataset is difficult. With this sort of data (very small objects) you should really train at higher resolution with a P6 model, i.e.:
EDIT: actually maybe the P6 model doesn't matter, as it's targeted for larger objects, but definitely a higher resolution like 1280 or 1920 would help this dataset. |
🐛 Bug
I try to use your rep to train yolov4's NET because yolov4(https://github.com/WongKinYiu/PyTorch_YOLOv4)'s code is outdate and do not maintain, it has many bugs.
when I train my own yolov4-tiny.yaml, it comes this bug, I think this bug is because my network can not connect to wandb's server? before today, I can train normally, and a few minute ago, I try many times to
python train.py
,but I still can not begin my train code.To Reproduce (REQUIRED)
python train.py
Output:
Expected behavior
A clear and concise description of what you expected to happen.
Environment
If applicable, add screenshots to help explain your problem.
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: