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
It potentially uses the wrong type (Float64, which is not necessarily the type it's working with), and also it seems to use realmin in place of eps, where eps is the appropriate value.
I want to change it to
abs(x - y) < 32 * max(eps(x), eps(y))
which is probably what was intended anyway.
The text was updated successfully, but these errors were encountered:
Okay, I now found it in the original paper, the condition there is specified as x-y == 0. The test abs(x-y) <= 32 * 1e-308 essentially accomplishes the same thing, because either x-y will be on the order of max(abs(x),abs(y))*eps(), or exactly zero, so I think this is identical, slightly roundabout way of checking x-y==0.
I mean this test:
cc03ba6#diff-9471aab4b037f803f311ca8d2d35fe8fR558
It potentially uses the wrong type (Float64, which is not necessarily the type it's working with), and also it seems to use realmin in place of eps, where eps is the appropriate value.
I want to change it to
which is probably what was intended anyway.
The text was updated successfully, but these errors were encountered: