:|
What a pile of distortion all around...
mr_mann posted the same
in a thread at Ars.
The WU that he had was obviously one with alot of RFI, eg., a large spike. The SETI client is designed so that if the file size of the result.sah file gets beyond a certain size (meaning a very "noisey" WU), then the analysis abruptly ends and the result is sent in. This can happen anywhere from a minute or so after the beginning of processing, up to close to the average for that particular platform... It all depends on the types of things found, power of spikes, etc. You would still get credit, but this is just so you know.
Another thing that would cause these "fast WUs" would be bad RAM. A number of people here and elsewhere have reported suddenly getting a series of fast WU completions in a row and shortly thereafter, discovered to their dismay, that their RAM stick crapped out on them.
It's sad that JSI was trying to suggest something other than the above... (aside from the use of that hacked client).. :|