k=141 to n=1100000
k=103, 143, 167 to n=985000

k=43 is complete to 1.7M and released. No primes.

I have some gaps to fill in before I can report progress on the other k's. Next month...
-Curtis

Status report
 

k=25 tested till n=2.17M
k=59 tested till n=2.92M
k=101 tested till n=1.96M
k=151 tested till n=1.96M
k=233 tested till n=1.23M
k=283 tested till n=1.23M
k=299 tested till n=1.23M

I am still working on those.

Our [URL="http://www.15k.org/riesellist.html"]k*2^n-1 stats page[/URL] is now updated with all latest reports, including
k=21 at 1090k
k=161 at 880k
k=195 at 920k

9 Ks at 886k

k=17 and 6th drive Ks also updated.

k=103, 143, 167 to n=1100000

109 is complete to 1M.
-Curtis

k=161 and 163 at 910k.

k=193 and 277 at 950k.

Status report
 

k=25 tested till n=2.19M
k=59 tested till n=3.01M
k=101 tested till n=1.99M
k=151 tested till n=1.99M
k=233 tested till n=1.25M
k=283 tested till n=1.25M
k=299 tested till n=1.25M

I am still working on those.

Reserving k=43 - until I find a prime for it :smile:

Reserving the following k:[LIST][*]from n=1.7M: 51, 57, 61, 65, 87[*]from n=1M: 111, 115, 117, 119, 125, 129, 135, 149, 155, 157, 165, 175, 179, 185, 191, 209, 213, 215, 229, 231, 237, 241, 249, 261, 265, 267, 271, 273, 279, 285, 291, 293[*]from n=1.12M: 79, 83, 89, 91 [*]k=73 from n=2M[*]k=75 from n=1.5M[/LIST]Total of 43 k.
The purpose of this reservation is sieving with upper limit of n=5M (afterwards we can launch an RPS drive based on this). Preliminary sieve file ready till p=2T should be ready in the first half of September, and at that time I will welcome any support in this effort :smile:
Initial target depth is p=50T which should be sufficient at least till n=2M.

Cruelty-
Please add 201 to the sieve, though I wish to keep it reserved for myself. I am nearly done to 1.2M, and was just about to start a new sieve for it; please start it at 1.2M. I will assist with sieving as always.

You will find that 50T is not nearly enough sieving to even start testing- with such a large sieve, efficiency rises quite a lot. I won't be surprised if 300T is optimal for 1.2M candidates, for instance. It does make sense to run one sieve to save overall effort, even though it will be slow going.

For comparison, I have a 5-k sieve (11,13,31,45,99) going to n=4M. At 370T, I just pulled out candidates below 2M for LLR work. With 43 k's and n=5M, I imagine optimal depth for n=2M would be close to 1P. This is a very very big project.
-Curtis