-
-
Notifications
You must be signed in to change notification settings - Fork 25.8k
KernelDensity and GMM interfaces are unnecessarily confusing #4062
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
I am surprised, I would have assumed that function to give back probabilities. I'm not a huge fan of adding more methods but |
My opinion is that we should add a |
Do you have a link? |
Here's the PR: #2468 It's held-up because I can't figure out a good interface to set hyperparameters of individual fits. But you'll see in the code that there's some hacking required because of the nonuniformity of the current interfaces between |
Could we confirm here whether the new GMM implementations do this right? |
cc @tguillemot |
|
It seems a pull request simply adding |
To evaluate the density of
data
atx
, the current interface isdensity = np.exp(kde.score_samples(data))
(see in action here)
This seems really silly and unnecessary for such a common operation.
How would people feel about adding a
density
method toKernelDensity
and toGMM
to make this easier for users to figure out?The text was updated successfully, but these errors were encountered: