20080523, 14:29  #56 
Quasi Admin Thing
May 2005
2^{4}×61 Posts 
@Gary, well as mentioned in my email to you, or at least I hope this will leave you in no doubt:
The one sieve file for Base 27 with more candidates remaining is simply because of higher sieve ranges, hence less candidates removed, but in fact range 1 and 2 started out being the same size (if I remember it right)! KEP! 
20080523, 22:06  #57 
May 2007
Kansas; USA
24714_{8} Posts 
Sierp base 3 is now complete to k=25M and n=25K. For k=15M25M, 47 additional k's were found to be remaining and are now shown on the web pages.
In additional to the 55 k's remaining for k=115M, this now makes 102 k's remaining for k<25M to n=25K. Including the ranges completed by Micha and Kenneth, we are now at 228 total k's remaining for the ranges of k<25M and k=100M120M. I'm continuing on to k=30M as per my reduced reservation. If anyone wants to do k=30M50M to n=25K for Sierp base 3, that would be a good range to work on now. If there is no interest, I'll take on the effort starting within a couple of months. IMHO, we should do a sieve for n=25K200K for all k's remaining once we reach k=50M. There should be ~200250 k's in such a sieve. Continuing to find 1000's of small primes gets quite boring after a while and it will make the effort more interesting if we do that in conjunction with sieving and searching for some larger primes. Gary Last fiddled with by gd_barnes on 20080523 at 22:17 
20080523, 22:38  #58  
Jan 2005
479_{10} Posts 
Quote:
(If I get away from the comp, it might run a bit further then 50M, but that will be ok I guess :) ) If about 200300 k's are left at 50M, let's make that the standard 'running length'. After sieving those, we'll need to get an 'optimum standard sieve depth' for those chunks. I'll take a mental note that I started this as 0:35 240508 :> One advantage of the script is, that I can tell you exactly which ones remain upto the range tested so far... (none upto 30025000)... First one found at: 30032708 1:19 240508 (it was the first one to run over 10k too...) Last fiddled with by michaf on 20080523 at 23:20 Reason: added first one found 

20080523, 22:47  #59 
Jan 2005
479 Posts 

20080525, 01:24  #60  
May 2007
Kansas; USA
10100111001100_{2} Posts 
Quote:
I'll start again on Sierp base 3 k=25M30M after the NPLB rally late Sunday. ETA is 56 days on 2 slowerspeed cores. I agree on the sieving. In the future, we'll sieve all kvalues remaining for each k=50M range...should be 200300 of them. I was suggesting the n=25K200K range but we can determine that more specifically when we get close to completing up to k=50M. Gary 

20080528, 17:25  #61 
Jan 2005
479 Posts 
Status on Sierpinski base 3, 3050M:
finished sieving (upto 5G seems about right, removal rate was just about 810 sec/n, and llr takes 7.something seconds to test. Sr2sieve wasn't used, it gave malloc error :( remaining at n=10k: 289 k's 
20080530, 14:32  #62  
Quasi Admin Thing
May 2005
2^{4}·61 Posts 
Quote:
Hope all is well, just out of curiosity, do you use t, to make sure that infact primes is found using your script hence avoiding a lot of double checking later on? KEP! 

20080530, 16:16  #63  
Jan 2005
737_{8} Posts 
Quote:
And no, I haven't used t as starters, but will check all the primes later on indeed. 

20080530, 17:13  #64  
May 2007
Kansas; USA
10100111001100_{2} Posts 
Quote:
Just let it crunch overnight on the tables if you have to. Be sure and save off the Legendre tables for the k's you're testing. That way you won't have to do it again if you start and stop the sieve or run it on more than one machine. I don't know if there's a way to make it NOT create the tables. Alternatively you can just use srsieve, albeit at a much slower sieving speed. Another alternative is to remove the 'problem' k and sieve it separately using sr1sieve. When doing the sieving using sr2sieve for n>25K for 200+ k's for all k<50M, we'll just have to wait and let it create the tables if the machine has enough RAM. Gary 

20080530, 17:26  #65  
Jan 2005
479 Posts 
Quote:
It quitted with a malloc error unfortunately :( Quote:
Quote:


20080530, 17:37  #66 
May 2007
Kansas; USA
24714_{8} Posts 
Oh yeah, you said that either. Either your machine doesn't have enough memory or sr2sieve isn't able to allocate enough memory for the table in question, most likely the latter.
Last fiddled with by gd_barnes on 20080530 at 17:38 
Thread Tools  
Similar Threads  
Thread  Thread Starter  Forum  Replies  Last Post 
Bases 251500 reservations/statuses/primes  gd_barnes  Conjectures 'R Us  2413  20220509 20:14 
Bases 101250 reservations/statuses/primes  gd_barnes  Conjectures 'R Us  982  20220508 22:14 
Riesel base 3 reservations/statuses/primes  KEP  Conjectures 'R Us  1132  20220507 18:19 
Bases 632 reservations/statuses/primes  gd_barnes  Conjectures 'R Us  1416  20220424 08:50 
Bases 33100 reservations/statuses/primes  Siemelink  Conjectures 'R Us  1715  20220123 14:23 