You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Using the cilk backend, I've experienced some unexplained behavior when using the train method. Sometimes when using a large dataset N = 7.5x10^6, D = 13, the EM iterations result in nonsense sparse mean vectors with large covariances. But when making copy of the dataset (data = data.copy()) before training, the result converges to meaningful mean vectors as expected.
Steps to reproduce:
initialize parameters using sklearn's kmeans++
initialize gmm specializer with diag covariance, any number of components
set components to initialized parameters.
run gmm.train(data)
get crazy mean vectors.
If I add "data = data.copy()" or anything else that causes the memory to be copied to a new location before step 4, the strange behavior doesn't occur.
Also, when loading smaller datasets this does not occur.
The text was updated successfully, but these errors were encountered:
Using the cilk backend, I've experienced some unexplained behavior when using the train method. Sometimes when using a large dataset N = 7.5x10^6, D = 13, the EM iterations result in nonsense sparse mean vectors with large covariances. But when making copy of the dataset (data = data.copy()) before training, the result converges to meaningful mean vectors as expected.
Steps to reproduce:
If I add "data = data.copy()" or anything else that causes the memory to be copied to a new location before step 4, the strange behavior doesn't occur.
Also, when loading smaller datasets this does not occur.
The text was updated successfully, but these errors were encountered: