[QUOTE=Uncwilly;382927]The count down number for proving M44 went through 200 in the last week and has been dropping quickly.[/QUOTE]Time for a full check-point update:

All exponents below [B]32,593,019[/B] have been tested and double-checked.
All exponents below [B][COLOR="Red"]51,646,879[/COLOR][/B] have been tested at least once.

Countdown to testing all exponents below M([B][COLOR="Blue"]57885161[/COLOR][/B]) once: 5,924
Countdown to double-checking all 2[SUP]P[/SUP]-1 smaller than 10M digits: [B][COLOR="Red"]72[/COLOR][/B] (Estimated completion : [COLOR="Blue"]2015-03-06[/COLOR])
Countdown to proving M([COLOR="Green"]37156667[/COLOR]) is the [COLOR="green"]45[/COLOR]th Mersenne Prime: 62,119

I question the utility of the estimated completion. It is almost certainly wrong. And even if all involved clients are perfect in their estimates (which itself is very unlikely) there are still those impatient poachers that will blast through the last few exponents thus making the time estimate meaningless.

[QUOTE=retina;387287]I question the utility of the estimated completion. It is almost certainly wrong. And even if all involved clients are perfect in their estimates (which itself is very unlikely) there are still those impatient poachers that will blast through the last few exponents thus making the time estimate meaningless.[/QUOTE]
Yes, the estimated date of completion should not be trusted for all clients. Here are the relevant lines of output of my current DC. The progress has been steady over the two months, the test is currently 62% complete, and it should therefore finish around 20 December. The chaotic estimated completion dates may be explained either by the fact that I run a fairly old version of mprime (v 26.5) (perhaps the handling or the rolling average has since been improved) or that my machine only runs a few hours per day, but I don't think either circumstance will be particularly unusual.

[CODE][Wed Sep 10 21:04:50 2014 - ver 26.5]
Sending expected completion date for M35614801: Jul 3 2015
[Fri Sep 12 00:37:14 2014 - ver 26.5]
Sending expected completion date for M35614801: Jul 2 2015
[Sat Sep 13 09:32:30 2014 - ver 26.5]
Sending expected completion date for M35614801: Jan 27 2015
[Sun Sep 14 09:32:31 2014 - ver 26.5]
Sending expected completion date for M35614801: Jan 26 2015
[Mon Sep 15 09:32:32 2014 - ver 26.5]
Sending expected completion date for M35614801: Jan 21 2015
[Tue Sep 16 09:32:33 2014 - ver 26.5]
Sending expected completion date for M35614801: Jun 25 2015
[Wed Sep 17 09:32:34 2014 - ver 26.5]
Sending expected completion date for M35614801: Jun 25 2015
[Thu Sep 18 09:32:35 2014 - ver 26.5]
Sending expected completion date for M35614801: Jun 22 2015
[Fri Sep 19 09:46:53 2014 - ver 26.5]
Sending expected completion date for M35614801: Jun 21 2015
[Sat Sep 20 18:23:21 2014 - ver 26.5]
Sending expected completion date for M35614801: May 31 2015
[Mon Sep 22 01:49:36 2014 - ver 26.5]
Sending expected completion date for M35614801: Jan 22 2015
[Tue Sep 23 01:49:37 2014 - ver 26.5]
Sending expected completion date for M35614801: Jan 21 2015
[Wed Sep 24 01:49:38 2014 - ver 26.5]
Sending expected completion date for M35614801: Jun 12 2015
[Thu Sep 25 10:33:41 2014 - ver 26.5]
Sending expected completion date for M35614801: Jan 21 2015
[Fri Sep 26 11:14:42 2014 - ver 26.5]
Sending expected completion date for M35614801: Jan 21 2015
[Sat Sep 27 11:14:43 2014 - ver 26.5]
Sending expected completion date for M35614801: Jan 20 2015
[Sun Sep 28 11:14:44 2014 - ver 26.5]
Sending expected completion date for M35614801: Jan 15 2015
[Mon Sep 29 11:14:45 2014 - ver 26.5]
Sending expected completion date for M35614801: May 29 2015
[Tue Sep 30 13:27:07 2014 - ver 26.5]
Sending expected completion date for M35614801: May 29 2015
[Wed Oct 1 13:27:08 2014 - ver 26.5]
Sending expected completion date for M35614801: May 25 2015
[Thu Oct 2 22:51:03 2014 - ver 26.5]
Sending expected completion date for M35614801: May 15 2015
[Fri Oct 3 22:51:04 2014 - ver 26.5]
Sending expected completion date for M35614801: Apr 28 2015
[Sun Oct 5 14:12:27 2014 - ver 26.5]
Sending expected completion date for M35614801: Jan 15 2015
[Mon Oct 6 18:16:21 2014 - ver 26.5]
Sending expected completion date for M35614801: Jan 14 2015
[Tue Oct 7 20:27:24 2014 - ver 26.5]
Sending expected completion date for M35614801: May 12 2015
[Wed Oct 8 20:27:25 2014 - ver 26.5]
Sending expected completion date for M35614801: May 9 2015
[Thu Oct 9 23:54:26 2014 - ver 26.5]
Sending expected completion date for M35614801: May 7 2015
[Fri Oct 10 23:54:27 2014 - ver 26.5]
Sending expected completion date for M35614801: Apr 20 2015
[Sat Oct 11 23:54:28 2014 - ver 26.5]
Sending expected completion date for M35614801: Apr 10 2015
[Sun Oct 12 23:54:29 2014 - ver 26.5]
Sending expected completion date for M35614801: Apr 1 2015
[Tue Oct 14 00:40:34 2014 - ver 26.5]
Sending expected completion date for M35614801: Jan 10 2015
[Tue Oct 14 10:31:16 2014 - ver 26.5]
Sending expected completion date for M35614801: Jan 9 2015
[Wed Oct 15 10:31:17 2014 - ver 26.5]
Sending expected completion date for M35614801: Jan 9 2015
[Thu Oct 16 10:31:18 2014 - ver 26.5]
Sending expected completion date for M35614801: Apr 20 2015
[Fri Oct 17 10:31:19 2014 - ver 26.5]
Sending expected completion date for M35614801: Jan 9 2015
[Sat Oct 18 18:42:22 2014 - ver 26.5]
Sending expected completion date for M35614801: Apr 15 2015
[Mon Oct 20 01:56:57 2014 - ver 26.5]
Sending expected completion date for M35614801: Jan 7 2015
[Tue Oct 21 01:56:58 2014 - ver 26.5]
Sending expected completion date for M35614801: Jan 8 2015
[Wed Oct 22 01:56:59 2014 - ver 26.5]
Sending expected completion date for M35614801: Jan 8 2015
[Thu Oct 23 02:02:22 2014 - ver 26.5]
Sending expected completion date for M35614801: Jan 7 2015
[Fri Oct 24 02:02:23 2014 - ver 26.5]
Sending expected completion date for M35614801: Apr 6 2015
[Sat Oct 25 11:53:07 2014 - ver 26.5]
Sending expected completion date for M35614801: Apr 2 2015
[Sun Oct 26 10:53:07 2014 - ver 26.5]
Sending expected completion date for M35614801: Mar 24 2015
[Mon Oct 27 10:53:08 2014 - ver 26.5]
Sending expected completion date for M35614801: Mar 16 2015
[Mon Oct 27 17:35:45 2014 - ver 26.5]
Sending expected completion date for M35614801: Jan 4 2015
[Tue Oct 28 17:35:46 2014 - ver 26.5]
Sending expected completion date for M35614801: Jan 3 2015
[Wed Oct 29 17:35:47 2014 - ver 26.5]
Sending expected completion date for M35614801: Dec 31 2014
[Thu Oct 30 21:08:50 2014 - ver 26.5]
Sending expected completion date for M35614801: Dec 30 2014
[Fri Oct 31 21:08:52 2014 - ver 26.5]
Sending expected completion date for M35614801: Dec 25 2014
[Sat Nov 1 21:08:52 2014 - ver 26.5]
Sending expected completion date for M35614801: Dec 23 2014
[Sun Nov 2 21:08:53 2014 - ver 26.5]
Sending expected completion date for M35614801: Mar 6 2015
[Mon Nov 3 21:08:54 2014 - ver 26.5]
Sending expected completion date for M35614801: Mar 3 2015
[Sun Nov 9 15:29:41 2014 - ver 26.5]
Sending expected completion date for M35614801: Mar 6 2015
[/CODE]

