-
Notifications
You must be signed in to change notification settings - Fork 145
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
Low MIG values bug found & solution #64
Comments
After a bit more digging, I think the problem comes from the fact that indexes are selected but the view() operation disentangling-vae/disvae/evaluate.py Line 272 in 7b8285b
Thus I think it should be:
in place of disentangling-vae/disvae/evaluate.py Line 269 in 7b8285b
disentangling-vae/disvae/evaluate.py Line 272 in 7b8285b
|
Awesome thanks Diane, a few others had open issues for that but there was no solutions (I don't actively work on that anymore). Do you think you could send a PR ? ideally, it would use samples instead of the mean , but I think it's more urgent to have the correct permutations ! |
Let me check my code again, and I will ! I also need to do a PR just for these changes (I edited quite some stuff in the fork I created). |
I trained a beta TCVAE with the code from https://github.com/rtqichen/beta-tcvae which gives MIG for beta TCVAE of ~0.50. When computing MIG with your code with the same model (based on MLP), I had values close to 0.0008.
Differences with Chen's code I found important:
MIG values are not computed on shape in Chen's code (not considered a factor of variation). I had to modify the dsprites dataset to remove shape from dSprites lat_names, and write a custom _estimate_H_zCv function. I can share if you want.
Chen uses samples, not the mean as you do here
disentangling-vae/disvae/models/vae.py
Line 71 in 7b8285b
The most important change is I changed these lines
disentangling-vae/disvae/evaluate.py
Line 272 in 7b8285b
which are closer to Chen's code, and I get values of ~0.50 now too. I don't exactly know why the original lines where not expanding the correct way
The text was updated successfully, but these errors were encountered: