b 17, 2017 at 7:25 AM, Benjamin Merkt
wrote:
Is this still considered a bug and therefore worth an issue?
On 14.02.2017 13:34, Benjamin Merkt wrote:
Yes, the data array y was already float64.
On 14.02.2017 12:28, Vlad Niculae wrote:
One possible issue I can see causing this is if X and y
Is this still considered a bug and therefore worth an issue?
On 14.02.2017 13:34, Benjamin Merkt wrote:
Yes, the data array y was already float64.
On 14.02.2017 12:28, Vlad Niculae wrote:
One possible issue I can see causing this is if X and y have different
dtypes... was this the case for
this case! At a glance, the code
should use the correct BLAS calls for the data type you provide. Can
you reproduce this with a simple small example that gets different
results if the data is 32 vs 64 bit? Would you mind filing an issue?
Thanks,
Vlad
On Tue, Feb 14, 2017 at 8:19 PM, Benjamin Merkt
OK, the issue is resolved. My dictionary was still in 32bit float from
saving. When I convert it to 64float before calling fit it works fine.
Sorry to bother.
On 14.02.2017 11:00, Benjamin Merkt wrote:
Hi,
I tried that with no effect. The fit still breaks after two iterations.
If I set
13.02.2017 23:31, Vlad Niculae wrote:
Hi,
Are the columns of your matrix normalized? Try setting `normalized=True`.
Yours,
Vlad
On Mon, Feb 13, 2017 at 6:55 PM, Benjamin Merkt
wrote:
Hi everyone,
I'm using OrthogonalMatchingPursuit to get a sparse coding of a signal using
a dictionary le
Hi everyone,
I'm using OrthogonalMatchingPursuit to get a sparse coding of a signal
using a dictionary learned by a KSVD algorithm (pyksvd). However, during
the fit I get the following RuntimeWarning:
/usr/local/lib/python2.7/dist-packages/sklearn/linear_model/omp.py:391:
RuntimeWarning: Or
