Primo/FastECPP reservation thread

[sweety439]

Originally Posted by Gelly

factordb seems to agree that it's prime, but the forward facing certificate doesn't appear to be available. not entirely sure what's going on there, as it says it's proven prime, but doesn't have an ECPP cert attached or anything.

i'll still attach the factordb entry to a t5k post but i'm still slightly unsure.

and yeah, i don't blame marcel for no longer posting all top 20s. seems to get updated a lot haha.

I know that you mean this number, a cofactor of the Mersenne number M106391, but why this number does not appear in the top ECPP proving page?

[paulunderwood]

Originally Posted by sweety439

I know that you mean this number, a cofactor of the Mersenne number M106391, but why this number does not appear in the top ECPP proving page?

Are you thick joking? I just posted that Gelly should submit to it to UTM. Until he does so it will not appear on the aforementioned top20 and at the top of the top20 Mersenne co-factors. Things don't magically happen -- some action is required!

[Gelly]

Originally Posted by paulunderwood

I'd say go ahead and report it to The Prime Pages at UTM and be assured in the knowledge that factorDB successfully verified the certificate.

ps. Do you fancy proving the co-factor of M78737?

Listed at UTM. I don't feel super-comfortable not having a certificate that's accessible to people anymore, but it appears that is happening to most of my primo certificates at this point. May have to look into some method of hosting them myself.

And yes, I may give a try to that next cofactor. Still settling into the new apartment, but 23k is going to be more than three times as fast to prove, so it won't be too much longer after popping it in to get results.

Don't consider this a reservation for the time being, though!

[paulunderwood]

Nearly finished:

M86137 cofactor prp25896

Dropping:

M86371 cofactor prp25984
M87691 cofactor prp26371
E(11848)/(5*1582043) prp40792

Reserving:

R86453

[sweety439]

Originally Posted by paulunderwood

Nearly finished:

M86137 cofactor prp25896

Dropping:

M86371 cofactor prp25984
M87691 cofactor prp26371
E(11848)/(5*1582043) prp40792

Reserving:

R86453

= = Are you sure that Primo can handle this large prime? Recently, the limit of Primo just extended from 40000 digits to 50000 digits, to make you can use Primo to prove R49081

Suggest you to prove (18^25667-1)/17 = R25667(18), this prime is also a generalized repunit, and is much smaller than R49081, this prime is interesting (much more interesting than R86453, you think R86453 is interesting is only because we use the number 10 as the base (radix) of our positional numeral system) is because this prime is the smallest generalized repunit prime in base 18 apart from 19 = R2(18), see https://oeis.org/A128164

[paulunderwood]

Originally Posted by sweety439

= = Are you sure that Primo can handle this large prime? Recently, the limit of Primo just extended from 40000 digits to 50000 digits, to make you can use Primo to prove R49081

Suggest you to prove (18^25667-1)/17 = R25667(18), this prime is also a generalized repunit, and is much smaller than R49081, this prime is interesting (much more interesting than R86453, you think R86453 is interesting is only because we use the number 10 as the base (radix) of our positional numeral system) is because this prime is the smallest generalized repunit prime in base 18 apart from 19 = R2(18), see https://oeis.org/A128164

Primo won't handle anything above ~50k digits. But FastECPP (+GWNUM) might and do it some 8 times faster than an extrapolated Primo could do it.

[ryanp]

Originally Posted by Gelly

Listed at UTM. I don't feel super-comfortable not having a certificate that's accessible to people anymore, but it appears that is happening to most of my primo certificates at this point. May have to look into some method of hosting them myself.

And yes, I may give a try to that next cofactor. Still settling into the new apartment, but 23k is going to be more than three times as fast to prove, so it won't be too much longer after popping it in to get results.

Don't consider this a reservation for the time being, though!

I only noticed this thread recently. I was just working on M78737 cofactor and just uploaded the cert. Hopefully no one else burned cycles on this...

[kruoli]

Originally Posted by ryanp

I only noticed this thread recently. I was just working on M78737 cofactor and just uploaded the cert. Hopefully no one else burned cycles on this...

Huh?

Originally Posted by ryanp

I decided to fire up certification of M78737 with Primo, using 64 processes. Hopefully no one else is already running this!

The machine it's running on is a 3Ghz, 36-core/72-thread system. Anyone have a rough sense of how long this should take?

(Addendum: it would be great if Primo was open-source... I'd love to understand more about these "stk4321" processes it spawns. If I could farm these out to a cluster and then feed the results back in, presumably this could go a lot faster).

[paulunderwood]

Originally Posted by kruoli

Huh?

Somewhere in the messaging bowels, Ryan did mention he had forgotten about his Primo run of the M78737 cofactor and that Primo had crashed. Better late than never!

[ryanp]

Originally Posted by kruoli

Huh?

Yes, I had reserved this one a while back, then promptly forgot about it (beyond what I could do with Primo on a single machine).

[paulunderwood]

@ryanp and @Andreas. Please make a The Prime Pages database entry for your numbers.

https://primes.utm.edu/top20/page.php?id=49
https://primes.utm.edu/top20/page.php?id=27

via

https://primes.utm.edu/bios/