Thread: 5000 < k < 6000 View Single Post
2009-07-29, 21:34   #7
justinsane

Mar 2004

3·11 Posts

Quote:
 Originally Posted by kar_bon please make some more specific details: i'm missing the test/sieve-range in n! is it still n=1M? so there're about 18.1M candidates left to test? i'm just llrnetting and i got a n=468010! when is the stats-page updated? you gave 581491 tested n with 661 primes found (n>50k if i'm right). which range was tested here? the most seems testd upto n=75k (as you mentioned above). why is k=5295 tested higher (upto n=130k). are others higher tested? the average of 878 n to test to find a prime is therefore only for n>75k. but in higher ranges it's quite more n to test (about 2000 to 4000 i think)! PS: the title of the page is "12121search" !

Haha, I just notived that 12121 thing and updated it. Oops.

Yes, the range is k = 5000-6000 with n up to 1M.

The stats page is updated automatically every time I update the results from prpnet. (I do so daily) But I am working on making it auto update. With LLRNET and the website hosted on different servers, thats a bit tricky.

You are right, those numbers are for ALL n tested greater than n=50,000, and right now the test is complete up to n=75,000 with some randoms after that. The statistics about prime frequency are definitely skewed because the majority of the results are n=50,000-75,000 and there are many more primes in that range, than say 900,000-1,000,000.

The plan is to change the reported information to n > 75,000 once there is enough completed results for n > 75,000. In that case (I estimate 1 week or so) then we will have a real idea of what the prime frequency should be. (Yes, I agree, it will be close to 2000-4000, probably higher) but that also depends on sieve depth. I still have not decided how much more I will sieve, but at 3T, there definitely is more to go. Sieving to at least 5T, can only improve the prime frequency. The sieve effort is on hole for now, but I will get back to it soon. (Any volunteers to help?)

Some n are higher tested because I personally LLR tested all k up to 60,000 and then used LLRNET for 60,000-75,000. On some n, I was too busy or forgot to stop LLR, but these are fairly few, and do not go much past 120,000, and they are all numebers with few n, so they should not effect the stats much.

User stats coming soon.