I'm still showing three assignments that potentially will expire. Take for example 38442727. This was assigned as a Cat 3 on April 24, originally with a 180 day expiration period (which was fine and would have been completed within that time period). Now it is a Cat 2 showing expiration in 84 days which on my older desktop is in danger of expiration.

I will shift that assignment to a faster machine, but all these changes in expiration dates are a hassle. I don't want to have an assignment working and then lose the work on it due to expiration.

I have days of work set to greater than 10, but I get Cat 3 assignments that change into Cat 2 within a day or two. What I really want is an option to get Cat 4 assignments so I can just let everything handle itself. Thanks!

[QUOTE=richs;435132]I will shift that assignment to a faster machine, but all these changes in expiration dates are a hassle. I don't want to have an assignment working and then lose the work on it due to expiration.[/QUOTE]

This shouldn't be happening.

The [URL="http://www.mersenne.org/thresholds/"]assignment rules[/URL] are very clear that the expiry is based on what category the assignment was in *at assignment time*. It doesn't matter if a Cat 3 almost immediately becomes a Cat 2 -- that assignment still has 270 days to complete, and further, must have moved into Cat 1 before it will be recycled.

Probably (hopefully) this is simply an issue of the reporting code not correctly and/or fully codifying the human language (the contract).

[QUOTE=richs;435132]Take for example 38442727. This was assigned as a Cat 3 on April 24, originally with a 180 day expiration period (which was fine and would have been completed within that time period). Now it is a Cat 2 showing expiration in 84 days which on my older desktop is in danger of expiration.[/QUOTE]

Doh! I should try to pay more attention!

What [URL="http://www.mersenne.org/assignments/?exp_lo=38442727&exp_hi="]is being reported is mostly correct[/URL]. It is showing it will expire in 84 days because it hasn't started yet. "Assignments are recycled if assignment is not started within 90 [days]". Edit: Seems like the report is 30 days off (in the client's favour).

Once "home2000" reports even a tiny bit of progress the expiry should jump up to 270 days from the date of assignment. And even then it won't be recycled until it is the 8,500th lowest first-time untested candidate.

[QUOTE=retina;435118]I think richs question highlights a problem. Shouldn't users be able to know from day 1 the amount of time they have to complete the assignment? All the uncertainty about when things expire is disappointing.[/QUOTE]

But they do... [URL="www.mersenne.org/thresholds/"]www.mersenne.org/thresholds/[/URL]

The fact that they get a grace period until it reaches midway through category 1 is irrelevant. :smile:

[QUOTE=richs;435132]I'm still showing three assignments that potentially will expire. Take for example 38442727. This was assigned as a Cat 3 on April 24, originally with a 180 day expiration period (which was fine and would have been completed within that time period). Now it is a Cat 2 showing expiration in 84 days which on my older desktop is in danger of expiration.

I will shift that assignment to a faster machine, but all these changes in expiration dates are a hassle. I don't want to have an assignment working and then lose the work on it due to expiration.

I have days of work set to greater than 10, but I get Cat 3 assignments that change into Cat 2 within a day or two. What I really want is an option to get Cat 4 assignments so I can just let everything handle itself. Thanks![/QUOTE]

In the case of [URL="http://www.mersenne.org/assignments/?exp_lo=38442727"]M38442727[/URL] it's because you haven't started it yet. The "% done" is zero.

Here is what the assignment rule page says for category 3 double-checking:
[QUOTE]Assignments are recycled if assignment is not started within 120 (unless manual testing) days or when the exponent moves midway into the first category and the assignment is more than 240 days old.[/QUOTE]

It was assigned 36 days ago and since it hasn't started yet, will expire in another 84 days.

But once you [B]do[/B] start it, that expiration time will "clear".

Just understand that assignments can expire for different reasons...
[LIST=1][*]Because it hasn't started in the # of days specified since being assigned (120 days for cat 3 DC)[*]The CPU hasn't checked in for a certain # of days (only for cat 0/1 assignments)[*]Because it moved into category 1 and the total-time rule goes into effect (240 days for cat 3 DC)[/LIST]
In other words, to boil it all down, you do have 240 days, but you have to start within 120 days (and let the server know you started, obviously). :smile:

Does that make more sense, hopefully? Sorry for any confusion or concern.

Doh! Ninja'd by madpoo

[QUOTE=chalsall;435148]Once "home2000" reports even a tiny bit of progress the expiry should jump up to 270 days from the date of assignment. And even then it won't be recycled until it is the 8,500th lowest first-time untested candidate.[/QUOTE]

FYI, the "midway into the first category" rule means this (I had to look at how it was implemented to make sure)

Look at the cat 0 threshold (currently 36266120 for double-check). Then look at the cat 1 threshold (currently 37345412).

The midway point is merely (cat 0 limit + cat 1 limit) / 2 = 36805766

So as of this minute, everything below 36805766 falls under the new "midway into cat 1" rule. Helpful?

It's not (as I first thought, like you perhaps) the point at which half of the assignments are above/below. Which I was glad for, because that would have been more work to figure out. :smile:

[QUOTE=sdbardwick;435151]Doh! Ninja'd by madpoo[/QUOTE]

Double Doh! Yeah, I was reading the LL rules rather than the DC rules.

I'm going to go back to my garden now.... :smile:

[QUOTE=Madpoo;435150]

In other words, to boil it all down, you do have 240 days, but you have to start within 120 days (and let the server know you started, obviously). :smile:
[/QUOTE]

Maybe add a superscript * footnote to the report indicating that the expiration time will increase once the assignment starts?

[QUOTE=Madpoo;435150]It was assigned 36 days ago and since it hasn't started yet, will expire in another 84 days.

But once you [B]do[/B] start it, that expiration time will "clear".[/QUOTE]And there is the confusing part. Two expiry dates. But reports only show one expiry date. I was also confused by this. I understand now, but so many others that don't read here probably won't understand.

[QUOTE=retina;435180]And there is the confusing part. Two expiry dates. But reports only show one expiry date. I was also confused by this. I understand now, but so many others that don't read here probably won't understand.[/QUOTE]

maybe call it the gtil date ? short for get to it or lose it