Results files, checking, & Primesearch reporting

[gd_barnes]

I have now looked for all the results files that I have received on all drives for n=260K-393K. I have sent PM's and Emails when necessary to attempt to locate missing results.

If you haven't gotten a PM or Email from me, thanks for forwarding them all to me.

There were really very few missing results. On drive 3, I have ALL results for n=260K-373.8K!

In doing all of this, I was able to do the following for ranges where I had all of the results files:

1. Verification of ALL primes for drive 3 for n=260K-373.8K in post 1 of the drive thread, on Karsten's drive 3 web page, and on Karsten's Rieselprime page for k=300-2000. NO ERRORS OR MISSING PRIMES were found! Nice work Karsten for such a large range! Nice work Anon with the results files and helping keep post 1 of the thread updated!

2. Report all primes and ranges at the Primesearch site (that weren't already reserved by others) on drive 3 for n=260K-360K. I just completed that earlier today.

3. I previously verified primes for drives 1 & 2 for n=320K-340K in post 1 of the drive thread, on Karsten's drives 1 & 2 web pages, and on Karsten's Rieselprime page for k=300-2000. Once again, no errors or missing primes were found on his pages. I previously added one missing prime to post 1 of drive 2.

4. Report all primes and ranges at the Primesearch site for drives 1 and 2 for n=320K-340K. I completed that yesterday. I couldn't do it previously because the site kept having problems at the time.

I just need a few more straggling results files from 3 people to fully complete the reporting of n=260K-320K to Primesearch for drive 2.

With just this small percentage of ranges and primes reported complete to Primesearch, we're already 6th place on # of digits in our primes and 12th place both for prime count and ranges searched. Once I'm able to report n=260K-320K for drive 2, we may be near the top on digits and top 5 or better on the other 2 categories.

I now have reserved at Primesearch up to n=480K on drive 1 and up to n=420K on drive 2. It's a tedious time-consuming process to reserve them and report them complete for such a large # of ranges. I'll be glad when I can complete n=260K-320K.

I also reserved n=100K-260K for k=1-100 for our double-check drive. Even though all (or most) of the primes will have been found previously, they haven't been reported at Primesearch because k=1-300 was only added there in the last 1-2 years. It may as well get done now with our effort. k=300-1001 has already been completed at the site for the n-range. After I see how we are progressing on the double-check drive (I'll be adding 2-3 cores to it next week), I may reserve all or a portion of k=100-300 for the n-range. I try not to reserve anything that can't be completed in 2 months. Their ranges 'expire' in 2 months, which is really only a guideline that means the admin, at his discretion, can unreserve the ranges for you if he thinks they won't be done. (very rare I think)

Congrats to everyone on some nice work!


Gary

[mdettweiler]

You mentioned about straggling ranges with results still missing for Drive #2--just to let you know, I'll try to get the LLRnet results file for Beyond's range 302K-205K processed as soon as possible. The problem is that I am really busy this weekend and might not get the chance to do it until a little later. Gary, you may as well consider the results for 302K-305K accounted for, since I have the results files and just need yet to get them processed.

[gd_barnes]

Originally Posted by Anonymous

You mentioned about straggling ranges with results still missing for Drive #2--just to let you know, I'll try to get the LLRnet results file for Beyond's range 302K-205K processed as soon as possible. The problem is that I am really busy this weekend and might not get the chance to do it until a little later. Gary, you may as well consider the results for 302K-305K accounted for, since I have the results files and just need yet to get them processed.

OK, no problem. What I do is compare primes in the results files with what is reported in post 1 of the drive thread, on Karsten's k=300-2000 page, and on Karsten's NPLB drive page.

If you don't have time to process the results but have time to check the primes found in them against the primes in post 1 of the drive thread, that'd be helpful. But if not, no big deal.

302K-305K is the only range in the 300K-320K Primesearch range I'm missing. I just recently got everything in the 260K-280K range and will shortly check that range.


Gary

[mdettweiler]

Originally Posted by gd_barnes

OK, no problem. What I do is compare primes in the results files with what is reported in post 1 of the drive thread, on Karsten's k=300-2000 page, and on Karsten's NPLB drive page.

If you don't have time to process the results but have time to check the primes found in them against the primes in post 1 of the drive thread, that'd be helpful. But if not, no big deal.

302K-305K is the only range in the 300K-320K Primesearch range I'm missing. I just recently got everything in the 260K-280K range and will shortly check that range.


Gary

If you want, I can just forward you the big LLRnet results files--they still have the primes listed just like normally, except that things are somewhat out of order, and that there's lines for username and date in there too. Anyway, it shouldn't be a problem if you're just using the "find" feature in Notepad/Wordpad/etc. to locate primes in the file.

[mdettweiler]

Well, I've almost got the processing of the 302K-305K results completed, so I should have the lresults file sent to Gary within the next half hour. Then we'll be able to report the entire 2nd Drive range as complete on PrimeSearch!

Edit: Okay, I've got the results processed now! They will be mailed to Gary as soon as I'm finished editing this message.

[gd_barnes]

Processing and verification of all results files up to n=380K is now complete for drive 1. All primes were checked vs. the 1st post of drive 1, Karsten's NPLB drive 1 page, and Karsten's k=300-2000 page. He is still working on entering primes and updating ranges on his pages.

All ranges have been completed and all primes have been entered at Primesearch with the exception of k=411 that I am working on now.

I will be complete with a couple of file reservations by Saturday for n=393K-395K on drive 1, which is all that is remaining up to n=400K there. I will then start the process for n=380K-400K.

Anon has found some missing results in an LLRnet range for n=373.8K-400K for drive 3. Everything had previously been checked for that drive up to n=360K. Once testing is done and the missing results are processed, I'll then start the above process for n=360K-400K for drive 3.

Within < 2 weeks, we should have everything complete, checked, and entered in all locations up to n=400K!!

On Primesearch, we are now 3rd on ranges completed, 5th on primes found, and....drum roll....FIRST on the # of digits in primes!

Way to go team!

[kar_bon]

Originally Posted by gd_barnes

(...)
Anon has found some missing results in an LLRnet range for n=373.8K-400K for drive 3. Everything had previously been checked for that drive up to n=360K. Once testing is done and the missing results are processed, I'll then start the above process for n=360K-400K for drive 3.

i've sent David the missing pairs in that range (about 3000) and he appended them again at his server:

Port 5000 has 12412 lines in knpairs.txt
File size of 136,545
first k/n pair 385 450337
last k/n pair 351 399121

see last pair! there are the missing ones!
so about 9000 other pairs upto n=460k to be done first!

[IronBits]

It was exactly 2,679 pairs

[gd_barnes]

OK, let's make port 5000 on drive 3 a priority for a while.

If you finish a range or need some filler work, please put it on port 5000 to get all results to n=460K processed so that we can then process the missing results.

There are no previously known primes from the current n-value in port 5000 up to n=463K so plenty of primes waiting to be found!


Thanks,
Gary

[mdettweiler]

Originally Posted by gd_barnes

OK, let's make port 5000 on drive 3 a priority for a while.

If you finish a range or need some filler work, please put it on port 5000 to get all results to n=460K processed so that we can then process the missing results.

There are no previously known primes from the current n-value in port 5000 up to n=463K so plenty of primes waiting to be found!


Thanks,
Gary

I've put one core on port 5000, and will add the other as soon as it finishes its Doublecheck Drive #1 range.