Skip to content
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

DeprecationWarning MiniBatchKMeans #6863

Closed
stefdoerr opened this issue Jun 7, 2016 · 8 comments
Closed

DeprecationWarning MiniBatchKMeans #6863

stefdoerr opened this issue Jun 7, 2016 · 8 comments

Comments

@stefdoerr
Copy link

I am trying to cluster using MiniBatchKMeans and I am getting around 20 deprecation warnings every time. It's a bit annoying in a jupyter notebook as it fills the screen. Can you confirm this is happening for you as well?

import numpy as np
from sklearn.cluster import MiniBatchKMeans

data = np.random.rand(100,3)
mb = MiniBatchKMeans(n_clusters=5)
mb.fit_predict(data)
/shared/sdoerr/Software/anaconda3/lib/python3.5/site-packages/sklearn/cluster/k_means_.py:1279: DeprecationWarning: This function is deprecated. Please call randint(0, 99 + 1) instead
  0, n_samples - 1, init_size)
/shared/sdoerr/Software/anaconda3/lib/python3.5/site-packages/sklearn/cluster/k_means_.py:1328: DeprecationWarning: This function is deprecated. Please call randint(0, 99 + 1) instead
  0, n_samples - 1, self.batch_size)
/shared/sdoerr/Software/anaconda3/lib/python3.5/site-packages/sklearn/cluster/k_means_.py:1328: DeprecationWarning: This function is deprecated. Please call randint(0, 99 + 1) instead
  0, n_samples - 1, self.batch_size)
[...]
@jnothman
Copy link
Member

jnothman commented Jun 7, 2016

I think this has been fixed in master. Please confirm.

@jnothman
Copy link
Member

jnothman commented Jun 7, 2016

Actually, yes, fixed in #6697 6712

@jnothman jnothman closed this as completed Jun 7, 2016
@stefdoerr
Copy link
Author

Ok thanks, will wait for next release then :)

@stefdoerr
Copy link
Author

Any idea when the next release will come out? The last one was on February.

@jnothman
Copy link
Member

jnothman commented Jul 4, 2016

I've been wondering the same, actually. I think it's a discussion that should be had soon...

@dswah
Copy link

dswah commented Jul 25, 2016

Bump!

@amueller
Copy link
Member

this is not the place to bump / discuss the release schedule (it was discussed on the mailing list).

@ffffaaasl
Copy link

N

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants