-
Notifications
You must be signed in to change notification settings - Fork 11
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
File Not Found error #12
Comments
1st Question) The folder Weights does not exist inside Data folder. But, logs folder exists. Weights folder exists inside HOI-CL/Weights/ Inside train_Solver_HICO.py, when I print "ckpt.model_checkpoint_path" before line 17, the output is But, an error is thrown at line 174: The second path has an additional "Data" This is because the path is replaced inside function : def switch_checkpoint_path(self, model_checkpoint_path): Why is this done? Because the path returned by this function does not exist 2nd Question) When I train ATL for the first time, should the file "res101_faster_rcnn_iter_1190000.ckpt" |
Dear anjugopinath, switch_checkpoint_path is just for my local env because I have trained the model in different machines and the path is different. You can remove it according to you environment. Yes, res101_faster_rcnn_iter_1190000.ckpt is download as follow,
|
I was training ATL on my own dataset. I stopped training midway and tried restarting it again.
But, I am getting the below error:
Traceback (most recent call last):
File "affordance/HOI-CL/tools/Train_ATL_HICO.py", line 210, in
sw.train_model(sess, args.max_iters)
File "affordance/HOI-CL/tools/../lib/models/train_Solver_HICO_MultiBatch.py", line 144, in train_model
self.from_snapshot(sess)
File "affordance/HOI-CL/tools/../lib/models/train_Solver_HICO.py", line 174, in from_snapshot
saver.restore(sess, self.switch_checkpoint_path(ckpt.model_checkpoint_path))
tensorflow.python.framework.errors_impl.NotFoundError: affordance/HOI-CL/Data/Weights/ATL_union_batch1_semi_l2_def4_vloss2_rew2_aug5_3_x5new_coco_res101;
The text was updated successfully, but these errors were encountered: