-
Notifications
You must be signed in to change notification settings - Fork 70
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
Issues about switch off the update G #10
Comments
@wty-ustc Yes, the result is consistent with what I tried. |
Thank you for your response!
…------------------ 原始邮件 ------------------
发件人: "XingangPan/deep-generative-prior" ***@***.***>;
发送时间: 2021年4月1日(星期四) 下午3:05
***@***.***>;
***@***.******@***.***>;
主题: Re: [XingangPan/deep-generative-prior] Issues about switch off the update G (#10)
@wty-ustc Yes, the result is consistent with what I tried.
Optimizing just for latent code would produce very inaccurate reconstruction for BigGAN, even if you enlarge the learning rate. That's why we need to optimize the generator too.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.
|
it's the same with my test. How do other generators do it, is it because the training set is smaller? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When I switch off the options --update_G, to perform the reconstruction, which means only optimize the latent code, the result seems far from satisfactory, even for imagenet val datasets.
![image](https://user-images.githubusercontent.com/55389940/113243369-7602e780-92e5-11eb-91aa-ce38fb64a75f.png)
In my understanding, optimizing just for latent code might not be perfect, but at least it shouldn't be this bad.
Is that consistent with what you tried?
The text was updated successfully, but these errors were encountered: