PDA

View Full Version : The "I hate n=333,333 project"



jasong
01-13-2008, 01:31 AM
If you go here (http://primes.utm.edu/primes/lists/all.txt) and scroll down, you'll see that the last 6 or 7 hundred entries in the Top-5000 known primes list is very boring looking, since the vast majority of them are n=333,333. The Twin Prime Search Project, a sub-project of PrimeGrid, is attacking n=333,333 to attempt to find the highest twin prime ever to be known to man.

Now, I have nothing against Rytis, the administrator, or the project itself, but it bugs the crap out of me that all those primes look so damn generic, like they came off of an assembly line or something.

Over at Mersenne Forum("Open Projects" Forum, at the bottom of the page, in the "new project ideas" Sticky) I'm attempting to start a project to knock these off the list as quickly as possible. Basically, the idea is to pick an n(fixed n, since that sieves so much faster than fixed k) and a range of k that guarantees that any primes found in that range will be larger than Twin Prime Search primes. If it starts looking like we're committing the same "crime" as TPS, than anybody has the option to start a new range with a new n.

Anybody interested?

em99010pepe
01-13-2008, 06:17 AM
Jasong,

Here's my humble opinion.
As I said looking for primes of a constant n is a waste of time because of its quality and size of the prime. You will see that time will knock out those primes from the rankings.

Your suggestion shows me you want to find easy primes and that your are using the same TPS strategy. In a year someone will post a comment like the one you did now.

I'm out. It's more difficult to search a prime for a fixed k, here's where you should concentrate your efforts. The beauty is to have processed a k for a long n.

Carlos

Beyond
01-14-2008, 04:49 PM
I too, was upset when TPS started registering all those primes with the TOP 5000 site. Alot of the lower ranged primes they knocked off the list took people months of sieving and testing to find. To make matters worse, thier next target is at the 500k range, which means another larger block of primes below that n=500k will be dropped from the list.But I suppose that is the cost of progress.

The problem with it as I see it, now most people will skip any search below the 333,333 range and then skip below the 500k range once stared by TPS, missing untold number of primes that would otherwise be found and listed.


At this late stage of the 333,333 search, knowing they will soon move on to the 500k range search, I would not be testing anything less than 500k. :Pokes: