W&B id is always the same and continue with the old logging. #1851
Labels
bug
Something isn't working
Comments
|
I also tried to reboot my cloud server, change the user account of W&B |
|
|
|
|
TommyZihao
added a commit
to TommyZihao/yolov5
that referenced
this issue
Jan 6, 2021
Fix the bug of always the same W&B ID and continue overwrite with the old logging. BUG report ultralytics#1851
|
I have fixed this bug. |
TommyZihao
added a commit
to TommyZihao/yolov5
that referenced
this issue
Jan 6, 2021
fix the bug of ultralytics#1851 If we had trained on yolov5s.pt, the program will generate a new unique W&B ID. If we hadn't, the program will keep the old code, we can still use --resume aug.
|
@TommyZihao thanks for the PR, will move the conversation over there. |
glenn-jocher
added a commit
that referenced
this issue
Jan 7, 2021
* Update train.py Fix the bug of always the same W&B ID and continue overwrite with the old logging. BUG report #1851 * Fix the bug of duplicate W&B ID fix the bug of #1851 If we had trained on yolov5s.pt, the program will generate a new unique W&B ID. If we hadn't, the program will keep the old code, we can still use --resume aug. * Update general.py * revert train.py changes Co-authored-by: Glenn Jocher <glenn.jocher@ultralytics.com>
This was referenced Apr 11, 2021
Merged
KMint1819
pushed a commit
to KMint1819/yolov5
that referenced
this issue
May 12, 2021
* Update train.py Fix the bug of always the same W&B ID and continue overwrite with the old logging. BUG report ultralytics#1851 * Fix the bug of duplicate W&B ID fix the bug of ultralytics#1851 If we had trained on yolov5s.pt, the program will generate a new unique W&B ID. If we hadn't, the program will keep the old code, we can still use --resume aug. * Update general.py * revert train.py changes Co-authored-by: Glenn Jocher <glenn.jocher@ultralytics.com>
vasilije77
added a commit
to vasilije77/YOLOV5
that referenced
this issue
May 29, 2022
* Update train.py Fix the bug of always the same W&B ID and continue overwrite with the old logging. BUG report ultralytics/yolov5#1851 * Fix the bug of duplicate W&B ID fix the bug of ultralytics/yolov5#1851 If we had trained on yolov5s.pt, the program will generate a new unique W&B ID. If we hadn't, the program will keep the old code, we can still use --resume aug. * Update general.py * revert train.py changes Co-authored-by: Glenn Jocher <glenn.jocher@ultralytics.com>
BjarneKuehl
pushed a commit
to fhkiel-mlaip/yolov5
that referenced
this issue
Aug 26, 2022
* Update train.py Fix the bug of always the same W&B ID and continue overwrite with the old logging. BUG report ultralytics#1851 * Fix the bug of duplicate W&B ID fix the bug of ultralytics#1851 If we had trained on yolov5s.pt, the program will generate a new unique W&B ID. If we hadn't, the program will keep the old code, we can still use --resume aug. * Update general.py * revert train.py changes Co-authored-by: Glenn Jocher <glenn.jocher@ultralytics.com>
SecretStar112
added a commit
to SecretStar112/yolov5
that referenced
this issue
May 24, 2023
* Update train.py Fix the bug of always the same W&B ID and continue overwrite with the old logging. BUG report ultralytics/yolov5#1851 * Fix the bug of duplicate W&B ID fix the bug of ultralytics/yolov5#1851 If we had trained on yolov5s.pt, the program will generate a new unique W&B ID. If we hadn't, the program will keep the old code, we can still use --resume aug. * Update general.py * revert train.py changes Co-authored-by: Glenn Jocher <glenn.jocher@ultralytics.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When I run train.py to train a new mission, W&B always generates the same ID and continue(append) with the old visualization.
I have tried to relogin wandb, change the --name, --project, --data, but not work.
I tried
wandb init, it indeed generates a new ID, but when I run train.py, it's the old ID again.The text was updated successfully, but these errors were encountered: