Colab FileNotFoundError about clipasso HOT 8 CLOSED

If it is of any help for someone else I found the cause of the error in my case - there is a hardcoded "python" command inside the run_object_sketching.py code which in my case launches a python 2 instance since my machine uses "python3" to run python3 - this also caused the string related errors.

So renaming
exit_codes.append(sp.run(["python", "painterly_rendering.py", target,
to
exit_codes.append(sp.run(["python3", "painterly_rendering.py", target,

in run_object_sketching.py fixed it for me

from clipasso.

Hello Pavel, thanks for your interest in our work!
This file should appear after the successful creation of a single sketch (with seed0), receiving this exception means that something went wrong when running the code previously.

Can you please provide more details about the error?

1. In which of the stages did it happen? (stage 2 or 3)
2. Can you please share the full exception traceback? (i.e. the entire output you received before this line)

from clipasso.

I am getting the same error when trying to follow the quick start example that uses run_object_sketching.py - it seems to be connected with the f"{something}" string formatting in some of the logging/saving utils (maybe it is a python version issue?)

from clipasso.

Hey I encountered same issue.

from clipasso.

@PavelGrigorev did you restart the runtime after stage 1? with "Runtime > Restart runtime"
If not, please try to restart the runtime and then rerun stage 2 - please let me know if it worked.
If you did, can you please tell me if you see any files under "output_sketches/camel"?

from clipasso.

I got it!!!
I did not restart the kernel in stage 1
Now it works fine!
thank you for sharing your awesome work!

from clipasso.

@PavelGrigorev great! thanks for your update :)

from clipasso.

Hi @jthteo, note that I opened a new issue for your response as you used Docker and not colab, so you experienced a different issue :) please reply on the new thread.

Same for @04RR - please provide more details on your environment (docker? colab? pip?) in a new related issue, in case you used colab, and you had the same problem as Pavel's, ignore this comment :)

from clipasso.