-
Notifications
You must be signed in to change notification settings - Fork 119
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
Issue 614: [DOCS] Add bayesian methods to GMM density page #642
Conversation
…ine mentioning the available models
docs/user-guide/mixture-methods.md
Outdated
@@ -4,7 +4,7 @@ Gaussian Mixture Models (GMMs) are flexible building blocks for other machine le | |||
|
|||
This is in part because they are great approximations for general probability distributions but also because they remain somewhat interpretable even when the dataset gets very complex. | |||
|
|||
This package makes use of GMMs to construct other algorithms. | |||
This package makes use of GMMs to construct other algorithms. Bayesian [BayesianGMMClassifier][bayes_gmm-classifier-api] and non-Bayesian Gaussian Mixture Models [GMMClassifier][gmm-classifier-api] are available. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I might rephrase this slightly because at this point in the docs folks are already aware of the normal GMMClassifier
.
Maybe something like "In addition to the GMMClassifier this library also features a Bayesian variant. More information can be found here"?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Updated!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Minor change.
Updated, thank you! |
I think it would make sense to mention |
Fixes issue #614: [DOCS] Add bayesian methods to GMM density pageAdded a line mentioning the available models
Before working on a large PR, please check with @koaning or @MBrouns that they agree with the direction of the PR. This discussion should take place in a Github issue before working on the PR, unless it's a minor change like spelling in the docs.
Description
Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context.
Fixes # (issue)
Type of change
Checklist:
If you feel your PR is ready for a review, ping @koaning or @MBrouns.