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

Unable to reproduce VAE-GAN results on CelebA #1

Open
akshaykulkarni07 opened this issue May 22, 2024 · 4 comments
Open

Unable to reproduce VAE-GAN results on CelebA #1

akshaykulkarni07 opened this issue May 22, 2024 · 4 comments

Comments

@akshaykulkarni07
Copy link

Hi, congratulations on your great work and acceptance to ICLR.

I was trying to reproduce the baseline VAE-GAN on CelebA but it seems that the results at the end of 50 epochs of training (with the given config file) are not as expected. See below for screenshots of 49_latent.png (generated image from sampled latent) and 49.png (generated image from real latent). There is some kind of mode collapse there, could you please advise on how to fix this?

49_latent
49

@k-eato
Copy link

k-eato commented Jun 8, 2024

Hello, I am experiencing this same problem, though in my case image quality is even worse. Any advice on what may be causing it would be greatly appreciated.

image

@adebayoj
Copy link
Collaborator

Hi @k-eato and @akshaykulkarni07. Thanks for this comment and raising this point! Apologies for our tardiness in replying to you. We just noticed this issue. We'll replicate this and get back to you. We are also working on a revamp of the code and release some of the other model classes in the paper.

@akshaykulkarni07
Copy link
Author

Hi @adebayoj, Thanks for your reply. Since the code has some issues, would it be possible for you to release the pretrained checkpoints/weights for the baseline VAE-GAN and the CB-VAE-GAN for CelebA?

@adebayoj
Copy link
Collaborator

Yes, this is definitely possible. Unfortunately, we'll have to go through some internal/legal approval to release model weights, which can actually take sometime. We are thinking of the quickest way to do that. We also want to debug the source of the issue to correct the problem. Thanks for the patience, we'll get to the bottom of this.

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

3 participants