[QUOTE=retina;387287]I question the utility of the estimated completion. It is almost certainly wrong. And even if all involved clients are perfect in their estimates (which itself is very unlikely) there are still those impatient poachers that will blast through the last few exponents thus making the time estimate meaningless.[/QUOTE]

As the saying goes, it's close enough for government work. :smile:

[QUOTE=Madpoo;387368]As the saying goes, it's close enough for government work. :smile:[/QUOTE]How about we make a deal. If you get rid of the internal table horiz scrollbar on the recent cleared/results reports then I won't complain about the estimated completion date. :deadhorse::spinner::whistle:

[QUOTE=retina;387369]How about we make a deal. If you get rid of the internal table horiz scrollbar on the recent cleared/results reports then I won't complain about the estimated completion date.[/QUOTE]

I think it only looks that way since you have Javascript disabled. The tablesorter plugin auto resizes columns once it loads, so that could make all the difference.

So... you could enable Javascript :deadhorse: :smile:

[QUOTE=Madpoo;387373]I think it only looks that way since you have Javascript disabled. The tablesorter plugin auto resizes columns once it loads, so that could make all the difference.

So... you could enable Javascript :deadhorse: :smile:[/QUOTE]Or you could remove the overflow value in the the pre tag: [strike]"style="overflow: auto;"[/strike] It's like the table is in :jail:

:tantrum:

[size=1][color=grey]Note: It only overflows when someone reports a very large p-1 factor, but it is very irritating when it does happen.[/color][/size]

[QUOTE=retina;387376]Or you could remove the overflow value in the the pre tag: [strike]"style="overflow: auto;"[/strike] It's like the table is in :jail:

:tantrum:

[SIZE=1][COLOR=grey]Note:[COLOR=Black] [SIZE=2][B]It only overflows when someone reports a very large p-1 factor,[/B][/SIZE][/COLOR] but it is very irritating when it does happen.[/COLOR][/SIZE][/QUOTE]


Are you sure that you are not insisting on this point just to maintain your evil cred?

[QUOTE=kladner;387400]Are you sure that you are not insisting on this point ...[/QUOTE]I'm not insisting on anything. Merely suggesting. :whistle:[QUOTE=kladner;387400]... just to maintain your evil cred?[/QUOTE]That is a given. Even my minions know not to question that! :razz:

I really don't know/get why javascript is "bad". Can someone enlighten me?

[QUOTE=kracker;387405]I really don't know/get why javascript is "bad". Can someone enlighten me?[/QUOTE]

Short answer: It's not. :smile: