50015437

[Mark Rose]

Exponent 50015437 looks odd to me. It has two LL results that don't match. There's a third assignment that is still progressing, but it's expired.

Why was the assignment expired if the two results don't match? The triple check still needs to be done, and it's a long way away from needed to be recycled.

[GP2]

There's a plausible explanation.

It expired after 90 days, presumably it must have failed to report in. That was back in May, before the recent changes in assignment rules. And then perhaps it suddenly did start reporting in, most recently on August 26.

As to why anyone was doing a double check of a 50M exponent in the first place, the user+machine Lelikoid,QH does have a track record of at least 14 mismatches and two verified bad results (46727689 and 47556083).


If anyone wants to DC more exponents from this user+machine:

DoubleCheck=51254857,73,1
DoubleCheck=51398881,73,1
DoubleCheck=51723127,73,1
DoubleCheck=53110229,73,1
DoubleCheck=55850857,73,1
DoubleCheck=56488879,73,1

[Mark Rose]

Originally Posted by GP2

There's a plausible explanation.

It expired after 90 days, presumably it must have failed to report in. That was back in May, before the recent changes in assignment rules. And then perhaps it suddenly did start reporting in, most recently on August 26.

As to why anyone was doing a double check of a 50M exponent in the first place, the user+machine Lelikoid,QH does have a track record of at least 14 mismatches and two verified bad results (46727689 and 47556083).


If anyone wants to DC more exponents from this user+machine:

DoubleCheck=51254857,73,1
DoubleCheck=51398881,73,1
DoubleCheck=51723127,73,1
DoubleCheck=53110229,73,1
DoubleCheck=55850857,73,1
DoubleCheck=56488879,73,1

Queued.

[Madpoo]

Originally Posted by GP2

There's a plausible explanation.

It expired after 90 days, presumably it must have failed to report in. That was back in May, before the recent changes in assignment rules. And then perhaps it suddenly did start reporting in, most recently on August 26.

You are correct sir. With my little side-task of tracking assignment check-in history, I can see that this expired assignment only started to check in results on August 23rd. when it went from zero to 60.2%.

It has checked in 3 more times since then but it went from 60.2 to 69.5% on the 2nd checkin, and has been stuck at that ever since. Not sure how it managed to check in on the 25th and 26th without moving the needle a single bit, but oh well.

There's no immediate danger of that exponent being reassigned as a DC anytime soon, so maybe he'll keep working on it and finish even though it's expired.

Your other point about that first tester having a bad track record is also spot on. The lifetime history of that system is 98 good, 49 bad (9 of those are "assumed" bad based on the other tester having an awesome record), 5 suspect. 16 exponents are still solo-checked and unknown.

For the year in question (2010), that CPU was particularly naughty with 16 good, 30 bad, 3 suspect but all of that vintage have been at least double-checked. 2011 wasn't a great year either with more bad than good. Looks like by 2012 it straightened out with 26 good, 1 bad, and then it disappears after that. Off to the great CPU recycler in the sky, I guess.