Novice Help

[Diplomatic-Capybara]

Cannot get gradio to work

===

more importantly; run.py produces the following, then quits
Please advise thank you

===

usage: run.py [-h] [--device DEVICE] [--pretrained-model PRETRAINED_MODEL] [--foreground-ratio FOREGROUND_RATIO] [--output-dir OUTPUT_DIR] [--texture-resolution TEXTURE_RESOLUTION] [--remesh_option {none,triangle, quad}] [--batch_size BATCH_SIZE] image [image ...]
run.py: error: the following arguments are required: image

trim1.mp4

[jammm]

For run.py, you should open a terminal window first, change directory to the folder where you cloned this repository, and then type the run.py command as described on the README:

python run.py demo_files/examples/chair1.png --output-dir output/

It appears however that you want to run the gradio demo. So you should instead follow the command for gradio_app.py instead:
python gradio_app.py

Make sure you have followed the installation instructions as well, i.e., Python, pytorch, CUDA, and the dependencies listed in the requirements.txt files.

[jaedmunt]

When I install requirements.txt, I consistently encounter a build failure with gpytoolbox.

Using a ubuntu on AWS, CUDA enabled.

What gives? I have nothing else in venv and only install reqs but it never works....

For run.py, you should open a terminal window first, change directory to the folder where you cloned this repository, and then type the run.py command as described on the README:

python run.py demo_files/examples/chair1.png --output-dir output/

It appears however that you want to run the gradio demo. So you should instead follow the command for gradio_app.py instead:

python gradio_app.py

Make sure you have followed the installation instructions as well, i.e., Python, pytorch, CUDA, and the dependencies listed in the requirements.txt files.

[jammm]

Can you share the build logs of the failure?

[jaedmunt]

I saw a similar issue in an earlier thread. Same callback re: pynim and gpytoolbox. Effectively identical. I believe using the latest version of the issue is using Ubuntu 22.04. I can recreate another time and will link the thread and post logs, but I am setting up an Amazon Linux Linux instance so I can continue for tonight (for my sanity). I have been trying to work around this all day!

…

On Mon, 26 Aug 2024 at 19:13, Aaryaman Vasishta ***@***.***> wrote: Can you share the build logs of the failure? — Reply to this email directly, view it on GitHub <#24 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ASIY27NW4BR4XOQNNI7NWR3ZTNV4JAVCNFSM6AAAAABMKEBBM2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGMJQG44DKOBRGU> . You are receiving this because you commented.Message ID: ***@***.***>

[jaedmunt]

Can you share the build logs of the failure?

#1

what system has worked for you so I can choose a compatible instance?

[jammm]

Well, if the issue is similar to the one in #1, then yes, give it Ubuntu 22.04 a try.

[jaedmunt]

Well, if the issue is similar to the one in #1, then yes, give it Ubuntu 22.04 a try.

Many thanks, Jamm. Booted one up on the lower version last night and dependencies installed without error. Just fiddling with CUDA drivers and I should be good to go.

Safe to say for anyone having a similar issue to avoid version 24 Ubuntu.

Thanks for the suggestion.