Closed Night1099 closed 3 months ago
I fixed this by doing
python main.py --start_epoch 0
Ive put in a pull request to provide instructions of how to do this
Hi, I have the same problem when I run it too. I followed your instructions python main.py --start_epoch 0 and ran it and it still reported an error. Do you know how to fix it?
student01@ubuntu-Precision-7920-Tower:~/CDFormer-main$ python main.py --start_epoch 0
in checkpoint
Making model...
/home/student01/anaconda3/envs/cdf/lib/python3.8/site-packages/torch/functional.py:504: UserWarning: torch.meshgrid: in an upcoming release, it will be required to pass the indexing argument. (Triggered internally at ../aten/src/ATen/native/TensorShape.cpp:3526.)
return _VF.meshgrid(tensors, *kwargs) # type: ignore[attr-defined]
Preparing loss function:
1.000 L1
/home/student01/anaconda3/envs/cdf/lib/python3.8/site-packages/torch/optim/lr_scheduler.py:136: UserWarning: Detected call of lr_scheduler.step()
before optimizer.step()
. In PyTorch 1.1.0 and later, you should call them in the opposite order: optimizer.step()
before lr_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-rate
warnings.warn("Detected call of lr_scheduler.step()
before optimizer.step()
. "
/home/student01/anaconda3/envs/cdf/lib/python3.8/site-packages/torch/optim/lr_scheduler.py:149: UserWarning: The epoch parameter in scheduler.step()
was not necessary and is being deprecated where possible. Please use scheduler.step()
to step the scheduler. During the deprecation, if epoch is different from None, the closed form is used instead of the new chainable form, where available. Please open an issue if you are unable to replicate your use case: https://github.com/pytorch/pytorch/issues/new/choose.
warnings.warn(EPOCH_DEPRECATION_WARNING, UserWarning)
G_lossfnweight
1.0
[Epoch 1] Learning rate: 1.00e-4
Traceback (most recent call last):
File "main.py", line 30, in
And script just stops with no errors, using same env as listed on readme and requirements.txt