This is one of the several changes it might be useful to get more eyes on to see how it fares ...
I will note that with .21 I am running: Collatz 30,028.77 NFS -1330 MW 57835 PG -101 WCG -86400 Collatz is doing some catch up, but it certain to be set to zero when its day in the sun is done ... what that will do to the other STD numbers because of normalization is hard to guess off-hand... push the other three projects hard up to plus 86400 for MW? I am not sure floating is a bad idea, just not sure it is the right cure ... only live fire will tell for sure ... On Dec 7, 2009, at 10:53 AM, David Anderson wrote: > Actually, looking at the code, we're already doing this. > The needed change is to not set the STD of non-runnable projects to zero; > instead, let them float around with the others. > > -- David > > David Anderson wrote: > ... >> >> An alternative: add the normalizing offset to non-runnable projects. >> In the above case, C's STD would go to MAX_STD, >> and it would start off on equal footing with B, >> which is the correct behavior. > _______________________________________________ > 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.
