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

Strokes on the background of the simulated image #21

Open
MandyLiuu opened this issue Dec 4, 2024 · 3 comments
Open

Strokes on the background of the simulated image #21

MandyLiuu opened this issue Dec 4, 2024 · 3 comments

Comments

@MandyLiuu
Copy link

When I use Frida, there are many meaningless strokes on the background of the simulated image. May I ask how you handle these noises?
imageData

@pschaldenbrand
Copy link
Member

Hi, good question. It is an artifact of the planner finding local minima, but there are a few tricks that sometimes help with this.

Try setting the --lr_multiplier to a larger value. Maybe 2.0 or so. This will help the strokes move around more and maybe avoid being placed in the background.

You can also increase the --init_optim_iter parameter to like 1000 or 2000 or more. This will give more optimization iterations to help the strokes move to better areas.

Hope this helps,
Peter

@MandyLiuu
Copy link
Author

MandyLiuu commented Dec 20, 2024

Thank you very much for your reply! I tried to modify the mentioned parameters and the effect was greatly improved. But as the init_optim_iter doubles, the drawing time will become very long. For example, in the case of RTX3090, num_strokes=100, and init_optim_iter=2000, it takes approximately 20 minutes to complete the painting. Do you have any inspiration to solve this problem? I will be very willing to try.

@pschaldenbrand
Copy link
Member

I'm glad that worked for you.

For speed, unfortunately the optimization process is pretty slow, and improving speed generally comes at the cost of the quality of the drawing. We don't have any implemented methods for greatly speeding up the process right now, unfortunately.

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