Team drive #1: k=400-1001 n=333.2K-600K - Page 20

gd_barnes · 2008-04-03, 21:14

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!

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

Flatlander · 2008-04-04, 00:28

Quote:

Originally Posted by gd_barnes

...mess...Gary

gd_barnes · 2008-04-05, 14:42

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

Mini-Geek · 2008-04-07, 20:08

Taking 410.4-410.6

gd_barnes · 2008-04-09, 15:56

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

Mini-Geek · 2008-04-11, 10:59

Taking 417.0-417.2

Mini-Geek · 2008-04-11, 16:07

Taking 417.2-417.5

Mini-Geek · 2008-04-13, 11:21

410.2-410.4 complete. No primes.

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

). Results attached.

gd_barnes · 2008-04-16, 04:55

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.

mdettweiler · 2008-04-17, 02:22

Taking 417.5-417.7 (2 files).

Mini-Geek · 2008-04-19, 23:59

417.0-417.1 completed. No primes. Results attached.

2008-04-03, 21:14	#210
gd_barnes May 2007 Kansas; USA 29×359 Posts	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! 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 Last fiddled with by gd_barnes on 2008-04-03 at 21:15

2008-04-09, 15:56	#214
gd_barnes May 2007 Kansas; USA 29·359 Posts	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 Last fiddled with by gd_barnes on 2008-04-09 at 15:58

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Team drive #14: k=600-1001 n=1M-2M	mdettweiler	No Prime Left Behind	10	2021-03-13 22:32
Team drive #7 k=800-1001 n=600K-1M	gd_barnes	No Prime Left Behind	127	2011-07-15 14:25
Team drive #6 k=600-800 n=600K-1M	gd_barnes	No Prime Left Behind	89	2011-03-10 12:34
Team drive #5: k=400-600 n=600K-1M	gd_barnes	No Prime Left Behind	135	2010-11-23 14:27
Team drive #4, 15 k's < 300 for n=600K-1M	gd_barnes	No Prime Left Behind	38	2008-10-22 16:20

2008-04-05, 14:42	#212
gd_barnes May 2007 Kansas; USA 29×359 Posts	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

2008-04-07, 20:08	#213
Mini-Geek Account Deleted "Tim Sorbera" Aug 2006 San Antonio, TX USA 17·251 Posts	Taking 410.4-410.6

2008-04-11, 10:59	#215
Mini-Geek Account Deleted "Tim Sorbera" Aug 2006 San Antonio, TX USA 17×251 Posts	Taking 417.0-417.2

2008-04-11, 16:07	#216
Mini-Geek Account Deleted "Tim Sorbera" Aug 2006 San Antonio, TX USA 10253₈ Posts	Taking 417.2-417.5

2008-04-16, 04:55	#218
gd_barnes May 2007 Kansas; USA 29·359 Posts	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.

2008-04-17, 02:22	#219
mdettweiler A Sunny Moo Aug 2007 USA (GMT-5) 3×2,083 Posts	Taking 417.5-417.7 (2 files).