Originally posted by Keroberts1
actually i believe the reasoning for such high predictions for the final primes is because of the low proth weight K values. Being that we've been finding the lower ones first we can probably expect the final date to move up.
Wow excellent point but I'm not sure if I understand correctly, by saying up you mean sooner right?
Code:
K Probability
4847 0.98860
5359 0.99469 Prime Found
10223 0.99539
19249 0.85992
21181 0.98736
22699 0.84058
24737 0.98830
27653 0.94479
28433 0.91430 (most recent prime)
33661 0.98703
44131 0.99661 Prime Found
46157 0.87826 Prime Found
54767 0.99464 Prime Found
55459 0.99832
65567 0.83838 Prime Found
67607 0.79880
69109 0.97235 Prime Found
If you sort them by probability
Code:
K Probability
55459 0.99832
44131 0.99661 Prime Found
10223 0.99539
5359 0.99469 Prime Found
54767 0.99464 Prime Found
4847 0.98860
24737 0.98830
33661 0.98703
21181 0.98736
69109 0.97235 Prime Found
27653 0.94479
28433 0.91430 (most recent prime)
46157 0.87826 Prime Found
19249 0.85992
22699 0.84058
65567 0.83838 Prime Found
67607 0.79880
It seems to be sort of random, in other words we have removed the same amount of low probabilty as high probablility primes. I wonder what this really means...
For example if our last prime is found at 100's of G it would take alot more k/n pair testing if we eliminated the low probability primes first. (I believe the probablilites were based upon how many k/n pairs there are per n=1m range.
So is it better for the project as a whole to eliminate the low probablility first (no we can't choose) or last? Of course I'm not suggesting doing any particular k first since we don't know where primes are etc.
Interesting