Top person sorted by score

The Prover-Account Top 20
Persons by: number score normalized score
Programs by: number score normalized score
Projects by: number score normalized score

At this site we keep several lists of primes, most notably the list of the 5,000 largest known primes. Who found the most of these record primes? We keep separate counts for persons, projects and programs. To see these lists click on 'number' to the right.

Clearly one 100,000,000 digit prime is much harder to discover than quite a few 100,000 digit primes. Based on the usual estimates we score the top persons, provers and projects by adding ‎(log n)3 log log n‎ for each of their primes n. Click on 'score' to see these lists.

Finally, to make sense of the score values, we normalize them by dividing by the current score of the 5000th prime. See these by clicking on 'normalized score' in the table on the right.

rankpersonprimesscore
181 Oliver Kruse 11.1667 49.2917
182 Robert L. Clark 11 49.2915
183 Mariusz Ɓugowski 3 49.2873
184 Barry Walsh 6 49.2833
185 Howard Shi 5 49.2740
186 JanPeter Fischer 12 49.2729
187 Ars Technica Team Prime Rib 1 49.2624
188 Darryl Hemsley 10 49.2600
189 Florian Baur 3 49.2518
190 Greg McDevitt 11 49.2513
191 Yifei Gao 10 49.2485
192 William Byerly 7 49.2482
193 Rod Skinner 4 49.2391
194 Randy Eldredge 5 49.2255
195 Brian Parsonnet 11 49.2237
196 Frank Meador 5 49.2169
197 Scott Earle 4 49.2163
198 Ralf Terber 4 49.2125
199 Johnathan Chu 10 49.2120
200 Andrew Fitzgerald 9 49.2003

move up list ↑
move down list ↓

Notes:


Score for Primes

To find the score for a person, program or project's primes, we give each prime n the score (log n)3 log log n; and then find the sum of the scores of their primes. For persons (and for projects), if three go together to find the prime, each gets one-third of the score. Finally we take the log of the resulting sum to narrow the range of the resulting scores. (Throughout this page log is the natural logarithm.)

How did we settle on (log n)3 log log n? For most of the primes on the list the primality testing algorithms take roughly O(log(n)) steps where the steps each take a set number of multiplications. FFT multiplications take about

O( log n . log log n . log log log n )

operations. However, for practical purposes the O(log log log n) is a constant for this range number (it is the precision of numbers used during the FFT, 64 bits suffices for numbers under about 2,000,000 digits).

Next, by the prime number theorem, the number of integers we must test before finding a prime the size of n is O(log n) (only the constant is effected by prescreening using trial division).  So to get a rough estimate of the amount of time to find a prime the size of n, we just multiply these together and we get

O( (log n)3 log log n ).

Finally, for convenience when we add these scores, we take the log of the result.  This is because log n is roughly 2.3 times the number of digits in the prime n, so (log n)3 is quite large for many of the primes on the list. (The number of decimal digits in n is floor((log n)/(log 10)+1)).

Printed from the PrimePages <t5k.org> © Reginald McLean.