Merry Christmas and a prime! (M50 related)

[Madpoo]

Originally Posted by pacionet

I found Madpoo test, the prime could be M64764893 :) which seems have 3 LL (1 failed e 2 OK)

I try to snag all of the triple-checking assignments and get them finished quickly, otherwise whoever turned in the mismatch is left wondering, and sometimes they run their own triple-check. If they match their own, I'll be doing an independent verification anyway so I'd rather just do the triple-check and get it done for them.

[paulunderwood]

Originally Posted by Madpoo

Just finished my double-check:
Mxxxxxxxx is prime!

[airsquirrels]

I have two parallel runs going on Vega 64 FEs. ETA ~ 36 hours. gpuOwl with Jacobi checks.

I’m sure the other verifications that aren’t mprime will also complete before then, but it is nice to be thorough.

[Batalov]

Congratulations to all GIMPS participants!
Everyone who ever tested a composite candidate made this prime possible!

[pacionet]

Please tell us which is the new prime !

[ET_]

We are waiting (and longing for) the other GPU and mlucas checks.

Go GIMPS Go!

[preda]

Congrats all!

there was a rather surprisingly large hole between M48 at 57'885'161) and the [ex] M49 at 74'207'281.

[R. Gerbicz]

Originally Posted by preda

Congrats all!

there was a rather surprisingly large hole between M48 at 57'885'161) and the [ex] M49 at 74'207'281.

I wouldn't say that: https://primes.utm.edu/notes/faq/NextMersenne.html .

[Luis]

@preda: LOL!

I tried to predict something similar more than three years ago.
http://mersenneforum.org/showthread....050#post388050

Who knows...
We, as humans, always look for linearity and simmetry. Math and prime numbers teach us a different plan.

[Madpoo]

Originally Posted by preda

Congrats all!

there was a rather surprisingly large hole between M48 at 57'885'161) and the [ex] M49 at 74'207'281.

My math on this is guaranteed to be wrong, so nobody crunch the numbers... but...

My theory is that we've missed a prime that will later be found by double-checking.

If we reckon that the error rate (so far) on first-time checks is around 3-4%, and we now have 50 Mersenne primes of ever increasing size, I think given that data it's safe to say that eventually a prime will most definitely be missed, sooner or later. My theory is that it's already happened.

If it hasn't already happened, it may still happen but I suppose that depends on the robustness of the new error checking methods that have been introduced. It'd be great if those really prove themselves worthwhile and we didn't have to "waste" 50% of the total compute capacity with double-checks.

[Madpoo]

Originally Posted by Luis

@preda: LOL!

I tried to predict something similar more than three years ago.
http://mersenneforum.org/showthread....050#post388050

Who knows...
We, as humans, always look for linearity and simmetry. Math and prime numbers teach us a different plan.

Whoa... the crazy part about that old post from just 3 years back is that we were just clearing the 53M first-time check milestone, and here we are coming close to the 77M milestone. We've been rocking it!