Yes, and invalid results need to generate a reduced daily quota eventually.
A daily quota of 1 seems to get peoples attention.
jm7
Raistmer
<[email protected]
> To
Sent by: "Jorden van der Elst"
<boinc_dev-bounce <[email protected]>, "Richard
[email protected] Haselgrove"
u> <[email protected]>
cc
BOINC Developers Mailing List
05/26/2010 11:04 <[email protected]>
AM Subject
Re: [boinc_dev] host punishment
mechanism revisited
> On Wed, May 26, 2010 at 3:31 PM, Richard Haselgrove
> <[email protected]> wrote:
>> In any event, it's pretty clear that it is taken from the canonical
>> result (validated tasks only), > so it doesn't help us with this BOINC
>> problem.
>
> But is there really a problem?
> I still don't have an answer to the question what a valid result is.
As I understood Richard answer is:
" those that are not returned immediately with an error," should be called
"success results".
"all work after validation"(successive validation) should be called "valid
results"
> Earlier, before this thread went astray into a pro-Seti forum, I opted
> for reliable hosts being the standard, instead of an optional.setting
> in the project configuration file.
Actually, when GPU comes into corrupted state, other projects could
experience same problems.
I.e., device "works" (not report errors), but makes invalid computations
(or
provides invalid data).
Invalid data for SETI most probably leads to pulses overflow.
Invalid data for some another project will lead to something different of
course, but invalid data still invalid and not usable.
_______________________________________________
boinc_dev mailing list
[email protected]
http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev
To unsubscribe, visit the above URL and
(near bottom of page) enter your email address.
_______________________________________________
boinc_dev mailing list
[email protected]
http://lists.ssl.berkeley.edu/mailman/listinfo/boinc_dev
To unsubscribe, visit the above URL and
(near bottom of page) enter your email address.
