k's/n-ranges not searched for team drives

[henryzz]

just look at how few primes the invidual ks mini-drive has found

[gd_barnes]

Originally Posted by VBCurtis

Gary-
I have 415 sieved to 1M, and plan to take it that far.

I have no reason to think there are any unreported primes- what incentive would I have to not report something? I've never had LLR fail to print a found prime to primes.txt, but you'll get the results files when my mini-drive is done anyway, and can look them over and continue to be surprised.
-Curtis

OK, thanks. I just thought I'd check because it's easy to overlook reporting primes when searching on multiple machines, especially non-top 5000 primes.

I noticed that on k=923, you missed reporting n=296612 as prime in Dec. 2007 on the Primesearch site. Carlos found the prime for NPLB in March of this year. I just now double-checked it and it is prime.


Gary

[VBCurtis]

Well, it can't hurt me to look over the results files from the mini-drive. I believe Steven should have his part done this month, at which point I should be able to put all the results together and send them along.

The fact I missed 923 at 296 means I am not paying close enough attention, so I understand the doubt you all have. I'll be sending my results to gary, so you need not take my word for things.

415 is complete to 500k, no new primes. I am continuing to 1M on this k.
-Curtis

[gd_barnes]

Curtis,

I have double-checked your drive from n=260K-440K for all k's. No problems were found. Good work!


Gary

[gd_barnes]

I have now completed double-checking Curtis's mini-drive for n=440K-500K. Results files for the entire range of n=260K-500K are available upon request. No problems were found and one prime was confirmed for n=440K-500K:

439*2^456023-1 is prime


Karsten,

You can now reflect the following at Rieselprime.org:
k / search range / reservation status
343 / 600K / reserved by NPLB individual-k drive**
359 / 540K / reserved by NPLB*
361 / 540K / reserved by NPLB*
375 / 540K / reserved by NPLB*
415 / 500K / reserved by VBCurtis
439 / 520K / reserved by NPLB
443 / 825K / reserved by VBCurtis
449 / 520K / reserved by NPLB
457 / 520K / reserved by NPLB
479 / 520K / reserved by NPLB
505 / 520K / reserved by NPLB


Curtis, you'll just need to have k=415 searched to n=600K by year end as it is the project goal to have all k=300-1001 at n>=600K by that time. Thanks.

*Shortly I will verify the results for the 3rd drive for n=520K-540K and you will be able to change the search range for ALL k=300-400 that are currently at n=520K to n=540K.

**I will add this to our individual-k reservations drive in a little while.


Gary

[gd_barnes]

Just a note about the k's in this effort: We are now anticipating that our 1st drive will complete by Dec. 23rd.

It is already the understanding of people involved with the k's in this effort that they are to have completed their searches by year end. With this note, I want to make them aware that in conjunction with our 1st drive, I will be running a double-check to n=600K on any remaining k's that haven't already been searched by us or previously double-checked.

I will plan on completing the double-checks by Dec. 20th or 21st, which means that ALL k<=1001 will be at n=600K by Dec. 23rd!


Gary

[gd_barnes]

I have determined what is remaining from the above k's that need to be double-checked that was not already searched or double-checked by normal NPLB drives so far.

There is only a small amount left because NPLB is doing most of the searching for n=500K-600K in the 1st drive (or already done in the 3rd drive), which will be done at the completion of the 1st drive.

The double-check has now started on 2 cores. ETA is ~2-3 days, which should coincide closely with the completion of the 1st drive.

By completing this effort, it will guarantee that ALL k's 300-1001 are at n=600K. This should be the last of the little straggling efforts that are needed to put us there.

Very exciting times!


Gary

[gd_barnes]

Well...how about this for a near grand finale for the 1st drive?: I just now finished double-checking what had not already been checked in the above and low-and-behold, I found a MISSING top-5000 prime!:

415*2^548359-1 is prime!


There were 3 different manners in which these k's were finished off:

1. k=343, 359, 361, and 375 had already been double-checked by me up to n=500K and finished from n=500K-600K by the 2nd drive.

2. k=439, 443, 449, 457, 479, and 505 had already been double-checked by me up to n=500K and WILL finish n=500K-600K by the 1st drive when it is complete in the next day or so.

3. k=415 was fully excluded from our drives and had already been double-checked previously by me up to n=500K. Since it was NOT included in our first drive, I had to double-check it for n=500K-600K to guarantee that we would have all k=300-1001 complete to n=600K by year end. That is now complete.

For now, I will show the k's that are still being worked by the 1st drive at n=580K with the exception of k=443 that has already been searched much higher by Curtis. I'll change them to n=600K once the 1st drive is officially done. Of course k=415 is already at n=600K since I double-checked it that far.

Karsten, after the 1st drive is done, you can change all of the k's included in the 1st post here to n=600K (k=443 at n=1.04M) just like the other 290+ of them.

For consistency, I will add this as a new prime to our 1st drive thread in the 1st post since it had not previously been found. I'll just show it as "plus 1 other" in the # of primes found for the specific range since it wasn't in the drive to begin with. Karsten, I'm not sure how you want to show it on the NPLB 1st drive web page. That is up to you.


Gary

[gd_barnes]

Originally Posted by gd_barnes

For consistency, I will add this as a new prime to our 1st drive thread in the 1st post since it had not previously been found. I'll just show it as "plus 1 other" in the # of primes found for the specific range since it wasn't in the drive to begin with. Karsten, I'm not sure how you want to show it on the NPLB 1st drive web page. That is up to you.


Gary

Technically, for consistency, I can NOT show the missing k=415 prime that I found here in the 1st post of the 1st drive thread. If I did, I'd have to show all of the confirmed primes that I found when double-checking the rest of the k's in this thread in the 1st post of the 1st, 2nd, and 3rd drives. There's no use to go back and do all of that. It's no different than if we do a double-check on our own efforts in the future and find a missing prime.

Therefore, I am taking the k=415 prime back out of the 1st drive thread 1st post.

My logic baffles even myself at times! lol

Karsten, I don't know if this affects your NPLB drive web pages in any way but I figured I'd better mention it.


Gary

[gd_barnes]

As previously mentioned, the double-checking of this mini-drive is now complete. With the official completion of the 1st drive to n=600K, all ranges have been updated in the 1st post of this thread. That is the last update that should be needed for this effort.


Gary