M40 Again!!!!

Complex33 · 2003-11-17, 20:32

Quote:

------- Mersenne Exponent Test State -------
Prime, UNVERIFIED : 1

lycorn · 2003-11-17, 20:56

George, any comment?
What range is the "suspect" in?

GP2 · 2003-11-17, 21:10

My preliminary guess would be in the 20.4M range. But that's after only five minutes' investigation...

Prime95 · 2003-11-17, 21:16

Uh oh, GP2 the data analysis guru is on the case. I suspect the identity will know the identity within an hour!

edorajh · 2003-11-17, 21:20

Let's hope this one will be verified as Mersenne prime! That will be wonderful!

Prime95 · 2003-11-17, 21:28

I've just downloaded the server logs. There is a report of a new Mersenne prime!!! It looks like it was found using a post-M40-false-alarm prime95 since the error code was reported: 00000000.

I've emailed the user (not a team) for his results.txt file and last save file. If he has the save file then it should be a breeze to run the last few thousand iterations and virtually prove this is not a false alarm.

Unfortunately, we'll have to wait for a complete verification run using a different program and different hardware before we can officially announce the new prime. I've started a retest using prime95 and it will complete in early December. I'll contact Ernst and Guillermo to see when they can start an official verification run.

GP2 · 2003-11-17, 21:28

Quote:

Originally posted by Prime95
Uh oh, GP2 the data analysis guru is on the case. I suspect the identity will know the identity within an hour!

On second thought, it would be a bit like opening Christmas presents early. Maybe I'll sit back and wait to be surprised like everyone else.

Prime95 · 2003-11-17, 21:35

GP2, go for it, just don't let everyone else know. I'd like to know if our current methods keep new primes anonymous.

flava · 2003-11-17, 21:46

Waaaazaaaaa! Great news. I hope it's 'da real deal!

Xyzzy · 2003-11-17, 21:50

How do I stop this thing from beeping?

Xyzzy · 2003-11-17, 21:55

Never mind, it was a low battery alarm...

2003-11-17, 21:46	#9
flava Feb 2003 2·59 Posts	Waaaazaaaaa! Great news. I hope it's 'da real deal! Last fiddled with by flava on 2003-11-17 at 21:47

2003-11-17, 20:56	#2
lycorn Sep 2002 Oeiras, Portugal 2653₈ Posts	George, any comment? What range is the "suspect" in?

2003-11-17, 21:10	#3
GP2 Sep 2003 13·199 Posts	My preliminary guess would be in the 20.4M range. But that's after only five minutes' investigation...

2003-11-17, 21:16	#4
Prime95 P90 years forever! Aug 2002 Yeehaw, FL 1CEF₁₆ Posts	Uh oh, GP2 the data analysis guru is on the case. I suspect the identity will know the identity within an hour!

2003-11-17, 21:20	#5
edorajh Oct 2003 Croatia 2³·3·19 Posts	Let's hope this one will be verified as Mersenne prime! That will be wonderful!

2003-11-17, 21:28	#6
Prime95 P90 years forever! Aug 2002 Yeehaw, FL 3²×823 Posts	I've just downloaded the server logs. There is a report of a new Mersenne prime!!! It looks like it was found using a post-M40-false-alarm prime95 since the error code was reported: 00000000. I've emailed the user (not a team) for his results.txt file and last save file. If he has the save file then it should be a breeze to run the last few thousand iterations and virtually prove this is not a false alarm. Unfortunately, we'll have to wait for a complete verification run using a different program and different hardware before we can officially announce the new prime. I've started a retest using prime95 and it will complete in early December. I'll contact Ernst and Guillermo to see when they can start an official verification run.

2003-11-17, 21:35	#8
Prime95 P90 years forever! Aug 2002 Yeehaw, FL 3²·823 Posts	GP2, go for it, just don't let everyone else know. I'd like to know if our current methods keep new primes anonymous.

2003-11-17, 21:50	#10
Xyzzy "Mike" Aug 2002 3²×19×47 Posts	How do I stop this thing from beeping?

2003-11-17, 21:55	#11
Xyzzy "Mike" Aug 2002 8037₁₀ Posts	Never mind, it was a low battery alarm...