[QUOTE=Madpoo;518132]Hmmm.... maybe it's due to the difference in what is considered "optimally" TF'd between CPUs and GPUs.[/QUOTE]

Regardless, it might be a good idea for Primenet to sort by TF level desc when people ask for specific ranges.

For "nominal" P-1 assignments, the TF'ers are keeping comfortably ahead of having candidates being "optimally TF'ed". But for specialized requests, not a lot of candidates are thusly worked. Please see [URL="https://www.mersenne.ca/status/tf/0/0/3/9000"]this report[/URL] on James' site.

P.S. I understand that Primenet currently does something like this for LL assignments, in that it sorts by P-1'ed desc, grouped by 1M range. Although this hasn't actually been needed for several years now because of the specialized TF'ers and P-1'ers.

[url]www.mersenne.org[/url] looks down or not reachable.

[QUOTE=ET_;518200][url]www.mersenne.org[/url] looks down or not reachable.[/QUOTE]

It is fine from here and right now.

[QUOTE=chalsall;518135]Regardless, it might be a good idea for Primenet to sort by TF level desc when people ask for specific ranges.

[/QUOTE]

On the manual GPU assignment page, there is a work preference box that allows the requester to select "what makes sense", highest bit levels, lowest bit levels, lowest exponents or highest exponents. This option provides a lot of flexibility to manual workers. For instance, it has allowed me to fine tune my TF reservations so that I can stay just ahead of (or perhaps out of the way of) the GPU72 effort. That same option on the manual P-1 reservation page would make it convenient to reserve adequately TFed exponents for P-1 work.

[QUOTE=Uncwilly;518207]It is fine from here and right now.[/QUOTE]

It had a hiccup... or I had. :smile:

PRP Not Expiring
 

It seems that some PRP assignments are not following the expiration rules.

[QUOTE=gjmccrac;518600]It seems that some PRP assignments are not following the expiration rules.[/QUOTE]Those may have been reserved before expiration began being applied to PRP assignments. If I recall correctly, Madpoo stated expiration is recorded in the database for each assignment, including effectively "no expiration". But yeah, eventually that will be a problem with orderly progress in general, and with reaching minor milestones.

[QUOTE=kriesel;518626]Those may have been reserved before expiration began being applied to PRP assignments. If I recall correctly, Madpoo stated expiration is recorded in the database for each assignment, including effectively "no expiration". But yeah, eventually that will be a problem with orderly progress in general, and with reaching minor milestones.[/QUOTE]

The problem I had when I added the "days to expire" to the website was that it's so stinkin' hard to estimate when that'll actually be. :smile:

The only surefire way of knowing when an exponent will expire is immediately after it expires. And that happens every day at just after 23:00 UTC.

I tried to take all of the rules into account, to try and predict on what day the *many* clauses in the nightly task will all align to boot the assignment.

One thing I haven't factored into it is when someone uses the website to manually extend their assignment. Doing that will give it some extra time before it expires, but I haven't poked at that too much. Not many people use it, or if they do, it's not generally in the range of some milestone people are paying attention to, so I just didn't bother. LOL

And with PRP, I wasn't sure at first if the daily expiration task was using the same rules or not. I think it is, so I'm using the same expiration estimates, but maybe they do have slightly different conditions on whether it will or will not expire.

Honestly, it'd be a TON simpler for me if the expiration date was set in stone at the time the assignment was made, and recorded as such. But expirations are fluid, based on what "category" it happens to be in.

Consider for example this clause in the first-time test rules:
[QUOTE]Assignments are recycled if assignment is not started within 90 (unless manual testing) days or when the exponent moves midway into the first category and the assignment is more than 360 days old.[/QUOTE]

Now how the heck do you estimate the expiration in advance? You can't. :smile:

Unable to manually reserve exponent for P-1
 

I an unable to manually reserve [URL="https://www.mersenne.org/report_exponent/?exp_lo=97232917&full=1"]this exponent[/URL] for P-1 factoring? Any ideas?

A very minor issue. I believe this has been mentioned before, but exponents with a composite P-1 factor do not show up under the Recent Cleared list.

[QUOTE=ixfd64;521700]A very minor issue. I believe this has been mentioned before, but exponents with a composite P-1 factor do not show up under the Recent Cleared list.[/QUOTE]For reference, [i]ixfd64[/i]'s recent composite factor for [M]57051389[/M]