-
-
Notifications
You must be signed in to change notification settings - Fork 985
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
[documentation: some suggestions for MLE & MAP guide] #3019
Comments
Hi @nipunbatra, those all sound like good improvements. Feel free to submit a PR. |
Thanks @fritzo I am making the above changes. I was calculating the analytical MAP and comparing with learnt MAP estimate. The learnt MAP estimate is 0.536 whereas the analytical one is 0.533. I was wondering if this is expected or if I'm doing something wrong. Can you please clarify? The analytical calculation for MAP below. Our NB -- I am also planning to add the following figure to explain existing text comparing the MAP estimate to the MLE estimate. |
I'd also seek your inputs on how to show the Autoguide to be similar/same as the custom guide in the tutorial. list(autoguide_map.named_parameters()), list(autoguide_map.named_pyro_params()) Output
The custom guide was: def guide_map(data):
f_map = pyro.param("f_map", torch.tensor(0.5),
constraint=constraints.unit_interval)
pyro.sample("latent_fairness", dist.Delta(f_map)) How should we show the equivalence?
Would appreciate your inputs on this @fritzo |
I'm not sure how to show code equivalence, but you might show parameter equivalence by printing the param store after each guide is trained: def print_param_store():
store = pyro.get_param_store()
for name, value in sorted(store.items()):
constraint = store._constraints.get(name, "real")
print(f"{name} constrained to {constraint} has value\n{value}") |
Hi,
I was going through the MLE and MAP estimation page. It is very well written. Thank you!
I had a few suggestions:
I can make a PR on the above.
Also, it may be useful to additionally show:
The text was updated successfully, but these errors were encountered: