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

Discussion: Beta scheduling #32

Open
Micky774 opened this issue Feb 23, 2020 · 1 comment
Open

Discussion: Beta scheduling #32

Micky774 opened this issue Feb 23, 2020 · 1 comment
Labels
appearance Appearance module dynamics Dynamics module enhancement New feature or request Low Priority

Comments

@Micky774
Copy link
Collaborator

The overfit test got me thinking: what if we scheduled beta? If initially beta started off at 0, or at least low like .1, then throughout training leveled out at 1. I'm thinking that this may encourage the network to first learn meaningful patterns and features in the encoder, and then ramp up the task to also having a cohesive latent space. Thoughts?

@Micky774 Micky774 added enhancement New feature or request dynamics Dynamics module appearance Appearance module Low Priority labels Feb 23, 2020
@idhumphrey
Copy link

I think that before we implement this idea, it would be helpful to run experiment 10 to explore what initial beta we would want and then in that case, we could compare the results of having a scheduled beta to the best result from exp10.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
appearance Appearance module dynamics Dynamics module enhancement New feature or request Low Priority
Projects
None yet
Development

No branches or pull requests

2 participants