80%
 

Now over 80% complete. :spot::spot: :spot::spot: :spot::spot: :spot::spot:

At the moment, I save the summary.txt once an hour on my server, and the second unverified prime first appeared in the 20:00 report, and disappeared in the 23:00 report. Other than that, I haven't a clue what happened.

EDIT: George just posted an update to the other thread.

Hardware seems to have improved a bit since the last verify I was involved in. Ernst, any idea what the itteration time was on M38? It was on a 500MHz 22164, IIRC. I'm pretty sure we didn't have any of the 666MHz 21264a boxes in, yet.

[QUOTE=willmore;141209]Hardware seems to have improved a bit since the last verify I was involved in. Ernst, any idea what the itteration time was on M38? It was on a 500MHz 22164, IIRC. I'm pretty sure we didn't have any of the 666MHz 21264a boxes in, yet.[/QUOTE]

The [URL="http://www.mersenne.org/6972593.htm"]press release[/URL] confirms 500MHz. It also refers to two weeks compute time so making a huge assumption and taking that as a real time figure you would get 0.173 secs/iter.

[QUOTE=ixfd64;141170]Wow, nice find! I'm surprised nobody else noticed that.

The residue of M42760397 (0x[B]A[/B]6090[B]C[/B]299[B]C[/B]0678__) has a strangely low proportion of hexadecimal digits. Does anyone else find it a bit... eye-catching?[/QUOTE]

Here is a list of the 17 possible exponents, arranged by number of hexits. By comparison, the expected number of hexits is 5.25.

[CODE]
42781927 69 0x8613884B69237A__ 2
37425887 68 0x9B10891A72B405__ 3
37763179 70 0xB141C151483C99__ 3
42760397 70 0xA6090C299C0678__ 3
28829407 69 0x849E58408C92DE__ 4
43112609 69 0x8691696D2BDA50__ 4
37946213 69 0x901FF5AA04168E__ 5
41959849 69 0xD689BE98B86C77__ 5
42796219 69 0x4F4C53A0908A5D__ 5
38859463 69 0x5840B65CA7CB7B__ 6
43411699 69 0x7C0112FE295ECD__ 6
36705287 70 0xDDA8BEB967041D__ 7
40896127 69 0x4F9CCA10FDF131__ 7
42206137 69 0x0A0EEC17151DAC__ 7
42801739 69 0xF6DDB517B9A4C6__ 7
43096799 69 0x32E28ECEC2C31B__ 7
41935241 69 0xEDB167FA1DBB31__ 8[/CODE]

Probability of having X Hexits in the not hidden characters of the residue:
(= having Y characters divisible by 3)

[CODE]0: 0.139%
1: 1.166%
2: 4.546%
3: 10.911%
4: 18.004%
5: 21.604%
6: 19.444%
7: 13.333%
8: 7.000%
9: 2.800%
10: 0.840%
11: 0.183%
12: 0.027%
13: 0.003%
14: 0.0001%
[/CODE]

[QUOTE=biwema;141260]Probability of having X Hexits in the not hidden characters of the residue:
(= having Y characters divisible by 3)
[/QUOTE]

Probability of having X Hexits in a "truly random number" or in a "LLT-residue" (is it known if the digits in the LLT-residues are equally distributed?)

Regards,
TheJudger

[QUOTE=TheJudger;141272]Probability of having X Hexits in a "truly random number" or in a "LLT-residue" (is it known if the digits in the LLT-residues are equally distributed?)

Regards,
TheJudger[/QUOTE]

I think he's assuming "truly random number".

[QUOTE=rgiltrap;141205]Now over 80% complete. :spot::spot: :spot::spot: :spot::spot: :spot::spot:[/QUOTE]

Wow, you're covering around 10% a day. I guess you'll be done by tomorrow!

[QUOTE=rgiltrap;141205]Now over 80% complete. :spot::spot: :spot::spot: :spot::spot: :spot::spot:[/QUOTE]

Yikes, I just past 70%... But your lamborghini is a gas guzzler, at least I am using renewable energy in my vehicle... :tu: <hugs Niagara Falls>

50% done
 

50% done. I'm late, I'm late...
Should ask for a new big toy next Christmas...
Tony