GPU to 72 spider poaching exponents?
 

I recently retired my mother's laptop from GIMPS as the computer was rarely used. I let the computer finish its remaining assignments (two double checks) before leaving the project.

When I went to check the results, I noticed that "For Research" had already submitted a double check for M31,370,891 with a matching residue:

[code]
Verified Sova 5AA6D1E1E56B3B5
Verified 2014-06-25 For Research 5AA6D1E1E56B3B52
Verified 2014-07-08 ixfd64 5AA6D1E1E56B3B52[/code]

From what I understand, For Research is the name of the GPU to 72 spider and isn't supposed to submit results. So I'm wondering: is this some sort of bug in which GPU to 72 is (re-)submitting results? Or did someone poach my assignment and try to pin it on the GPU to 72 spider?

It's not a big deal as I got still got credit for the assignment, and that a triple check is overall better than a double check, but I'm still curious as to what happened.

Had the exponent expired?

[QUOTE=ixfd64;379165]From what I understand, For Research is the name of the GPU to 72 spider and isn't supposed to submit results.[/QUOTE]

Half true.

"For Research" is my personal account which is "trusted" by Primenet, which GPU72 uses to collect expired exponents. Thus, results from that account will be seen very regularly.

[QUOTE=ixfd64;379165]So I'm wondering: is this some sort of bug in which GPU to 72 is (re-)submitting results? Or did someone poach my assignment and try to pin it on the GPU to 72 spider? It's not a big deal as I got still got credit for the assignment, and that a triple check is overall better than a double check, but I'm still curious as to what happened.[/QUOTE]

GPU72 is definitely not "resubmitting" results. It's not cheating.

All I can tell you is what I can see:

[CODE] 31370891 D LL, 79.80% 384 71 2014-06-11 2014-04-01 2014-03-31 2013-03-13 ixfd64 chiousheng-pc
31370891 D LL, 80.90% 388 67 2014-06-11 2014-04-06 2014-04-05 2013-03-13 ixfd64 chiousheng-pc
31370891 D LL, 82.70% 395 1 2014-04-13 2014-04-11 2014-04-10 2013-03-13 ixfd64
31370891 D LL, 83.20% 399 2 2014-04-18 2014-04-15 2014-04-14 2013-03-13 ixfd64
31370891 D LL, 83.40% 403 1 2014-04-21 2014-04-19 2014-04-18 2013-03-13 ixfd64
31370891 D LL, 85.50% 410 2 2014-04-29 2014-04-26 2014-04-25 2013-03-13 ixfd64
31370891 D LL, 86.20% 413 2 2014-05-02 2014-04-29 2014-04-28 2013-03-13 ixfd64
31370891 D LL, 86.30% 415 2 2014-05-04 2014-05-01 2014-04-30 2013-03-13 ixfd64
31370891 D LL, 86.60% 419 3 2014-05-09 2014-05-06 2014-05-05 2013-03-13 ixfd64 chiousheng-pc
31370891 D LL, 86.70% 424 2 2014-05-13 2014-05-10 2014-05-09 2013-03-13 ixfd64 chiousheng-pc
31370891 D LL, 87.20% 430 2014-05-17 2014-05-14 2014-05-13 2013-03-13 ixfd64 chiousheng-pc
31370891 D LL, 87.80% 438 3 2014-05-28 2014-05-25 2014-05-24 2013-03-13 ixfd64 chiousheng-pc
31370891 D LL, 90.00% 448 2 2014-06-06 2014-06-04 2014-06-03 2013-03-13 ixfd64 chiousheng-pc
31370891 D LL, 91.70% 457 1 2014-06-14 2014-06-12 2014-06-11 2013-03-13 ixfd64 chiousheng-pc
31370891 D LL, 93.30% 467 -2 2014-06-21 2014-06-19 2014-06-18 2013-03-13 ixfd64 chiousheng-pc
[/CODE]

Possibly this was reassigned to one of my machines.