-
Notifications
You must be signed in to change notification settings - Fork 112
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Dot verification fails with single precision #20
Comments
We currently check that the
Option 1 is simple but might hide errors. If the arrays contain correct values, then as long as the reduction is close for this benchmark it might be suitable. |
Would it be possible to make the "sum" has double datatype irrespective of input args, "double or float" so that it gives accurate results. |
For devices which do not support double precision would this not pose a problem? |
Hi, |
Yes, but we've not come up with a satisfactory solution yet. |
Thanks for your reply. Am I right in assuming that despite the verification failing, my measurements are still valid? |
If it's just the reduction that fails (dot), and the other kernels are OK then the contents of the arrays should be correct. If the result is close enough on inspection but fails because of the tolerance then it's probably fine. If the result is 0.0 or some other nonsense number then it might have done something really wrong... |
Alright, thanks a lot! |
@zjin-lcf suggested using different tolerances for the reduction result based on the data type (option 1 above). |
Whilst reviewing #186 we discussed the fact that the |
We probably just need to increase the tolerance. The error will also be proportional to the size of the arrays (unlike with the other kernels), so we need to make sure whatever error checking tolerance we use is robust enough to avoid these sorts of false positives for any sort of input.
The text was updated successfully, but these errors were encountered: