-
Notifications
You must be signed in to change notification settings - Fork 41
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
Detected call of Ir_scheduler.step( before 'optimizer.step()
.
#37
Comments
not really an issue since it only affects a single step (out of thousands) |
Sure, thank you for your response. I encountered the following issue during the training process. After running the code for one epoch, it threw an error and stopped. The reason seems to be related to WandB (Weights and Biases). I want to disable it, but the User |
that seems to be a different, unrelated issue (for which it is better to open a separate issue). |
I'm sorry; next time, I will create a new separate question. I executed the following command to run. GPU_IDS=0 |
closing this issue which is continued here: #39 |
Detected call of Ir_scheduler.step(
before 'optimizer.step()
. In PyTorch 1.1.0 and later, you should call them in the opposite order:'optimizer.step(before 'Ir_scheduler.step()
. Failure to do this will result in PyTorch skipping the first value of the learning rate schedule. See more details at https://pytorch.org/docs/stable/optim.html#how-to-adjust-learning-rateIf the mentioned error occurs during training, how should it be resolved?
The text was updated successfully, but these errors were encountered: