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

Input argument for ELBO criterion #66

Open
zanklanecek opened this issue Jun 1, 2021 · 3 comments
Open

Input argument for ELBO criterion #66

zanklanecek opened this issue Jun 1, 2021 · 3 comments

Comments

@zanklanecek
Copy link

criterion = metrics.ELBO(len(trainset)).to(device)

Your training set is divided on train and validation. Shouldn't here be (1-valid_size)*len(trainset)?

@rahulrathnakumar
Copy link

While I don't understand using the whole train set length for computing ELBO on a minibatch, what is the (1-valid_size) in your question?
Thanks

@Nebularaid2000
Copy link

I think it should be
criterion = metrics.ELBO(batch_size).to(device)
since the ELBO is calculated based on each mini-batch. Is it correct? @kumar-shridhar

@zanklanecek
Copy link
Author

While I don't understand using the whole train set length for computing ELBO on a minibatch, what is the (1-valid_size) in your question? Thanks

I don't really understand the concept, but I am certain that they further divide their trainset into train and validation. So (1-valid_size) represents the actual size of the trainset.

If the actual length of training set must be used here, then my proposal should be correct. However, if ELBO is calculated based on each mini-batch, then @Nebularaid2000 solution should be the correct one.

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