Free-DC
06-23-2010, 02:32 PM
I've lowered the strictness of the validator from 10e-11 to 10e-10. I'm hoping this should significantly reduce the number of WUs flagged invalid. If the issue persists I might have to lower it farther to 10e-9. The new application will have the strictness back at 10e-11, so keep that in mind if you're compiling your own versions.
The issue we're having seems to be that the ATI 48xx GPUs and the ATI 58xx GPUs are returning different results, and if too many of either make it into the quorum they will invalidate the other results (including stock results). I'm still trying to determine if the 58xx GPU or the 48xx GPU is the one correctly validating against the stock application.
I've also updated the validator so if you check your tasks they will show what fitness they reported, so you can compare vs other tasks for the same workunit.
I'm hoping we should have this issue straightened out shortly, and thanks for your patience.
More... (http://milkyway.cs.rpi.edu/milkyway/forum_thread.php?id=1647)
The issue we're having seems to be that the ATI 48xx GPUs and the ATI 58xx GPUs are returning different results, and if too many of either make it into the quorum they will invalidate the other results (including stock results). I'm still trying to determine if the 58xx GPU or the 48xx GPU is the one correctly validating against the stock application.
I've also updated the validator so if you check your tasks they will show what fitness they reported, so you can compare vs other tasks for the same workunit.
I'm hoping we should have this issue straightened out shortly, and thanks for your patience.
More... (http://milkyway.cs.rpi.edu/milkyway/forum_thread.php?id=1647)