k=411 goof and reservation
 

NPLB had originally excluded k=411 for the range of n=260K-400K because of a reservation at Primesearch by G127.

Some way or another, I ended up reserving n=300K-400K for NPLB. In looking at the reservation date, I see what happened. G127 unreserved the range of n=300K-400K meaning that he only ended up with a reservation of n=260K-300K. I then thought I missed reserving it the first time through; not checking to see what we were excluding and hence, I ended up reserving it.

To make matters worse, when entering primes the last few days for n=260K-340K, seeing that we found no primes for k=411, I completed the range of n=300K-340K and showed no primes. I guess it's kind of hard to find a prime if you don't search it! :smile:

So...I'll have to clean up the mess. I'll pull 3 CPU's from other efforts and reserve k=411 from n=260K-400K and test it. n=260K-300K will probably be a double-check of G127's effort but doing that is consistent with what we've done with our drives. If I find a prime for n=300K-340K, I'll have to have Mike Hartley uncomplete the range(s) and enter it correctly.

The good news is that I discovered this before completing ranges for n=340K-380K, which I've already done for a few k's already.

I have now removed k=411 off of the thread that shows k's excluded from NPLB searches.

Any primes found will be shown as though they were found in this drive. Karsten, no scoring necessary for the range. Only score any prime found.

Edit: I have now checked all other k's at Primesearch that we excluded, all or in part, from our searches. No other issues like this were found.

Ugh!


Gary

[quote=gd_barnes;130663]...mess...Gary[/quote]
:smile:

393.4-393.6 complete; no primes
394.4-394.6 complete; 1 new prime plus 1 confirmed prime


We are now complete to n=400K for drive 1!! I'll start verifying results and reporting n=380K-400K to Primesearch within the next couple of days. n=260K-380K has already been completely reported to Primesearch for k=400-1001.


Gary

Taking 410.4-410.6

Reserving 410.6-412.0 and 415.0-417.0 for the port 300 LLRnet server.

The lower range was previously posted manual LLR files. The server will now fill in the gap there. New manual files have been posted for 417.0-418.0.

I have dropped the file size for the manual files down to n=100 since the testing times are getting longer at this n-range.

Karsten, I'm sure you know what to do on scoring: Beginning at n=417K for this drive, the ranges will score half as much as previously.


Gary

Taking 417.0-417.2

Taking 417.2-417.5

410.2-410.4 complete. No primes. :down: That's my first team drive file to not get a prime (three files, three primes before). I've been lucky. I'd say my luck has run out, but that'd be the gambler's fallacy (could be aka the prime-searcher's fallacy :smile:). Results attached.

k=411 is now complete from n=260K-400K. 1 non-top-5000 prime previously reported.

It is included in drive 1 for n>400K.

Taking 417.5-417.7 (2 files). :smile:

417.0-417.1 completed. No primes. Results attached.