PrimeNet Assignment Rules

[Uncwilly]

Part of the reason is to shove the manual testing assignments further away from the tail. User Sugarbeet has a bunch that are going to expire that are more than 120 days old. So they must have been Cat 3 or 4 assigned. Maybe Cat 2 should not be allowed to have manual assignments. And the rule "If manual testing, user must have signed up for the smallest exponents (see setting in green above)" should apply to Cat 3.

The Cats have "Must be completed in XX days" where:
Cat 0 = 30
Cat 1 = 60
Cat 2 = 120
Cat 3 = 240
Cat 4 = 360

My proposal to push the size of the Cats out is to make it so that those that fail the 240 days on Cat 3 don't do so into Cat 0. Rather they would do so into high Cat 1 or low Cat 2 range.

And maybe a new rule for the slowest machines still asking for LL or DC work should either:
be given PRP-CF, if they can handle it, or
be given work in a "Far Cat 4" area.
--Have the server give them exponents 30M ahead of the DC milestone, or
--- at a set point like 80M, or
--- have them working downward from 100M (picking that as a point were the PRP with Cert has dominated and DC is less needed), or
be given ECM work

The threshold for DC should be:
"Minimum Pentium 4 equivalent speed for a proven reliable computer 2,000 MHz"
vs the current 1,000. That is way too slow to not have current assignments expire on them or the to be like these 1230+ days assignments that eventually turned in:
https://www.mersenne.org/report_expo...3188601&full=1
https://www.mersenne.org/report_expo...3216419&full=1

This ancient FTC (almost 6 years) that turned into a DC, is an example of a number that should not have been given to that machine.
https://www.mersenne.org/report_expo...5701981&full=1