![]() |
![]() |
#1 |
Mar 2014
22×13 Posts |
![]()
My first XXX-rated thread!
I observed this morning that one of my assignments had been expired. It was M75642647, cat 1 when I started it and cat 0 now. But it was started promptly, reported on daily (87% yesterday, 13 days after assignment), and well within the 30 day allotment. Looking at the exponent report, we see that someone else had the exponent in August, expired before I was assigned the exponent, and then turned in a result today. Nothing wrong with somebody finishing a late result; I've had that happen before. But usually that turns my LL assignment into a D assignment, but doesn't change my expiration date. This time, the result turned in was a "PRP" result rather than a "LL" result -- and apparently that does something different. Is this a bug introduced by some recent experimenting with the PRP feature? (By the time you read this, my LL test will have finished, and also appear in the exponent report.) |
![]() |
![]() |
![]() |
#2 |
Sep 2003
5×11×47 Posts |
![]()
You seemed confident that your LL test would be finished, but it's still showing only the one, unverified result. There is also no expired assignment for you.
Did your LL test finish? If so, try copy-and-pasting the relevant lines from your results.txt file to https://www.mersenne.org/manual_result/ If the server really converted your assignment to a PRP test and then threw away your result when it was completed and reported, that would be a pretty big bug. Last fiddled with by GP2 on 2017-10-02 at 17:19 |
![]() |
![]() |
![]() |
#3 |
Mar 2014
22×13 Posts |
![]()
Yes, my LL test result was submitted a few minutes after I posted. (Mine is the Gordon Bower LL showing on the exponent report now.)
When my result was submitted, my name was removed from the list of expired assignments (where it appeared most of the morning.) The bug, if there was one, afflicted the person who had the exponent before me, who had it from August 30th to September 19th and then submitted something -- I am not sure what -- early this morning. My concern is that we know what odd thing the other tester did to the exponent, and why his result submission caused the server to become confused about my assignment. (And, of course, that I don't get charged with failing to complete an exponent on time and kicked back to Category 4...) |
![]() |
![]() |
![]() |
#4 |
"Mihai Preda"
Apr 2015
2×691 Posts |
![]()
I submitted the PRP result. The story is like this: I got an LL manual assignment (there was no PRP assignment back then), did PRP on it on the GPU, then waited a while until the server was ready to accept the PRP result, and submitted the result today.
|
![]() |
![]() |
![]() |
#5 |
P90 years forever!
Aug 2002
Yeehaw, FL
24×17×29 Posts |
![]()
This is somewhat a fallout of the upcoming PRP change.
preda is the author of gpuowl which does PRP tests on Mersenne numbers. PRP residues are incompatible with LL residues. When a PRP result was checked in, the server saw that it did not need your LL result to complete the double-check and just expired it as "poached". The real problem is preda needs a good way to get PRP assignments that have never been assigned as LL (or at least unlikely to have an expired LL result returned). Also, we need to modify LL assignments to stay away from PRP tests that are recently expired and may have a PRP result unexpectedly returned. It will take time to get these rules right. As to your exponent, it can now be DCed with either a PRP test or an LL test. |
![]() |
![]() |
![]() |
#6 |
Mar 2014
22·13 Posts |
![]()
I appreciate the news from you both, and am sure that eventually all the dust will settle.
I just wanted to make sure that someone was aware there was some oddness going on. |
![]() |
![]() |
![]() |
#7 | |
Serpentine Vermin Jar
Jul 2014
52×7×19 Posts |
![]() Quote:
Vice versa too when PRP assignments are out there, making sure they're not assigned as LL in a similar situation. |
|
![]() |
![]() |
![]() |
Thread Tools | |
![]() |
||||
Thread | Thread Starter | Forum | Replies | Last Post |
Strange expiration | qingkong | PrimeNet | 3 | 2016-10-21 16:40 |
Expiration Dates | Fred | PrimeNet | 3 | 2016-02-20 08:30 |
Expiration time | NormanRKN | GPU Computing | 7 | 2013-06-28 23:53 |
LL and DC expiration times | Chuck | GPU to 72 | 8 | 2012-01-18 17:39 |
Exponent expiration | drh | PrimeNet | 25 | 2011-10-24 04:51 |