2019-04-11, 14:36   #4
kriesel

"TF79LL86GIMPS96gpu17"
Mar 2017
US midwest

2·2,459 Posts
PRP DC reporting progress daily in V29.7, expiring in 30 days from automatic assignment anyway

Quote:
 Originally Posted by Prime95 Automatic assignments use different rules (see https://www.mersenne.org/thresholds/) Every time prime95 sends in a progress report, usually daily, the expiration date is set to 60 days in the future. This means that in most cases, as long as you do not take a two month hiatus, the exponent will not expire.
Not exactly, at least in some cases. I received in prime95 an automatic assignment after setting preference for PRP DC. Prime.log contains
Code:
[Wed Mar 27 18:15:20 2019 - ver 29.4]
Exchanging program options with server
[Thu Mar 28 03:37:00 2019 - ver 29.4]
Getting assignment from server
PrimeNet success code with additional info:
Server assigned PRP work.
Got assignment (aid redacted): PRP M79335979
Sending expected completion date for M79335979: Apr 23 2020
PrimeNet success code with additional info:
WARNING: Estimated completion date is more than one year away.  The assignment may be reassigned to another user after one year.
[Thu Mar 28 14:39:26 2019 - ver 29.4]
Updating computer information on the server
Sending expected completion date for M90094027: Mar 29 2019
Sending expected completion date for M79335979: Apr 24 2020
PrimeNet success code with additional info:
WARNING: Estimated completion date is more than one year away.  The assignment may be reassigned to another user after one year.
[Fri Mar 29 05:11:08 2019 - ver 29.4]
Sending result to server: UID: Kriesel/Parrot, M90094027 completed P-1, B1=685000, B2=12672500, E=4, Wg4: (seccode redacted), AID: (aid redacted)
...

[Tue Apr 02 15:50:33 2019 - ver 29.7]
Updating computer information on the server
Sending expected completion date for M79335979: Mar 20 2020
[Wed Apr 03 15:50:34 2019 - ver 29.7]
Updating computer information on the server
Sending expected completion date for M79335979: Mar 10 2020
[Thu Apr 04 15:50:35 2019 - ver 29.7]
Updating computer information on the server
Sending expected completion date for M79335979: Feb 27 2020
[Fri Apr 05 15:50:36 2019 - ver 29.7]
Updating computer information on the server
Sending expected completion date for M79335979: Feb 17 2020
[Sat Apr 06 15:51:21 2019 - ver 29.7]
Updating computer information on the server
Sending expected completion date for M79335979: Feb 08 2020
[Sun Apr 07 15:51:21 2019 - ver 29.7]
Updating computer information on the server
Sending expected completion date for M79335979: Jan 26 2020
[Tue Apr 09 12:11:12 2019 - ver 29.7]
Updating computer information on the server
Sending expected completion date for M79335979: Jan 22 2020
[Wed Apr 10 12:11:12 2019 - ver 29.7]
Updating computer information on the server
Sending expected completion date for M79335979: Jan 04 2020
So it is reporting in daily. Yet it is indicated now as expiring in 16 days. That expiration might be appropriate if it was a first-time test, in Cat 0, and that is how it's (incorrectly) being listed, in my assignments page. But it is a PRP DC, not PRP first test, assigned 2019-03-28, on which work began March 29 when the preceding P-1 assignment on a different exponent completed. There is a completed type 4 PRP, and a completed type 1 PRP, recorded at https://www.mersenne.org/report_expo...exp_hi=&full=1 The client software is now updated to V29.8b1. It does not indicate PRP vs PRP DC at the client. That exponent, as a Cat 4 DC per https://www.mersenne.org/thresholds/, should have up to 360 days to complete, not a mere 30.
Someone please check the scripting for handling PRP DC cases, of which there probably have been very few so far. Also please fix the database entries for this exponent.

Last fiddled with by kriesel on 2019-04-11 at 14:44