If DC categories are changed, it should be done gradually so there is enough DCTF capacity to keep up with the shifting cutoff.

It might make sense to put category 4 work two or three or more years out, and give as many years to complete, so slow computers have a good chance of finishing work before the exponents are recycled from being into the first category. Fast computers could quickly move into lower category work, so doing so won't delay verifying primes much if at all, but it will better utilize the slower computers than having their work recycled.

[QUOTE=Prime95;396337]Cat 3 with the 240 day expiration will unfortunately present a poaching target when it slips into cat 1 territory. Change the second crossover to 15000 or 20000 (or more?).[/QUOTE]

240 days for Cat 3 seems ok but why: "Must be started within 180 days". Why are they allowed 180 days before they even have to start? Wouldn't 60 or 90 days be more than enough?

[QUOTE=Prime95;396337]LL testing. We have the opposite problem, big swaths of unclaimed exponents. Change from 5000/15000 to 2500/7500???[/QUOTE]

Makes sense to me.

[QUOTE=Prime95;396337]If curtisc ever activates the trusted user bit, then we have some big adjustments to make![/QUOTE]

Indeed.

[QUOTE=Mark Rose;396344]If DC categories are changed, it should be done gradually so there is enough DCTF capacity to keep up with the shifting cutoff.[/QUOTE]

Relax... We're well ahead if the DC'ers. But, if you want to help more, take some of 40M to 72.

I used Excel to plot the cat boundaries at 2-week intervals starting March 1, 2014.

[QUOTE=ATH;396345]Why are they allowed 180 days before they even have to start? Wouldn't 60 or 90 days be more than enough?[/QUOTE]

Manual assignments.

[QUOTE=cuBerBruce;396357]I used Excel to plot the cat boundaries at 2-week intervals starting March 1, 2014.[/QUOTE]

Sweet! Thanks for that. Sincerely.

From what I can tell, Cat1 jobs must finish in 60 days and Cat3 jobs must finish in 240 days.

The reason Cat2 exists is to provide a step between Cat3 and Cat1 because THE smallest Cat3 job would end up in Cat1 within hours and this is not ideal because while it is an assignment we WISH to have finished in 60 days, it must have the promised 240 days instead.

This is only an issue if a Cat3 assignment manages to slide all the way into Cat1. As long as this takes no less than 180 days to occur, we're golden.

What is the current 180-day throughput of Cat1 + Cat2? That is what the Cat3 bound should be.

[QUOTE=cuBerBruce;396357]I used Excel to plot the cat boundaries at 2-week intervals starting March 1, 2014.[/QUOTE]

I made the same graphs in a spreadsheet, by copying the data every now and then over the past year. The idea was to see how the new rules would lead to a stable and predictable handing out of assignments over time, after cleaning up the debris left behind by the old rules. As you can see, for DC assignments that happened in September and for first time LL tests, that will take till Cat 1 assignments reaches about 61M.

[QUOTE=TheMawn;396371]This is only an issue if a Cat3 assignment manages to slide all the way into Cat1. As long as this takes no less than 180 days to occur, we're golden.[/QUOTE]

Sigh... Read the language...

Up to 240 days.

[QUOTE=tha;396377]I made the same graphs in a spreadsheet, by copying the data every now and then over the past year. The idea was to see how the new rules would lead to a stable and predictable handing out of assignments over time, after cleaning up the debris left behind by the old rules. As you can see, for DC assignments that happened in September and for first time LL tests, that will take till Cat 1 assignments reaches about 61M.[/QUOTE]

I actually read those graphs differently.

To me they clearly show that the DC parameters are short, and the LL parameters are long.

Ideally all lines should approximately follow each other with a constant gap. Clearly they don't.