-
-
Notifications
You must be signed in to change notification settings - Fork 269
gaussian mixture model #102
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
Comments
This could be updated to use new |
Any reason why the cluster means can't use |
Actually, anyone mind if I update this with |
That sounds amazing and things like that are the reason there is a I am not sure how much of that was already available in latest v3 releases, but the issue is the same. A notebook is added to cover and explain a specific use case, a while later we see (or have time to implement) a way to make that case better and easier, but when the feature is added to pymc, the notebook is not updated. When that happens many users won't be aware the new feature exists, and others might now but be unable to use it without an example notebook so the new feature ends up being underused and the old but well documented way of doing things prevails. |
Great. Will put in a PR soon. |
Moving this in the notebook state tracker from 'todo' to 'done'. And closing issue |
File: https://github.com/pymc-devs/pymc-examples/blob/main/examples/mixture_models/gaussian_mixture_model.ipynb
Reviewers:
Known changes needed
Changes listed in this section should all be done at some point in order to get this
notebook to a "Best Practices" state. However, these are probably not enough!
Make sure to thoroughly review the notebook and search for other updates.
General updates
ArviZ related
Changes for discussion
Changes listed in this section are up for discussion, these are ideas on how to improve
the notebook but may not have a clear implementation, or fix some know issue only partially.
General updates
ArviZ related
Notes
Exotic dependencies
Computing requirements
The text was updated successfully, but these errors were encountered: