20080116, 21:28  #166 
"Jason Goatcher"
Mar 2005
DB3_{16} Posts 
I'm still hoping for a sieve file.
Also, I've thought about it, and I've decided I'm willing to sieve for any base from 231. I'm thinking I might download the various sieve files and see what kinds of numbers I come up with. Of course, I intend to start with my already reserved number. k=16734 base=4. :) 
20080116, 22:30  #167  
May 2007
Kansas; USA
24177_{8} Posts 
Quote:
I'm thinking to get it to 1.5T would take about 10 CPU days but just getting it to about P=1.2T1.25T would be helpful. I need to remove k's found prime by the drive in the last few days but I could send them to you within about 6 hours or so. (4 AM GMT) Let me know and I'll give you more specifics about what is needed. Gary 

20080116, 23:30  #168  
"Jason Goatcher"
Mar 2005
3×7×167 Posts 
Quote:


20080117, 04:40  #169  
May 2007
Kansas; USA
7·1,481 Posts 
Quote:
Are you familiar with how to run sr2sieve? If not, I should mention that it doesn't remove candidates, it only writes out factors. I'm fine if you want to run the sieve and send me the factors. I can then remove the candidates using srfile. Gary 

20080117, 05:53  #170 
Sep 2004
UVic
70_{10} Posts 
13438 prime found
13438*2^395260+1 is prime! Time: 232.374 sec.
aka 13438*16^98815+1 results file attached. (file completed) Gary can you send a pm with directions how to submit properly? I do believe it's large enough and I've never done it before... reserving: sievesierpbase28.txt Last fiddled with by tcadigan on 20080117 at 05:59 
20080117, 06:39  #171  
May 2007
Kansas; USA
7×1,481 Posts 
Quote:
Wow, lightning strikes twice in two days! Congrats on your first top5K prime! And just in time before the file ran out. It saves me sieving time for n=100K200K also. (I'm including all k's remaining in it; not just the 'team drive' k's.) Life is good! I'm thinking it makes sense to publically post the instructions on submitting a top5K prime. I'll do that in the 'report primes here' thread in a little while. Edit: This one will be a little 'different' so to speak. You can choose to submit it as is but the top5K site will 'normalize' it to 6719*2^395261+1. I would suggest submitting it in this normallized format. I prefer to do it that way because otherwise you get a cryptic message that is not an error but is hard to understand if you've never done it before. I'll send you a PM in addition to the public instructions. Gary Last fiddled with by gd_barnes on 20080118 at 01:57 Reason: Changed comment about where instructions thread is 

20080117, 11:20  #172  
Jan 2005
479 Posts 
No, I did not add it back (haven't even seen it coming up :>)
I'll add it to my files, and sieve/llr it as far as the rest Quote:


20080117, 19:34  #173 
Sep 2006
11×17 Posts 
Status update Sierp b17 and b18
Sierp b17: LLR around n~90k for all three k. I reserved till 100,000, but I think I will continue. Will start sieving soon, but have a question again.
What's more effective:  Sieve all three k together, or alone? Alone, I can use sr1sieve, which is much faster..  Sieve n = 100,000  200,000, or should I already sieve a bigger range (for example 100,000  1,000,000)? Sierp b18: LLR around n~150k, still one k remaining, and still no prime :( Last fiddled with by Xentar on 20080117 at 19:35 
20080117, 20:18  #174 
Jan 2006
Hungary
2^{2}×67 Posts 
342*27^36291+1 is prime.
found PRP by LLR, proven with pfgw. I won't continue that range obviously. Has anyone ever found a PRP that turned out not to be prime after all? Willem. 
20080117, 22:20  #175 
Jan 2005
479 Posts 
Usually, taking a bigger range doesn't affect the speed too much.
Then again, whenever you find a prime, the extra time is 'wasted'. I'd say that after n=0100k, a good choice would be n=100500k. Best would be to testsieve a few ranges and see how it affects the speed 
20080117, 22:35  #176  
May 2007
Kansas; USA
7·1,481 Posts 
Quote:
I know I haven't found a PRP to be not prime. Edit: I think there is some smaller ones listed on the top5000 site. Supposedly the larger the PRP, the less chance it has of being not prime. I heard someone say that there's a much better chance of a hardware error causing an incorrect prime than a PRP being found not prime. Gary Last fiddled with by gd_barnes on 20080117 at 22:46 

Thread Tools  
Similar Threads  
Thread  Thread Starter  Forum  Replies  Last Post 
Bases 5011030 reservations/statuses/primes  KEP  Conjectures 'R Us  3857  20210509 14:34 
Bases 101250 reservations/statuses/primes  gd_barnes  Conjectures 'R Us  898  20210508 18:09 
Bases 251500 reservations/statuses/primes  gd_barnes  Conjectures 'R Us  2281  20210426 18:08 
Riesel base 3 reservations/statuses/primes  KEP  Conjectures 'R Us  1098  20210418 21:07 
Bases 33100 reservations/statuses/primes  Siemelink  Conjectures 'R Us  1682  20210413 23:50 