-
Notifications
You must be signed in to change notification settings - Fork 90
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
No such file or directory: '..../camel_16strokes_seed0/config.npy' (Docker installation) #2
Comments
Hi, can you please check if you have any files under "CLIPSketch/output_sketches/camel/camel_16strokes_seed0"? |
Thanks for moving here u2net.pth is in the correct directory. |
Line 42 does not seem to the problem. Line 82 seems to be referring to a non-existent config.npy file which is named in the error message. I cannot find any sign of this file in the folders. I tried renaming and putting the config.py file from the main directory but it doesn't work either as it doesn't recognise it as for the pickel. |
This error means that there was an exception during running. When execution is done successfully, a "config.npy" file should appear with all the information about the specific session. |
Encountered same issue. Docker installation as per instructions but when >python run_object,,,,, the following happens:
Processing [camel.png] ...
Results will be saved to
[/home/vinker/CLIPSketch/output_sketches/camel/] ...
GPU: True
100%|████████████████████████████████████████| 278M/278M [04:57<00:00, 982kiB/s]
Traceback (most recent call last):
File "run_object_sketching.py", line 99, in
run(seed, wandb_name)
File "run_object_sketching.py", line 83, in run
allow_pickle=True)[()]
File "/home/vinker/miniconda/envs/habitat/lib/python3.7/site-packages/numpy/lib/npyio.py", line 417, in load
fid = stack.enter_context(open(os_fspath(file), "rb"))
FileNotFoundError: [Errno 2] No such file or directory: '/home/vinker/CLIPSketch/output_sketches/camel//camel_16strokes_seed0/config.npy'
Originally posted by @jthteo in #1 (comment)
The text was updated successfully, but these errors were encountered: