LL test successfully completes Double-Check of M53137907

[TheMawn]

My i5-3570k has recently started work on some double-check work. I assigned two of the four workers to DC instead to put a bit of work into that area a while ago, and the first one has started. The next will start some time during the night.

The worker that just finished reported that the LL test successfully completed the double-check. The assignment was 16 days old, and I can guarantee you with 100.00% certainty that I switched the worker to grab double-check work well after it started on M53137907. Before then, I was on Makes Sense^TM. I'm about 95% sure I never saw anything about that exponent being double-check work, and I highly doubt something in the 53 million would have been sent to me for double-check as I was automatically getting assignments.

My guess is some kind of glitch. Could it be that it thought the test was a double-check because the worker is assigned double-check work? I'll let you know tomorrow morning if my other worker which is scheduled to do DC work does the same thing.

My main concern here is that the exponent made it through only being checked the one time.


EDIT: Here is the Prime95 output

[TheMawn]

The result as it shows up on my account.

[TheMawn]

My account summary has not recorded any DC work.

[cheesehead]

Originally Posted by TheMawn

The worker that just finished reported that the LL test successfully completed the double-check. The assignment was 16 days old, and I can guarantee you with 100.00% certainty that I switched the worker to grab double-check work well after it started on M53137907.

Did you get the assignment of 53137907 manually, on the manual assignments page, or did prime95 get it automatically from PrimeNet?

Before then, I was on Makes Sense^TM. I'm about 95% sure I never saw anything about that exponent being double-check work, and I highly doubt something in the 53 million would have been sent to me for double-check as I was automatically getting assignments.

You can check on the work that has been previously done on an exponent by consulting the Exponent Status. http://mersenne.org/report_exponent/...&B1=Get+status gets the status for 53137907. That shows that two years ago, "ANONYMOUS" reported an LL on 53137907 with the same residue as yours.

My guess is some kind of glitch. Could it be that it thought the test was a double-check because the worker is assigned double-check work?

The assigned work-type has nothing to do with doublechecked status. If, when an LL result is reported, there was already an earlier LL result in its database, then it deems the second one (if the residues match, as they do in this case) to be a doublecheck report -- regardless of what keyword was in the worktodo file on the line for that exponent.

My main concern here is that the exponent made it through only being checked the one time.

As you can see on the Exponent Status report, 53137907 was indeed already LL tested, two years ago, and yours was the second, not first, LL report.

- -

Originally Posted by TheMawn

My account summary has not recorded any DC work.

Now, that's a puzzle. Maybe the TEST= work-type in worktodo does affect how your result is categorized on the account summary page, even if it makes no difference to whether PrimeNet considers the exponent to have been doublechecked.

[Prime95]

Originally Posted by TheMawn

The worker that just finished reported that the LL test successfully completed the double-check. The assignment was 16 days old, and I can guarantee you with 100.00% certainty that I switched the worker to grab double-check work well after it started on M53137907.

The first LL test had a non-zero error code. Thus, it was re-released as a first-time test.

[kracker]

But it should(unless I am missing something) display DC's on his stats? ("successfully completes Double-Check")

[TheMawn]

Alright. It doesn't really matter to me what I get credit for. As long as everything is good and the exponent isn't being pushed through without appropriate double-check work.

It comes in with en error code, so it gets re-released as a first time check. It comes in again with the same residue, so it must be correct, therefore it successfully "double-checks" the exponent even though it was sent out as a first-time LL test.

My guess is if the residue had been different, it would have registered as a first-time test.

[Brian-E]

Originally Posted by kracker

But it should(unless I am missing something) display DC's on his stats? ("successfully completes Double-Check")

I would have thought registering the work as a first time test in the personal stats, as the software indeed does, is most sensible. The assignment was granted as a first time test, and the work was regarded as a first time test while in progress due to the previous test being considered unreliable, so it would not make much sense to suddenly change the status to that of a DC just because - surprise! - the first test was correct after all. That would not be popular amongst users who are specifically interested in working at their first-time-test credit and ranking.

[cheesehead]

It seems that now, after collectively taking all relevant factors into account, we have solved all mysteries.

[TheMawn]

Bringing an old thread back rather than starting new:

When a residue is suspected of being bad or if the DC residue doesn't match, how is the user notified? I finish a DC roughly every 36 hours between my two cores and I usually just scroll back a few days and check that I get the "successfully completes" message. Would I have to find out about a bad residue through the GUI or do I get a notification on my account at mersenne.org?

[garo]

Sign into your account and in the Results Query menu choose LL Results. Once there, choose your range and don't forget to choose the radio box "Display results for user id:" and put your user-name in.