Forum > Discussion Forum
When corrupted results get validated...
Josef W. Segur:
--- Quote from: Miep on 07 Jan 2011, 07:40:37 am ---If that's stock 6.03 with dodgy stderr showing wrong version number... maybe?
--- End quote ---
Yes, Richard recalled correctly; you need to look a few lines above where it says "Application version SETI@home Enhanced v6.03" to know the actual version number.
IIRC the only difference between 6.02 and 6.03 was an SSE folding variant which had to be commented out because it sometimes crashed.
--- Quote ---most of inconclusives are GPU -9 and some diverging signal reports plus a few where signal reported match, so something the validator checks that isn't in stderr?
alltogether lots of inconclusives from that corner :(
--- End quote ---
Yes, even when running the intended software, the CUDA cards sometimes produce false result_overflow cases. For that matter, some CPU processing does too, though that's fairly rare. I'll attach an archive with text copies of a WU page and its five task detail pages which is mind-boggling and illustrative of the weird things which can happen.
Most inconclusives get resolved with a correct result being assimilated. This thread is about cases which are exceptions to that rule, plus cases where both of the first two results are almost certainly wrong but agree.
The only thing the Validator looks for in stderr is "result_overflow" and that's only used to set a flag when the canonical result is assimilated. Aside from that, stderr could be a quote from Nietzsche and it would make no difference to validation. It's some details of the signals in the uploaded result file which are checked by the Validator.
Joe
Navigation
[0] Message Index
[*] Previous page
Go to full version