-
Notifications
You must be signed in to change notification settings - Fork 74
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
Potentially rewrite constraint functions for bayesian layers #53
Comments
edward-bot
pushed a commit
that referenced
this issue
Nov 13, 2019
Fixes #53. PiperOrigin-RevId: 280257372
edward-bot
pushed a commit
that referenced
this issue
Nov 15, 2019
See more details in ed.initializers' docstring. Fixes #53. PiperOrigin-RevId: 280257372
edward-bot
pushed a commit
that referenced
this issue
Nov 15, 2019
See more details in ed.initializers' docstring. Fixes #53. PiperOrigin-RevId: 280257372
edward-bot
pushed a commit
that referenced
this issue
Nov 15, 2019
See more details in ed.initializers' docstring. Fixes #53. PiperOrigin-RevId: 280257372
edward-bot
pushed a commit
that referenced
this issue
Nov 15, 2019
See more details in ed.initializers' docstring. Fixes #53. PiperOrigin-RevId: 280257372
edward-bot
pushed a commit
that referenced
this issue
Nov 15, 2019
See more details in ed.initializers' docstring. Fixes #53. PiperOrigin-RevId: 280570568
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We currently adopt Keras' practice of unconstrained parameters followed by projected gradient descent. It's more common in probabilistic modeling code to constrain the parameter space itself, e.g.,
ed.Normal(0., tf.nn.softplus(tf.Variable(1.)) + tf.keras.backend.epsilon())
. This is subtle but potentially an impactful change so we should be careful with our ablation studies if we want to change this behavior.The text was updated successfully, but these errors were encountered: