Input arrays values must be floats.

Question

Input arrays values must be floats.

javvy opened this issue 4 years ago · 4 comments

I experienced a few days of confusion because I happened to be using x-values that were type "integer"
(because they were values for "years").
That produced very bizarre results.
Eventually I realized that "locreg" assumes that the x-values ar type "float".
Multiplying my x-value array by "1.0" fixed things up.

RECOMMEND that documentation specify that the x and y input arrays need to contain type "float" values.

Answer 1 · 2021-03-17T13:10:11.000Z

Thank you for your feedback, I had not noticed this. I tried to reproduce the error, and it appeared to me that integer x and y actually worked fine, but integer x0 caused the returned values to be cast to integer. Could it be that x0 were also integer in your case? If so I have now fixed the error, and it will be fixed in the next version of localreg.

Answer 2 · 2021-03-17T13:20:36.000Z

I left x0 at the signature default, but wouldn't then have it's values set to x, which in my case are python integers? "You won't find the right answers if you don't ask the right questions!" (Robert Helmbold, 2013) On Wednesday, March 17, 2021, 06:10:29 AM MST, Sigvald Marholm ***@***.***> wrote: Thank you for your feedback, I had not noticed this. I tried to reproduce the error, and it appeared to me that integer x and y actually worked fine, but integer x0 caused the returned values to be cast to integer. Could it be that x0 were also integer in your case? If so I have now fixed the error, and it will be fixed in the next version of localreg. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or unsubscribe.

Answer 3 · 2021-03-17T13:27:57.000Z

Yes, you are right, x0 defaults to x. In that case I believe it is fixed, and I'm closing the issue.

Answer 4 · 2021-03-17T14:10:19.000Z

Thanks "You won't find the right answers if you don't ask the right questions!" (Robert Helmbold, 2013) On Wednesday, March 17, 2021, 06:28:20 AM MST, Sigvald Marholm ***@***.***> wrote: Yes, you are right, x0 defaults to x. In that case I believe it is fixed, and I'm closing the issue. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or unsubscribe.