Trial Factor and P-1 assignments squatting in Cat 0 and Cat 1 ranges

[kriesel]

Originally Posted by ATH

Would it be hard to make the server deny any TF assignments in like 53M-59M and 93M-108M ?

Set it to deny excessive-tf-depth assignments globally. Then TF assignments can't tie up any exponents that are sufficiently factored.

[ATH]

Originally Posted by kriesel

Set it to deny excessive-tf-depth assignments globally. Then TF assignments can't tie up any exponents that are sufficiently factored.

I doubt there is a limit set on all exponents that is up to date with the GPU factoring limits.
There was back in the day when only Prime95/mprime was used for factoring.

Plus it would block everyone who wants to factor deep for example in <50M range like the "under 20M unfactored exponents" project.

[kriesel]

Originally Posted by ATH

I doubt there is a limit set on all exponents that is up to date with the GPU factoring limits.
...t would block everyone who wants to factor deep for example in <50M range like the "under 20M unfactored exponents" project.

Ok, if that application of excessive TF is accepted, cap TF assignments for p>40M to no more than one bit higher than the corresponding tf target in the gpu72 line of mersenne.ca lookup for the exponent concerned, or the approximate linear interpolation of that. It's common to see random exponents at the wavefront wastefully TF 2 or 3 levels above optimal, and/or P-1 skipped, before primality testing commences.

[firejuggler]

That would be about half the GhZ cost of a prp, right? Or is it a quarter?

[S485122]

Originally Posted by kriesel

Ok, if that application of excessive TF is accepted, cap TF assignments for p>40M to no more than one bit higher than the corresponding tf target in the gpu72 line of mersenne.ca lookup for the exponent concerned, or the approximate linear interpolation of that. It's common to see random exponents at the wavefront wastefully TF 2 or 3 levels above optimal, and/or P-1 skipped, before primality testing commences.

Much simpler, instead of having the lowest unverified exponent for double-check TF and the lowest untested exponent, for first time checks factoring, set it to the lowest CAT2 exponent in each category (respecting the fact that CAT 0 and CAT1 "Not available for manual testing." (CAT2 should only be available for reliable users having signed up for getting the smallest exponents.) Why not use the existing rules (and already implemented code) applied to DC, LL, PRP and PRP-CERT ?

Jacob

[Uncwilly]

Originally Posted by S485122

Why not use the existing rules (and already implemented code) applied to DC, LL, PRP and PRP-CERT ?

That would prevent things like this assignment (in the bottom half of Cat 0) 95000533

[kriesel]

Originally Posted by Uncwilly

That would prevent things like this assignment (in the bottom half of Cat 0) 95000533

What does "that" refer to? (And firejuggler, same question.)
95000533 is already TF 2 levels higher than goal, and P-1 done rather thoroughly too. https://www.mersenne.ca/exponent/95000533
Justifiable TF level is lowered by P-1 integration into gpuowl primality testing, resulting in higher economic P-1 bounds than previously. And lowered by PRP proof reducing primality effort by ~50%.

[S485122]

Originally Posted by Uncwilly

That would prevent things like this assignment (in the bottom half of Cat 0) 95000533

Until now the rules state "Not available for manual testing."

And it could concern only untested exponents in the first test range and the unverified exponents in the double check range (for the time it will exist.)

And if adding those conditions would be too difficult, the TF of verified exponent can wait until the wavefront passed.

Then it is possible that the size of the different categories could benefit from a review.

Jacob

[chalsall]

Originally Posted by Uncwilly

That would prevent things like this assignment (in the bottom half of Cat 0) 95000533

Yup. And because this is a manual assignment, it won't expire until March of next year.

Further, because of the way TF assignments are handled, even if someone did the TF'ing to 78 (which would be silly) the assignment /still/ wouldn't be released.

[ATH]

Server should block TF in Cat 0+1 and probably Cat 2 (and maybe Cat 3?) and it should give no AID on the TF assignments either from manual assignment or through Prime95/mprime. Particularly since all the El Dorkos and morons and idiots out there are using this strategy to annoy and block progress.

Before handing out AID the server already checks the category anyway to see if the users computer requirement are met for Cat 0/1/2/3 and denies the AID if not.
I do not know how this is programmed, but logically it seems reasonable that an additional check could be put in like: IF (Cat<3 AND Assignment == TF) DENY!

[Uncwilly]

There is this batch down in the DC Cat 1 range (just above the Cat 0 level).
https://www.mersenne.org/assignments...first=1&exp1=1

ATH and S485122 have suggested server rules that would prevent this.