Strategic couple and dribble checks (PRP's, P-1's, and special Certs too)

[JHagerson]

Taken.

PRP=1,2,81023053,-1,76,0
PRP=1,2,81024919,-1,76,0
PRP=1,2,81034027,-1,76,0

I requested these using manual testing, stating that they were double check PRP with proof. PrimeNet tells me that they are category zero and due in 7 days.
What should I do now?

[Jan S]

@Jhagerson: Use manual assigment, register these exponents as LL-Doublecheck(you got 180 days), and then rework worktodo.txt lines to PRP.

Worktodo.txt entry lines format: https://www.mersenneforum.org/showpo...8&postcount=22

[kriesel]

Originally Posted by JHagerson

What should I do now?

Reserve as PRP DC as you did is fine. Finish them within 180 days of assignment.

No need to do the "reserve as LLDC/manually revise to PRP/perform as PRP" shuffle, unless you are using hardware that is unusually slow that will need months to complete an assignment that a good GPU can do in hours, or even a Core2Duo can do in ~5 weeks. (Might want to save the electricity in that case, and upgrade to more efficient hardware.)
And please do not mislead the server (and indirectly, its admins, and other users) as to what work types you are running. I think that is poor practice and should be discouraged, not encouraged. If deliberately deceptive operation is not prohibited by the terms and conditions of use, maybe it should be. https://www.mersenne.org/legal/

In my experience the PRP DC assignments count down to 0 days until expiration, then show 23 or 22, and continue counting down again.
They display in https://www.mersenne.org/workload/ as if the server is treating them as first time PRP assignments, but actually expire later. The assignments listing it seems to me gets PRPDC assignment category number badly wrong. I guess there is some reason to it; a PRP on an exponent that had an LL first test is the second test, but the first PRP on it.
For example, today, among my assignments in progress:

CPU         worker      exponent    worktype  catnow  catorig    progress        assigned      last-update          ETA     daystogo   daystoexpire
eaglet	        1	66328081 	PRP	0	0	PRP, 96.77%	2023-02-15	2023-03-19	2023-03-20	1	-2
condorella	1	64112549 	PRP	0	0	PRP, 71.64%	2023-03-07	2023-03-18	2023-03-21	2	18
Manual testing	1	74296093 	PRP	0	0		        2023-03-11	2023-03-11		        	22

Obviously (as it is 2023-03-19 now), these did not actually expire in 7 days from assignment, on Feb 22 (66328081 on eaglet Core2Duo prime95 auto), March 14 (64112549 prime95 auto) or March 18 (74296093 manual assignment). Nor at 30 days after assignment, which would have been March 17 for 66328081.
I get the concern about expiration (and kudos for being responsible), but the server assignment report is not being accurate re PRP DC assignment expirations, especially in the first week after assignment.

A PrimeNet API-issued PRPDC assignment issued early today, displays as follows in the prime95 comms pane:

[Comm thread Mar 19 04:02] Getting assignment from server
[Comm thread Mar 19 04:02] PrimeNet success code with additional info:
[Comm thread Mar 19 04:02] Server assigned PRPDC work.
[Comm thread Mar 19 04:02] Got assignment (AID): PRPDC M64226807
[Comm thread Mar 19 04:02] Sending expected completion date for M64226807: Apr 16 2023
[Comm thread Mar 19 04:02] Done communicating with server.

And like this in the assignments page:

CPU         worker      exponent    worktype  catnow  catorig    progress        assigned      last-update          ETA     daystogo   daystoexpire
eaglet	        1	64226807 	PRP	0	0		        2023-03-19	2023-03-19	2023-04-16	28	7

This one won't actually expire before completion either.

[JHagerson]

Thank you for your replies.

I have an Intel Core-i3. Prime95 estimates about 17 days for each of these assignments, depending on the number of certification jobs the server sends my way.