Numpy.ma polyfit function for masked arrays crashes on integer input

Question

The numpy polynomial fit function for masked arrays, ma.polyfit, crashes on integer iput:

import numpy.ma as ma
x = ma.arange(2)
y = ma.arange(2)
p1 = ma.polyfit(np.float32(x), y, deg=1)
p2 = ma.polyfit(           x , y, deg=1)

The last line results in an error:

ValueError: data type <type 'numpy.int64'> not inexact

Why can't I fit data with integer x-values (it's no problem with the normal numpy.polyfit function), is this a (known) bug?

lucasg · Accepted Answer · 2012-11-02T16:37:24.217

3

It is indeed a bug from numpy.ma : the rcond (a parameter to exclude some values ) takes len(x)*np.finfo(x.dtypes).eps as a default value, and np.int32 does not have any epsfield (because an int does not have a relative precision).

import numpy.ma as ma
eps = np.finfo(np.float32).eps 

x = ma.arange(2)
y = ma.arange(2)
p1 = ma.polyfit(np.float32(x), y, deg=1, rcond = len(x)*eps)
p2 = ma.polyfit(           x , y, deg=1, rcond = len(x)*eps)

I've looked quickly into numpy's issues, and this bug does not seems to figured there. It might be a good idea to raise a new issue : New Issue

edited Nov 02 '12 at 16:37

answered Nov 02 '12 at 13:38

lucasg

10,734
4
35
57

Thanks for reassuring, I have submitted a new issue. – Rolf Bartstra Nov 02 '12 at 14:10
BTW, instead of `import np.finfo(np.float32).eps as eps`, I guess you meant `eps = np.finfo(np.float32).eps` ...? :-) – Rolf Bartstra Nov 02 '12 at 14:20
it's identical : it's a question of style :p – lucasg Nov 02 '12 at 14:45
That's curious: `import np.finfo(np.float32).eps as eps` gives me a syntax error ... – Rolf Bartstra Nov 02 '12 at 15:40
oups you're right : I didn't run this part of the code. I fix it immediately. – lucasg Nov 02 '12 at 16:36

Numpy.ma polyfit function for masked arrays crashes on integer input

1 Answers1