How to handle NaN?

[basnijholt]

(original issue on GitLab)

opened by Jorn Hoofwijk (@Jorn) at 2018-10-29T11:13:53.243Z

Suppose some function returns NaN for some input value, how should this be handled?

I think the user should at least be warned that the function is ill-behaved.

Then we could still continue learning the function but then ignoring this point for any further evaluation, so we then more or less keep those points in the pending points indefinitely, which could slow down the learner a lot if there are many points that return NaN.

Or we could simply raise an exception and terminate the runner. Which could be inconvenient if you let it run overnight and find in the morning that your learner stopped.

[basnijholt]

originally posted by Bas Nijholt (@basnijholt) at 2018-10-29T11:16:27.414Z on GitLab

The Learner1D and Learner2D currently handle NaNs, I implemented it at some point (also I am currently using this feature in a project.)

It's not tested and I don't remember exactly what happens there, but I guess it is easy to figure that out.

[basnijholt]

originally posted by Jorn Hoofwijk (@Jorn) at 2018-10-29T11:22:05.044Z on GitLab

ohw okay, in that case I should close this right?

[basnijholt]

originally posted by Bas Nijholt (@basnijholt) at 2018-10-29T11:22:39.353Z on GitLab

I think it should be tested though to make clear what should happen.