not-quite-monthly update:
 

I haven't updated in a while because I've taken a long time to fill in lower ranges- I spread some k's over many machines, and waited for all ranges to finish to report.
11 is complete to 1.55M (2 cores)
13 to 1.5M. (1 core)
45 to 1.25M (2 cores)
93 to 980k (might be same as before, I have a hole 980-1000k left to fill)
99 to 1.3M (3 cores)
127 to 1.85M (1 core)
197 to 1.14M (only going to 1.2, almost done on one core)
201 1.04M (1 core)

109,131,141,211,245,269,281 all done to 700k. These are being tested as a group, so the going is slow for now, until some of the above projects finish or I buy a Quad.
I have a sieve for these last ones to 52T, and welcome assistance. I'm willing to "rent out" 100k blocks for any single k. 141 is spoken for, the rest are available 765k-865k.
-Curtis

k = 49
 

Update:
Sieving at 35T to 5M,
LLR complete to 1.34M.

Hi all,

As part of a new effort to help push forward a number of k<300 that are significantly "behind" their neighbors as far as testing level is concerned, the No Prime Left Behind project is reserving the following currently unreserved k's, all searched to n=600K except k=289:

65, 115, 149, 175, 179, 185, 199, 215, 227, 229, 239, 241, 257, 265, 271, 289, 293

With the exception of k=289, which we will be reserving for the range of n=520K-1M, all of the above k's are reserved for the range of n=600K-1M.

We will be starting a public team sieve for these k's within the next week or two, and plan to start an LLR team drive when that is concluded, so if any of you guys want to help search these k's, feel free to come on over! :smile:

Anon :smile:

Prime Search has never searched k<250, and since several years ago they haven't searched k<300 either (with exception of Griffin at k=255). On the other hand RPS, and 15k before, have been committed to k<300 from the beginning. We've searched some Ks from as low as n=20k.

In other words, [B]your reservation makes no sense[/B]! You have your 300 < k < 1000, 350 of them, that's more than enough.

And Ks at 600k are [B]not[/B] "behind" for prime search in general. Some k<100 of the k*2^n+1 form are still not completely tested below 500k!

Anon-
I assume this means you will credit RPS as the project, not primesearch?

What is the reasoning to start another team drive when we have a drive on k's of very similar size already sieved yet untested at the levels you are aiming at?
RPS has a history of having some k's tested as team drives, others left open to reservation for individual testers. We have many files already sieved in the 600k to 1M range, yet many longtime RPS members like to sieve for themselves. If your main goal is to get as many k's to 1M as possible, test the Masser files, or the 6th drive. We don't need more sieving done right now, but we do like having individual k's available at a level where an individual with 1-3 machines can make useful progress on his/her own. If you take all remaining k's currently under 1M, that opportunity is lost to the extent that megabits are MUCH slower for individuals with few machines to make progress on. This is exactly the reason I left these k's out of the 6th drive- I could have sieved all of them, but we like the idea of leaving some for individual reservations.
There is efficiency in sieving many k's all at once, but a yet greater efficiency in sieving a large range of n all at once. If you do go ahead with a k<300 search, please consider honoring our wishes to leave some k's for individual RPS members; you can compensate for this by taking fewer k's higher than 1M- high enough to make a project of similar length, and likely with a more efficient sieve.

Please explain how you conclude these k's are "behind". I'm interested in the thought process, why you are choosing RPS k's instead of some other smaller unsearched candidates (proths under 300? Riesels in 1000-2000? etc). The top-5000 cutoff is ~400k, I think; primes that take twice as long to test as the cutoff prime don't seem behind to me, particularly when there are quite a few k's in 300-400 also only tested to 600k-- and you already have those sieved to 1M!

I suspect by the time you test 300-400 to 1M, many of these k's under 300 would be reserved and advanced toward 1M, if not higher. With so much already sieved and ready to test both in RPS and NPLB, I hope you will reconsider your effort, which removes the opportunity for individuals to run individual k's start-to-finish with their own sieving effort. Review AES's entry into RPS and reservations for an example of a recent individual tester- he has both team participation and his own k's.

-Curtis

My concern here is the excess of work to be tested on such limited CPU power.

k=191
 

Taking k=191 from 1M.

To Gary,

Only jerks keep on posting their worthless messages.
It's up to you to show who you are.

To Gary and Anon

If it was not already clear from before:
We don't want to deal or cooperate with you in any way.
We don't want to read your junk mail, and waste time responding to it.
You are not welcome on these pages.

We consider your latest reservation of 20 Ks void.

This is the end of discussion.
Please go away and leave us alone.

[QUOTE]the No Prime Left Behind project is reserving the following currently unreserved k's, all searched to n=600K except k=289:

65, ... 241, ... 293
[/QUOTE]

[QUOTE=Kosmaj;140375]
We consider your latest reservation of 20 Ks void.
[/QUOTE]

So does this mean that I (or any other individual) can reserve k=241? Just wondering, because that k is not listed as available on the [url]www.rieselprime.org[/url] page.

MooMoo

Yes you can, and you are welcome to do so!