M(6972593) is the 38th Mersenne prime

[Prime95]

Congratulations GIMPSters,

Yesterday the last double-check below M(6972593) came in. This proves there are no undiscovered Mersenne primes below M(6972593) making it the 38th Mersenne prime.

Thanks to everyone for all their hard work in making this milestone possible.

Keep on crunching and have fun,
George

[helgen19]

How cool is that!

[eepiccolo]

Originally Posted by helgen19

How cool is that!

Extremely cool!!! :D :D

[lycorn]

Well done!
Now it´s time to roll up our sleeves and tackle the next one: test all exponents below 13466917 at least once.
You fast testers out there: try to get recycled exponents below this milestone, but please refrain from poaching...
Suggestion for George: you could do the same you did recently for 7M DCs and release some exponents below M39 that are hopelessly hanging around (if any).

[dswanson]

I'm on it already... 8)

[code:1]
------- Exponents Assigned -------

Assignment overdue check-in is set at 60.0 days (0.0 days to expire)

prime fact current days
exponent bits iteration run / to go / exp date updated date assigned computer ID Mhz Ver
-------- -- ---- --------- ----------------- --------------- --------------- ------------ ---- ---
...
11279189 65 1364500 6.7 10.3 60.3 04-Feb-03 06:27 29-Jan-03 06:02 1800-B 1808 v19/v20
12086951 65 1377791 27.7 3.3 60.3 04-Feb-03 06:16 08-Jan-03 06:02 2400-A 2399 v19/v20
12225991 65 24.7 63.3 60.3 04-Feb-03 04:06 11-Jan-03 06:10 1800-E 451 v19/v20
12270763 65 3.7 8.3 60.3 04-Feb-03 06:27 01-Feb-03 06:03 1800-A 1807 v19/v20
12342461 64 27.7 7.8 60.8 04-Feb-03 16:56 08-Jan-03 06:02 1800-H-clem 1794 v19/v20
12381773 65 35.7 9.7 60.7 04-Feb-03 15:22 31-Dec-02 06:09 1800-C 1794 v19/v20
12442069 65 31.7 16.3 60.3 04-Feb-03 06:27 04-Jan-03 06:06 1800-B 1808 v19/v20
12446857 65 19.7 14.3 60.3 04-Feb-03 06:27 16-Jan-03 06:07 1800-A 1807 v19/v20
12522941 65 20.7 16.7 60.7 04-Feb-03 15:22 15-Jan-03 06:01 1800-C 1794 v19/v20
12545783 65 1202815 19.7 4.7 59.7 03-Feb-03 14:52 16-Jan-03 06:07 1800-I-dzun 1794 v19/v20
12613127 65 26.7 8.3 60.3 04-Feb-03 06:16 09-Jan-03 06:03 2400-A 2399 v19/v20
12658301 65 27.7 13.3 60.3 04-Feb-03 06:16 08-Jan-03 06:02 2400-A 2399 v19/v20
12677911 65 24.7 18.3 60.3 04-Feb-03 06:16 11-Jan-03 06:10 2400-A 2399 v19/v20
12699439 65 3248607 45.7 8.7 60.7 04-Feb-03 15:41 21-Dec-02 06:02 1800-J-dodd 1794 v19/v20
12843731 65 12.7 21.3 60.3 04-Feb-03 06:27 23-Jan-03 06:02 1800-A 1807 v19/v20
12850619 65 21.7 24.3 60.3 04-Feb-03 06:16 14-Jan-03 06:06 2400-A 2399 v19/v20
12855211 65 3013247 13.7 5.7 60.7 04-Feb-03 14:59 22-Jan-03 06:20 1800-M-koid 1794 v19/v20
12949081 65 35.7 29.3 60.3 04-Feb-03 06:16 31-Dec-02 06:09 2400-A 2399 v19/v20
[/code:1]

[Ian_H]

Originally Posted by dswanson

I'm on it already... 8)

Great stuff! But.... couldn't you switch the exponent below to a faster machine?! :)

[code:1]12225991 65 24.7 63.3 60.3 04-Feb-03 04:06 11-Jan-03 06:10 1800-E 451 v19/v20[/code:1]

[dswanson]

Pay no attention to the days-to-go and MHz columns for 12225991. It's running on a 1.8 GHz P4 that's isolated from the net. I periodically sneakernet prime.spl over to a P2-450 and report from there. So the days-to-go and MHz are reported as if the 450 were running the exponent, which it isn't. The number will be done in a few days. :D

[cheesehead]

Notice how the longer days-to-go number for 12225991 makes it look like an "obvious" poaching target.

But as dswanson points out, the reality is that M12225991's L-L testing is proceeding as fast as, or faster than, other assignments.

Edited to remove excessive OT verbiage. :)

[Ian_H]

Originally Posted by dswanson

I periodically sneakernet prime.spl over to a P2-450 and report from there.

"Sneakernet"

Of course cheesehead is right, too - but let's leave the poaching debate in the other thread... :)

[dswanson]

Originally Posted by Ian_H

"Sneakernet"

Sneakernet = copy intermediate file(s) from off-net machine onto floppy, walk to on-net machine, copy files from floppy. Sneakernet.

[dswanson]

Originally Posted by dswanson

Pay no attention to the days-to-go and MHz columns for 12225991. It's running on a 1.8 GHz P4 that's isolated from the net. I periodically sneakernet prime.spl over to a P2-450 and report from there. So the days-to-go and MHz are reported as if the 450 were running the exponent, which it isn't. The number will be done in a few days. :D

I figured out how to make use of some of the features in undoc.txt to make the 450 report as if it were the 1.8 GHz P4. Specifically, I added the following to local.ini:
[code:1]CpuOverride=1
CpuType=12
CpuSpeed=1800
CpuSupportsRDTSC=1
CpuSupportsCMOV=1
CpuSupportsPrefetch=1
CpuSupportsSSE=1
CpuSupportsSSE2=1
[/code:1]
And presto! The correct end date is reported for 12225991...
[code:1] prime fact current days
exponent bits iteration run / to go / exp date updated date assigned computer ID Mhz Ver
-------- -- ---- --------- ----------------- --------------- --------------- ------------ ---- ---
...
12225991 65 9015681 30.0 2.0 61.0 10-Feb-03 06:26 11-Jan-03 06:10 1800-E 1800 v19/v20
[/code:1]
Like I said, it will be done in a couple of days! :D