Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Weights at epoch 64 not found
See original GitHub issueI was running the script of run_demo_pytorch.py using the command:
python run_demo_pytorch.py --config_filename=data/model/pretrained/METR-LA/config.yaml
This is what I got: Traceback (most recent call last): File “run_demo_pytorch.py”, line 33, in <module> run_dcrnn(args) File “run_demo_pytorch.py”, line 18, in run_dcrnn supervisor = DCRNNSupervisor(adj_mx=adj_mx, **supervisor_config) File “/home/cyd/DCRNN_PyTorch/model/pytorch/dcrnn_supervisor.py”, line 50, in init self.load_model() File “/home/cyd/DCRNN_PyTorch/model/pytorch/dcrnn_supervisor.py”, line 93, in load_model assert os.path.exists(‘models/epo%d.tar’ % self._epoch_num), ‘Weights at epoch %d not found’ % self._epoch_num AssertionError: Weights at epoch 64 not found
Could you please upload the ‘models/epo64.tar’ to the repo? I hope to reproduce the MAE results demonstrated in README. Thx!
Issue Analytics
- State:
- Created 4 years ago
- Comments:12 (2 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
@chnsh actually I ended up doing the change in data/model/pretrained/METR-LA/config.yaml and that did it
Setting train/epoch to 0 in data/model/dcrnn_test_config.yaml solves the problem for me.