![]() |
1 Attachment(s)
[QUOTE=rogue;544792]Here is the next batch of R66 primes. All k thru 44451283 are tested to n=25000.[/QUOTE]
Primes that were found for k=17.578M-44.4515M n=11K-25K: 9190 Primes in that group already found prime for n=10K-11K: 15 Unique k's found prime for k=17.578M-44.4515M n=11K-25K: 9175 R66 previously remaining at n=25K: 95114 Primes found for k=17.578M-44.4515M n=11K-25K: 9175 R66 k's now remaining: 85939 Attached are the 15 k's that were found prime for n=11K-25K that already had a prime for n=10K-11K. I'm hoping that will help you save some time in your remaining searches. |
[QUOTE=gd_barnes;544855]Primes that were found for k=17.578M-44.4515M n=11K-25K: 9190
Primes in that group already found prime for n=10K-11K: 15 Unique k's found prime for k=17.578M-44.4515M n=11K-25K: 9175 R66 previously remaining at n=25K: 95114 Primes found for k=17.578M-44.4515M n=11K-25K: 9175 R66 k's now remaining: 85939 Attached are the 15 k's that were found prime for n=11K-25K that already had a prime for n=10K-11K. I'm hoping that will help you save some time in your remaining searches.[/QUOTE] Hmm. I thought I had removed k with previously known primes. Which k already had primes? Maybe they were in a range that I didn't clean-up before finishing. |
[QUOTE=rogue;544863]Hmm. I thought I had removed k with previously known primes. Which k already had primes? Maybe they were in a range that I didn't clean-up before finishing.[/QUOTE]
See the attachment to the previous post. They were in a fairly narrow k-range of k=36.5M-38.6M so you probably missed removing them in one file or something like that. |
[QUOTE=gd_barnes;544867]See the attachment to the previous post. They were in a fairly narrow k-range of k=36.5M-38.6M so you probably missed removing them in one file or something like that.[/QUOTE]
You are correct. They were all in primes_14.log. None were in any of the other 9 files I submitted. |
1 Attachment(s)
K4 S53 at 1.6M (RES file attached)
Extending reservation to 1M7 Reserving S53 to 305K |
The "top 10 primes" for R55 has the prime 68*55^29173-1, however, 68*55^1-1 = 3739 is prime, thus this prime is not the [I]first[/I] prime for k=68
|
[QUOTE=sweety439;549882]The "top 10 primes" for R55 has the prime 68*55^29173-1, however, 68*55^1-1 = 3739 is prime, thus this prime is not the [I]first[/I] prime for k=68[/QUOTE]
Good catch. This revealed an error in this base. k=608 (not k=68) was only tested up to n=25K. No prime was found. From this point forward k=608 was misread as k=68 and so k=68, despite having several small primes including at n=1, was tested for n>25K with a prime quickly found at n=29173. So this brings to light the fact that k=608 has only been tested to n=25K and has never had a prime found. I have updated the pages accordingly including removing the larger prime for k=68 and will begin a search 608*55^n-1 for n>25K. |
An odd state of affairs here:
After all of that messing around with sieving 608*55^n-1 for n=25K-100K (and preparing to sieve n=100K-300K) because it was found to erroneously only have been tested to n=25K: 608*55^25062-1 is prime! Found by the 5th test in the sieve file! So R55 is back to 5 k's remaining. :smile: |
Reserving S88 to n=500k (250-500k) for BOINC
|
S 53
K4 S53 at 1.61M
S53 -200K-305K -res sent to Gary Base released ( except K4 of course) |
1 Attachment(s)
Here are a bunch of primes for R66. The k between 94245817 and 99461099 still need to be tested to n=25000. All k outside of that range have been tested to n=25000. I hope to complete finish it off in a few weeks. Since I started this on 10/19 of last year, I will be happy to have finished it. It would probably take less time to get S3 to n=50000 than the time it took me to do this (and no, that is not next on my list).
Gary, if you think that there are other gaps that I could have missed, please let me know and I'll investigate. |
| All times are UTC. The time now is 09:03. |
Powered by vBulletin® Version 3.8.11
Copyright ©2000 - 2021, Jelsoft Enterprises Ltd.