Expiration date contradiction
 

So, I manually reserved an exponent to test, selecting that I only wanted world record exponents to LL test, and going in the manual extensions page ([url]https://www.mersenne.org/manual_extension/[/url]) I see that after I extended the assignment several times I should have one year to complete it.

While if I go in the assignments page ([url]https://www.mersenne.org/workload/[/url]) it says I only have 90 days to complete it.
Which of the two numbers of remaining days to complete the work is the actual one?

I may be wrong, but I'll take a stab at this.

I think the 90 days refers to how long you have to start the exponent. Once the first progress report gets sent to the server, the expiration date changes to a year.

[QUOTE=PhilF;529779]I may be wrong, but I'll take a stab at this.

I think the 90 days refers to how long you have to start the exponent. Once the first progress report gets sent to the server, the expiration date changes to a year.[/QUOTE]


Ok, but how can I let PrimeNet know that I have started to work on the exponent if I'm manual testing?

Normally Prime95 checks in with the server every day, reporting any progress on all of the exponents in the worktodo.txt file, including manual checkouts. If you have Prime95 set to not do that, or the machine doesn't have internet connectivity, then that becomes problematic.

I think all the server needs in order to give you that year for completion is that first progress report, even if you have to use a different machine to report it.

[QUOTE=PhilF;529797]Normally Prime95 checks in with the server every day, reporting any progress on all of the exponents in the worktodo.txt file, including manual checkouts. If you have Prime95 set to not do that, or the machine doesn't have internet connectivity, then that becomes problematic.

I think all the server needs in order to give you that year for completion is that first progress report, even if you have to use a different machine to report it.[/QUOTE]


Ok, now Prime95 sent the server an extimated completion date. But the server says that the days to go are 276 while it will expire in only 120 days. What is the difference between these 2 values?

[QUOTE=David703;529800]Ok, now Prime95 sent the server an extimated completion date. But the server says that the days to go are 276 while it will expire in only 120 days. What is the difference between these 2 values?[/QUOTE]

The client estimated it would take 276 days to complete the test. The client can be somewhat inaccurate depending on other things using CPU, etc. Occasionally it will calculate the time remaining while the system is under heavy load an estimate a time taking even a hundred times longer than it will.

The 120 days is the time the server is allowing to finish, according to the rules [url=https://www.mersenne.org/thresholds/]here[/url].

[QUOTE=Mark Rose;529801]The client estimated it would take 276 days to complete the test. The client can be somewhat inaccurate depending on other things using CPU, etc. Occasionally it will calculate the time remaining while the system is under heavy load an estimate a time taking even a hundred times longer than it will.

The 120 days is the time the server is allowing to finish, according to the rules [URL="https://www.mersenne.org/thresholds/"]here[/URL].[/QUOTE]


Ok, got it! Thanks to you and PhilF for the help.

[QUOTE=Mark Rose;529801]The client estimated it would take 276 days to complete the test. The client can be somewhat inaccurate depending on other things using CPU, etc. Occasionally it will calculate the time remaining while the system is under heavy load an estimate a time taking even a hundred times longer than it will.

The 120 days is the time the server is allowing to finish, according to the rules [url=https://www.mersenne.org/thresholds/]here[/url].[/QUOTE]



Sorry guys but this "expires (days)" at [url]https://www.mersenne.org/manual_extension/[/url] is disgusting since only the value at [url]https://www.mersenne.org/workload/[/url]
really matters.
Why extending a Exponent 60 days, if that has no effect at expireing?

I hate early expiring and unclear data about it on the website, because it leads to what now really means wasted computing time. ([FONT="Impact"]and no it's not an early triple check,[/FONT]:woltman:).

[URL="https://www.mersenne.org/report_exponent/?exp_lo=49299013&full=1"]49299013[/URL]

[QUOTE=moebius;530335]Sorry guys but this "expires (days)" at [url]https://www.mersenne.org/manual_extension/[/url] is disgusting since only the value at [url]https://www.mersenne.org/workload/[/url]
really matters.
Why extending a Exponent 60 days, if that has no effect at expireing?[/QUOTE]

"Disgusting" ? I'm hurt. :smile:

I added the days-to-expire estimates to certain pages as a general guideline, and it works by estimating the time-to-live based on the various assignment rules.

One thing it does not include (and I've made this clear repeatedly) is exponents that have an extension applied through that page. Reason being, it's not commonly used, and it was going to add to the complexity of the estimation calculations.

I've said that at some point I may modify it to take that into consideration, but it's just not something that has bubbled up into my to-do list.

Anyway, don't worry - if you've manually extended an assignment, that will work just fine.

The reason it was hard to estimate an expiration date in advance is that all of the code that does the actual expiration is "point in time". It analyzes each assignment to see "should this be expired?" and if so, expires the assignment and makes it available again.

Looking at an assignment and making a binary decision "expire: yes or no" is one thing. Predicting in advance exactly *when* it will expire is another thing entirely. Lots of rules, lots of "if this then that, or if this, then another thing, but if this then not that" etc.

For example, a brand new assignment has a shorter expiration time if it hasn't started yet. But once it does start, the expiration date changes. That's the simplest example, but you get the idea. Others are things like what category was it when expired, and what category is it in now? If it's moved into certain categories then it may expire sooner.

I hope that helps, and don't be frustrated, just finish your assignments in a timely manner. :smile:

Oh, and it's worth pointing out that "large" exponents (like 20-30 million above whatever current category 4 exponents) aren't going to expire anyway. There's just not a need. So people doing 100M digit checks are going to be safe for many years. That also includes people doing double-checks like 70-80M and higher. Of course a lot of those are first time checks that expired and were converted to double-checks when someone else turned in a result.

Thanks for the attention and explanation, no offense.