|
I just noticed that this result's stderr.txt output didn't quite match up to that of other sieving workunits I've crunched--whereas all the others said either "factors file found" or "factors file not found" at the end of their stderr.txt, the one linked to above didn't. Is this a potential bug?
Also, I've noticed that the aforementioned WU and all the others I've received to crunch after it have had a quorum of 1, whereas before all sieving workunits had a quorum of 2; is this a change made to all the sieving workunits in general, or just an error made with those workunits? I know that over at Riesel Sieve I heard that since they can validate sieve results quickly and easily without doublechecking them, they only needed a quorum of 1 (especially since they use fixed credit), but I figured I'd ask here anyway in case it's different.
And while I'm at it, here's another question about the new sieving workunits: I've noticed that the workunit that I had linked to at the beginning of this post was granted more than half a credit more than the previous sieving workunits that I'd crunched. Is this intentional? It looks like the sieving app here has fixed credits (IMO a good thing since it is just about the only foolproof way to stop cheating), so the only cause I can imagine for this is a raise of the fixed credit by the admins; is this the case? (FYI, all of the credits I've gotten for sieve workunits have been more than my client's claim, anyway.)
____________
 | 
