collatz_sieve_3324384911943423492096_52776558133248
log in

Advanced search

Message boards : Number crunching : collatz_sieve_3324384911943423492096_52776558133248

Author Message
Stick
Send message
Joined: 30 Apr 10
Posts: 20
Credit: 10,932,336
RAC: 48,374
Message 23990 - Posted: 6 May 2017, 15:00:32 UTC

Workunit 120284398 is probably going to disappear from the DB soon and, if so, will render this issue unanswerable. If that happens, it's OK. I am not reporting this because I missed out on some credit. I am reporting it because I think there may be a logic flaw in the Validater.

The WU had 3 tasks issued and reported: 1 - Completed and validated (issued first); 1 - Error while computing (issued second and possibly after the first's deadline); and, 1 - Completed, marked as invalid (issued after the second one errored out). The invalid one (mine) was the last to report. The valid one was a Collatz Sieve v1.20 and the invalid one was a Collatz Sieve v1.21 (opencl_amd_gpu).

My question is, how did the validater determine that mine was invalid and the other one was valid? If the two didn't match, shouldn't a tiebreaker have been issued? Maybe mine was marked invalid because it happened to be the last to report and therefore was just unneeded.


Post to thread

Message boards : Number crunching : collatz_sieve_3324384911943423492096_52776558133248


Main page · Your account · Message boards


Copyright © 2018 Jon Sonntag; All rights reserved.