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
If the ground-truth execution returns NaN or -NaN, then no matter what the other executables return, the default comparison function will always return either NaN or -NaN.
Not only is this value weird and unintuitive, but it breaks the bisect algorithm. If it weren't for the bisect algorithm, I would say this is not an issue, as it is kind of weird if your baseline code is returning NaN.
However, for the sake of bisect, and therefore for always and forever, the default case shall be to say that if the ground-truth is NaN or -NaN, then return 0.0 if the baseline is the same sign of NaN. That is to say, as far as FLiT is concerned in the default case, NaN == NaN and -NaN == -NaN.
The text was updated successfully, but these errors were encountered:
If the ground-truth execution returns
NaN
or-NaN
, then no matter what the other executables return, the default comparison function will always return eitherNaN
or-NaN
.Not only is this value weird and unintuitive, but it breaks the bisect algorithm. If it weren't for the bisect algorithm, I would say this is not an issue, as it is kind of weird if your baseline code is returning
NaN
.However, for the sake of bisect, and therefore for always and forever, the default case shall be to say that if the ground-truth is
NaN
or-NaN
, then return0.0
if the baseline is the same sign ofNaN
. That is to say, as far as FLiT is concerned in the default case,NaN == NaN
and-NaN == -NaN
.The text was updated successfully, but these errors were encountered: