[QUOTE=kriesel;554491]There is a clash between the maximum bit level that manual tf will allow (85), and the GPU72 listed final bit level at mersenne.ca (86) for high exponents in the mersenne.org range.[/QUOTE]I wouldn't worry about it. TF levels are still being re-evaluated (with regards to PRP-proof rebalancing), and by the time the 990M range becomes relevant I'm sure things will have changed half a dozen ways. Target TF may drop by one bitlevel in the near(ish) future. I'm perfectly content to leave the mersenne.org pages capped at 85. If somebody [i]really[/i] wants to TF to such depths I'm sure they'll figure out a way.

[QUOTE=James Heinrich;554493]I wouldn't worry about it. TF levels are still being re-evaluated (with regards to PRP-proof rebalancing), and by the time the 990M range becomes relevant I'm sure things will have changed half a dozen ways. Target TF may drop by one bitlevel in the near(ish) future. I'm perfectly content to leave the mersenne.org pages capped at 85. If somebody [I]really[/I] wants to TF to such depths I'm sure they'll figure out a way.[/QUOTE]Not worried, just thought it was interesting. It seems to only affect from ~956M up. It's easy enough to manually edit the last digit of a manual assignment. And performing these will be rare for quite some time.

On my assignments page at [url]https://www.mersenne.org/workload/[/url] I have two Manual testing PRP assignments from PRP-DC via gpuOwl that say they are original and current cat 0 and now expire in 3 days. However, when I go to [url]https://www.mersenne.org/manual_extension/[/url] to extend them, that table says they have an age of 4 days and expire in 176 days. Which is correct? Should I extend them? They will take about 4 more days to complete.

[QUOTE=frmky;556695]On my assignments page at [url]https://www.mersenne.org/workload/[/url] I have two Manual testing PRP assignments from PRP-DC via gpuOwl that say they are original and current cat 0 and now expire in 3 days. However, when I go to [url]https://www.mersenne.org/manual_extension/[/url] to extend them, that table says they have an age of 4 days and expire in 176 days. Which is correct? Should I extend them? They will take about 4 more days to complete.[/QUOTE]

I would trust the workload page. I'd extend them and hope it works.

Done. The extension page now says 236 days but the workload page still says 3 days. It's for 83877517 and 83878189.

[QUOTE=frmky;556697]Done. The extension page now says 236 days but the workload page still says 3 days. It's for 83877517 and 83878189.[/QUOTE]

I guess the workload page is thinking those are first-time tests whereas they are DCs.

[QUOTE=Prime95;556698]I guess the workload page is thinking those are first-time tests whereas they are DCs.[/QUOTE]A long outstanding issue. Separate thread started in January: [URL]https://www.mersenneforum.org/showthread.php?t=25066[/URL]
November: [URL]https://www.mersenneforum.org/showthread.php?t=24942[/URL]

My workload page shows this assignment expiring in -109 days and is indicated as cat 0 there:
[URL]https://www.mersenne.org/report_exponent/?exp_lo=83023643&full=1[/URL]
And the extensions page says it has 60 days before expiration.
According to [URL="https://www.mersenne.org/thresholds/"]assignment rules[/URL], it should be a CAT 4 PRP DC, and so presumably display and be treated as one.

(Please don't poach DC, especially of active reliable users; [URL]https://www.mersenne.org/report_exponent/?exp_lo=82972553&exp_hi=&full=1[/URL] was nearly 35% complete, and next in line to be resumed after completion in less than one more week, of two unintended 54M LLDC forced on it from V30.x updates. There's plenty of available LLDC or PRP DC to do for everyone, no need or justification to poach PRP DC assignments tens of millions away from the DC wavefront, costing/wasting system-weeks or months per poached exponent of a slow i3. On the laptop posting this message that's used daily. That one case 82972553 represents 2 months wasted on the laptop. PRP DC work type was selected both so that the slow system would remain far ahead of any wavefront, and aid in the accumulation of error rate data for PRP/GEC.)
[URL]https://www.mersenne.org/report_prp/?exp_lo=2&exp_hi=999999999&exp_date=&end_date=&user_only=0&user_id=&exdchk=1&dispdate=1&exbad=1&exfactor=1&B1=[/URL] will return lots of potential DC. Those I spot checked would not involve poaching.

Excluding doublecheck done, gives a list of active assignments, led off by PRP DC with pending/overdue doublecheck assignments (NOT expired, many are checking in regularly.) [url]https://www.mersenne.org/assignments/?exp_lo=55616930&exp_hi=999999999&execm=1&exdchk=1&exp1=1&extf=1[/url]

The numbers on the Exponent Status Distribution page don't tally
 

On the [url=https://www.mersenne.org/primenet/]Exponent Status Distribution[/url] page the numbers don't tally for the 3M, 4M, 6M, 7M and 10M ranges. (The number of exponents is not equal to the total of the number of primes, composites and unproven.) There is even an exponent that would be unproven : it has a 1 in the "Unproven / ERR" column, although all exponents that haven't been factored have been at least double checked.

Jacob

Correct. I had also noticed that. No action yet, tho.

[QUOTE=S485122;557539]On the [url=https://www.mersenne.org/primenet/]Exponent Status Distribution[/url] page the numbers don't tally for the 3M, 4M, 6M, 7M and 10M ranges. (The number of exponents is not equal to the total of the number of primes, composites and unproven.) There is even an exponent that would be unproven : it has a 1 in the "Unproven / ERR" column, although all exponents that haven't been factored have been at least double checked.

Jacob[/QUOTE]

Blame it on PRP proofs. Before, exponents were in one of a several tables. Now, while waiting for a proof to be uploaded the exponent is in none of those tables. It will get patched up someday.