-
-
Notifications
You must be signed in to change notification settings - Fork 107
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
Beta parameter is ignored in GPVAE when using the IWAE setting #540
Comments
Hi there 👋, Thank you so much for your attention to PyPOTS! You can follow me on GitHub I have received your message and will respond ASAP. Thank you for your patience! 😃 Best, |
This issue had no activity for 14 days. It will be closed in 1 week unless there is some new activity. Is this issue already resolved? |
Still not resolved AFAIK |
Hi Alexander, Apologies for the delayed response, and thank you very much for pointing this out! At this stage, we would like to stay consistent with the official GP-VAE implementation. Additionally, there doesn't appear to be any established foundation or implementation for combining beta with IWAE. Given this, we believe the most appropriate solution would be to raise a warning when K > 1 and beta is specified, as you suggested. If you're interested in proceeding with a PR to implement this warning, we'd be happy to review it. Thanks again for your valuable contribution to improving the software! |
No problem, it's a very minor issue, I understand that it's not a priority ;). |
Issue description
In the backbone of GPVAE, a different path is taken depending on whether IWAE is used or not.
In the case K=1, the elbo is updated like this:
In the case K>1, the elbo is updated like that:
I understand that those usages are different, but it feels wrong to me to silently ignore a parameter. Also, I do not see why beta could not be applied in the IWAE case. I therefore suggest one of:
Let me know so I can propose a PR.
Thanks for the great software!
The text was updated successfully, but these errors were encountered: