20080513, 12:17  #1 
Account Deleted
"Tim Sorbera"
Aug 2006
San Antonio, TX USA
10253_{8} Posts 
n=333333 off the list
http://primes.utm.edu/primes/lists/all.txt
All k*2^3333331 primes are now off the Top 5000 list. #5001 is 28782838101*2^3333331 (archivable for being an arithmetic progression). I remember reading some posts between Jasong and Gary before NPLB started about Jasong wanting to have a "I hate n=333333" project to make the bottom of the list not boring, and Gary saying he had something coming up. In any case, the bottom of the Top 5000 list is no longer boring. p.s. it will be #5002 once I submit my prime, and probably drop a lot from several prime submissions...why did they have to do maintenance right when I found a prime? Oh well. again. 
20080513, 16:18  #2 
Just call me Henry
"David"
Sep 2007
Cambridge (GMT/BST)
16DF_{16} Posts 
it still is partly boring becausee of the number of primes found for k*2^3336661

20080513, 17:26  #3 
May 2007
Kansas; USA
24143_{8} Posts 
Yep, this is the project that was in the works that helped knock off the n=333333 primes. I hadn't planned it for that reason but it was a nice side benefit of it.
Don't worry, the n=333666 primes will soon go away also. The best way to knock off fixednsearches with HUGE kvalues is to do smallkvalue searches across a moderate range of nvalues just above the fixednvalues. The sieving is a little less efficient but the LLRing is much faster. Editor note :) : I never said anything about 'hating' the n=333333 primes. I should say that Jasong came up with that verbiage. They may have been somewhat of an annoyance but I think it's important to respect what the leader of an effort is after (unless they are poaching other projects). MooMoooo did a very nice job of organizing that project and they were a little unlucky not to find a huge twin prime, which was their objective. I believe the consensus on that project now is that the effort will search across a wide range of nvalues with smaller kvalues in the future but that is not set in stone yet. In the mean time, PrimeGrid has somewhat of an 'annoying' effort to do a similar thing with n=666666. At least it takes ~8 times as long to find an n=666666 prime vs. an n=333333 prime so they are trickling in quite slowly right now. Gary Last fiddled with by gd_barnes on 20080513 at 17:34 
Thread Tools  
Similar Threads  
Thread  Thread Starter  Forum  Replies  Last Post 
n=333333 Twin Found!  Kosmaj  Twin Prime Search  12  20090814 13:10 
What if we don't find twin prime n=333333?  cipher  Twin Prime Search  5  20090416 21:53 
Preparing N=333333  biwema  Twin Prime Search  26  20070211 23:35 
After n=333333, our next exponent will be... (revised poll)  MooooMoo  Twin Prime Search  24  20070201 06:30 
Who has a list?  Ice9  Math  9  20040127 16:32 