Skip to content
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

Help #8

Open
Zegervg opened this issue Jul 12, 2024 · 21 comments
Open

Help #8

Zegervg opened this issue Jul 12, 2024 · 21 comments

Comments

@Zegervg
Copy link

Zegervg commented Jul 12, 2024

Hi,

I know this is not really an issue, but can you give me an example prompt on how to run the soapbox. Since whenever I run it I dont get results that look like the one from the example in the github.

@Zegervg
Copy link
Author

Zegervg commented Jul 12, 2024

init.mp4

@Zegervg
Copy link
Author

Zegervg commented Jul 12, 2024

init.mp4

@yudianzheng
Copy link
Owner

init.mp4

what are your parameters? As the name of "init.mp4", I think you may just get the initialised strokes instead of optimised sketches.

@Zegervg
Copy link
Author

Zegervg commented Jul 13, 2024

Just the default parameters, but I don't
Capture
think its working either. The script appears to be running without errors but at the end it says 0% and just bails out.

@yudianzheng
Copy link
Owner

I believe the parameters are correct. The main issue is that the program terminates before optimization completes. It is intended to run for 2000 epochs, with an MP4 file output every 100 epochs

@Zegervg
Copy link
Author

Zegervg commented Jul 13, 2024

Yeah I see, do you know any solutions to this issue? Tried debugging it but without success.

@yudianzheng
Copy link
Owner

Yeah I see, do you know any solutions to this issue? Tried debugging it but without success.

Logically speaking, such a thing shouldn't happen, and I haven't encountered this problem before either. You can set breakpoints to check why the process exits after initialization and at which step it exits.

@Zegervg
Copy link
Author

Zegervg commented Jul 18, 2024

Thanks for the advice, I've also tried CLIPasso with docker install which worked fine, could my gpu having to litlle amount of vram be part of the problem?

@yudianzheng
Copy link
Owner

Thanks for the advice, I've also tried CLIPasso with docker install which worked fine, could my gpu having to litlle amount of vram be part of the problem?

Perhaps, you can try decreasing the number of strokes. It may help with low GPU resources.

@Zegervg
Copy link
Author

Zegervg commented Jul 21, 2024

quick question, what exact python version are you running this on and is this on linux or windows

@yudianzheng
Copy link
Owner

quick question, what exact python version are you running this on and is this on linux or windows

python 3.7.5; Linux.

@Zegervg
Copy link
Author

Zegervg commented Jul 21, 2024

ubuntu?

@yudianzheng
Copy link
Owner

ubuntu?

ubuntu20.04 cuda11.3 torch1.12.1.

@Zegervg
Copy link
Author

Zegervg commented Jul 21, 2024

ty

@Zegervg
Copy link
Author

Zegervg commented Jul 25, 2024

hi, me again. I lowered the values and now it seems to be working

"
python run_object_sketching.py --target_file $1 --focus foreground --data_folder ../data/dataset/$1 --consist_param 1.0 --frames_param 0.001 --num_strokes 4 --num_iter 101 --atlas_epoch '010000' --clip_model_name "RN101" --num_of_frames 49 --clip_RN_layer_weights "0.0,0.0,1.0,1.0,0.0" --clip_fc_loss_weight "0.1" --width "1.5" --device 0
"

Capture

Could you tell me if its even worth rendering with these bad parameters.

@yudianzheng
Copy link
Owner

I believe the main parameters influencing time are the number of strokes, number of frames, and number of iterations. However, the 3-hour runtime might be due to the capability of your GPU, as the requirements of these parameters are relatively low. Unfortunately, I cannot help further since I haven't fully optimized the code's efficiency. The consist_param and frames_param mainly influence the stability or flexibility of the video, while clip_RN_layer_weights and clip_fc_loss_weight influence the semantics. I advise you to only change consist_param, frames_param, or width, and use more strokes(16, 32, 48) and iterations(like 401).

@Zegervg
Copy link
Author

Zegervg commented Jul 25, 2024

Thanks for all the help, currently renting out an rtx 3090 to experiment with this <3

@Zegervg
Copy link
Author

Zegervg commented Jul 26, 2024

Capture

Any clue what the reason of this issue could be?

@yudianzheng
Copy link
Owner

Has the program output the sketch videos yet? Is this feedback related to training the neural atlas or optimizing the sketch video?

@Zegervg
Copy link
Author

Zegervg commented Jul 26, 2024

It did not output any sketch videos. I Tried running this on my own dataset. Running the process_dataset and operate_atlas worked without any errors. But This happened when running the operate_clipavideo. It finished the first 1200 iterations and then had an error after the last 500 iterations.

@yudianzheng
Copy link
Owner

I haven't tried high iterations, like 1200, as that might cause some problems, such as exceeding the default maximum iterations. However, I think iterations higher than 800 will not make much difference. Some artifacts and poor results typically stem from the capabilities of the neural atlas and can be reduced by adjusting parameters like the number and width of strokes.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants