![]() |
|
|
#23 | |
|
Serpentine Vermin Jar
Jul 2014
1101010011102 Posts |
Quote:
|
|
|
|
|
|
|
#24 |
|
Serpentine Vermin Jar
Jul 2014
1101010011102 Posts |
Still 25 available in the 85M-86M range...
This is why the user kept getting them reassigned - they'd expire but nobody else would pick them up in the meantime until they checked in again and got the same ones because they were already in their queue. |
|
|
|
|
|
#25 |
|
Sep 2003
2·5·7·37 Posts |
That's odd. Maybe all the big guns have moved on to doing PRP instead of LL?
|
|
|
|
|
|
#26 | |
|
"TF79LL86GIMPS96gpu17"
Mar 2017
US midwest
11110100100002 Posts |
Quote:
As for myself, all primenet-connected production cpu cores have been switched to PRP. Gpus are mixed. I have a 100Mdigit LL completing tonight. Some gpus can't run PRP (gpuowl) so will stay TF P-1 and LL. Others will run PRP in the future not LL. Most cpus and gpus are running subprojects for a while yet. Gpus are manual assign only so can't get cat 0 assignments anyway. The countdown to 86M first test milestone is now 132 active (distributed among about 80 usernames) plus 20 available. Most have updated recently. Each username completing two exponents will wrap it up. Number available will probably jump again when Daniel Procopio's batch expire. Last fiddled with by kriesel on 2019-08-26 at 16:31 |
|
|
|
|
|
|
#27 |
|
Apr 2019
5·41 Posts |
I would try to grab a few, but I don't have any machines that qualify for Cat 0 yet.
Is there any way to see specifically which of the assignment requirements are met/failed for one's computers? I get up to Cat 1 currently, but one thing I'm not clear about is how the various "in the last 120 days" related rules for Cat 0 are calculated, if the computer has not been registered that long yet. Do these rules imply that the computer must have been returning results for at least 120 days? |
|
|
|
|
|
#28 |
|
"TF79LL86GIMPS96gpu17"
Mar 2017
US midwest
24×3×163 Posts |
If the LL first-test assignment expires, that should not prevent someone from getting a PRP first-test assignment on the same exponent. It may be less desirable, if the expired LL eventually completes, to have differing type runs. And that issue also can arise with PRP residue types. But the higher reliability of PRP/GEC is likely worth it.
|
|
|
|
|
|
#29 |
|
P90 years forever!
Aug 2002
Yeehaw, FL
17×487 Posts |
It is for that exact reason that rules are in place to prevent PRP testers from getting expired LL assignments. I'd have to look at the server's PHP code for the exact rule. I presume a PRP tester could get the assignment if the expiration on the LL test was several months ago (won't happen for a cat 0 assignment).
|
|
|
|
|
|
#30 |
|
Jul 2017
168 Posts |
I like to test Mp with (p+1)/6=p* for prime p*
|
|
|
|
|
|
#31 |
|
"Sam"
Jun 2019
California, USA
478 Posts |
I noticed one of my machines recently completed a PRP of an exponent below 90M that got expired from this user: 89773741. This is the only Cat 0 PRP assignment I'm aware of that any of my Prime95 machines ever received from PrimeNet.
A quick check within the GIMPS Milestones page revealed 6 exponents under 90M assigned to this user back in July last year, with 5 of them showing blank under the "Stage, %" column, along with ETA (days) all in the -240 range. Are these OK from GIMPS perspective? It seems to me this user may interfere with the timely completion of an upcoming milestone for GIMPS: "All exponents below 90 million tested at least once". I'm just curious as to whether anything can be done about such "zombie" exponents. |
|
|
|
|
|
#32 |
|
"TF79LL86GIMPS96gpu17"
Mar 2017
US midwest
24·3·163 Posts |
Well, then, TEST them already. Or unreserve them, so someone responsible can finish them.
It's counterproductive to hoard them and do little or nothing with them for several months, keep them reserved until they expire, renew them, again do nothing with them, hoard yet longer, etc. Code:
Exponent Work Type Stage % expires (days) ETA (days) Assigned Last update Next update Completion User 89900149 PRP 14 -250 2019-07-08 2020-03-02 2020-04-25 2019-07-14 patgie 89906359 PRP PRP, 8.80% 16 -247 2019-07-10 2020-03-02 2020-04-28 2019-07-17 patgie 89903273 PRP 17 -245 2019-07-11 2020-03-02 2020-04-28 2019-07-19 patgie 89935537 PRP 21 -244 2019-07-15 2020-03-02 2020-04-30 2019-07-20 patgie 89936059 PRP 21 -244 2019-07-15 2020-03-02 2020-04-30 2019-07-20 patgie 89986801 PRP 29 -236 2019-07-23 2020-03-18 2020-05-08 2019-07-28 patgie Last fiddled with by kriesel on 2020-03-20 at 18:44 |
|
|
|
|
|
#33 | |
|
May 2011
Orange Park, FL
25×29 Posts |
Quote:
|
|
|
|
|
![]() |
Similar Threads
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| Add repeated digits after a number until it is prime | sweety439 | sweety439 | 74 | 2022-05-17 19:28 |
| Completed assignments still in GPU72 Assignments page | kladner | GPU to 72 | 3 | 2019-06-15 01:19 |
| Assignments Completed by Another User | linament | PrimeNet | 99 | 2015-08-26 21:40 |
| x86 Microcode Execution Unit and repeated-address implied loads | ewmayer | Hardware | 8 | 2014-10-07 08:17 |
| Trivial bug: repeated PM notifications | Christenson | Forum Feedback | 0 | 2011-03-21 03:49 |