Thread: Double checking
View Single Post
Old 2007-08-25, 23:58   #9
gd_barnes
 
gd_barnes's Avatar
 
May 2007
Kansas; USA

23×5×263 Posts
Default Upcoming double-check work and add'l. effort done

First some additional effort that I didn't mention from my last post. I also effectively triple-checked k=1 to 100 up to n=10K since I tested all k's <= 1001 and checking it took very little time. Of course I found no errors because it had already been double-checked.

Here is my upcoming double-check work in the order that I plan to work on it:

1. Kosmaj, I have completed sieving the entire ranges for all 6 k's that you suggested for k=109, 203, 205, 215, 217, and 257. The sieve was up to the optimum point of P=300G using sr2sieve, which left 32458 candidates to test. I have one core that I can dedicate to LLRing the entire thing starting on Monday or Tuesday. Estimated completion time is about 3 weeks.

2. I am currently LLRing the entire range of k=1 to 1001 from n=25K to 50K. Sieving is done but I've only had one core to dedicate to LLRing it (due to 4 cores on my high-weight LLR) and it is about 20% complete. At the rate that it is going, I'm guessing about 2 weeks to finish the LLR. Then I'll be able to double-check to that level. Since the density of problems from n=16K to 25K was large for Prime Search, I'm guessing a similar rate of problems in this range.

3. Test and check the other 4 k's with unusually large prime gaps for 300 < k < 1001 up to n=100K (that are not already done). That is k=509, 543, 599, and 737. To be done after #2 is complete. Later on, extend the range to n=150K for all 6 k's and then 200K depending on the size of the prime gaps on the individual k's.

4. Test and check primes found by others on 2 of my k's that I haven't already done. That is k=111546435 from n=120K to 200K and k=686701125 from n=60K to 173.3K. With only 2 k's, this is a smaller effort than any of the above so I'll put my very slow borrowed machine on it after it's done doing sieving on twin primes from n=15K to 20K.

5. Lowest priority after all of the above. Triple-check k < 300 up to n=50K since that is being included in all of my sieve and LLR efforts. If Kosmaj prefers, I can attempt to test and check n=100K to 125K for k < 300 but sieve and LLR time at that level is very intensive. It'll probably have to wait until after I'm done with my high-weight k testing from n=200K to 400K.



Gary
gd_barnes is offline   Reply With Quote