Team drive #9 k=1005-2000 n=50K-350K - Page 21

gd_barnes · 2009-04-15, 07:22

Karsten,

When you get a chance, can you process the results to me for k=1400-1600 and n=200K-350K for this drive.

It's a huge amount of results so take your time with it.

Thanks,
Gary

kar_bon: all sent!

gd_barnes · 2009-04-16, 14:16

I have completed preliminary checking on results and primes for k=1400-1600 and n=200K-350K. Several problems were found:

1. A k was missing from one of the results files. Karsten, see your Email.

2. There were 8 missing and 2 incorrect primes in the 1st post of this drive. The primes and counts have now been corrected.

3. The k=300-2000 page is missing 1539*2^228676-1.

4. The 9th drive page has 1539*2^228676-1 out of order within the k.

After I get the corrected results, I'll complete final checking.

Gary

Mini-Geek · 2009-04-16, 21:10

1601-1607 complete. 3 new primes: (1 previously reported)
1605*2^272499-1
1607*2^319908-1
1607*2^339164-1
The results are too large to attach here, so I emailed them to Gary.
I started on the port for the rally. I'll resume my individual k reservation after the rally.
Edit: Oh yeah, just remembered, one result got put in an lprime.log file. (and I forgot to add it to the zip of results that I sent) Here it is:

Code:

1603*2^240239-1 is not prime.  LLR Res64: 377C6599D29D9D3A  Time : 114.463 sec.

gd_barnes · 2009-04-17, 01:47

Results and primes verified for k=1601-1607. Everything looks good.

Karsten, you'll just need to add the k=1607 primes to the k=300-2000 page and the 9th drive page.

gd_barnes · 2009-04-17, 02:45

Corrected results for k=1400-1600 for n=200K-350K were recieved from Karsten. All results and primes have now been verified against the 1st post here, the k=300-2000 page, and the 9th drive page. Everything now checks out.

Karsten, this means something that warms my heart greatly: After you post that one missing prime stated in the prior post, you can now show all k=1400-1600 as complete to n=520K and remove most of those annoying (...) symbols!

[For the uninitiated, that means a testing gap.]

Gentlemen, very nice work on filling in this porous area of the primes world that had been previously searched in a fragmented and incomplete manner. All primes are now known and we now know exactly how many primes each k contains for the following ranges:

k=300-350 to n=700K
k=350-400 to n=620K (Ian and I are working on bringing this up to n=700K over the next 1-2 months.)
k=400-600 to n=660K
k=600-800 to n=630K
k=800-1001 to n=660K
k=1003-1400 to n=500K (Peter Benson has likely completed much higher but it is not known specifically.)
k=1400-1600 to n=520K

When this drive is complete, we'll also have all k=1600-2000 up to n=520K plus whatever additional range the 10th drive has completed by that point.

Gary

gd_barnes · 2009-04-21, 11:24

Reserving k=1700-1800 for port 9000.

gd_barnes · 2009-05-10, 00:57

Reserving k=1800-2000 / n=200K-350K for port 9000.

That will be all for this drive!

MyDogBuster · 2009-05-12, 03:15

That last range we added to IB9000 is not in k-n sequence but in n sequence. This is going to be a mess to keep straight.

mdettweiler · 2009-05-12, 03:37

Quote:

Originally Posted by MyDogBuster

That last range we added to IB9000 is not in k-n sequence but in n sequence. This is going to be a mess to keep straight.

Hmm...I see. Well, that shouldn't make much of a difference on the processing end of things, since the results are out of order anyway (being recorded as they come in) and need to be sorted; though, it will mean that none of these ranges can be processed until the entire k=1800-2000 range is complete.

kar_bon · 2009-05-12, 08:24

that's right!

i used to process the results, if a whole k-value was checked from n=200k to 350k.

now i have to wait until the k-range from 1801 to 1999 is complete!

gd_barnes · 2009-05-12, 12:54

CRAP CRAP CRAP!! Yep, that's how I sent it alright. Since k>1800 is already being processed, it's too late now and would be a big mess to attempt to retract it at this point. Thankfully it's the final file of the drive, which makes it less of a problem.

I'm sorry Karsten. Man, it's hard to keep all of these 10's of files on multiple drives straight. One time, I almost sent the entire k=1003-2000 range for the next n-range on port 8000. Now, THAT would have been a real mess!

Besides making it annoying for Karsten by forcing him to wait until the end to finalize any k=1800-2000 ranges, it makes it hard to list them in the 1st post here. Ian, I'll assist with keeping them in k-value sequence here if you want.

Gary

2009-04-15, 07:22	#221
gd_barnes May 2007 Kansas; USA 2844₁₆ Posts	Karsten, When you get a chance, can you process the results to me for k=1400-1600 and n=200K-350K for this drive. It's a huge amount of results so take your time with it. Thanks, Gary kar_bon: all sent! Last fiddled with by kar_bon on 2009-04-15 at 08:56

2009-04-16, 14:16	#222
gd_barnes May 2007 Kansas; USA 2²·3·859 Posts	I have completed preliminary checking on results and primes for k=1400-1600 and n=200K-350K. Several problems were found: 1. A k was missing from one of the results files. Karsten, see your Email. 2. There were 8 missing and 2 incorrect primes in the 1st post of this drive. The primes and counts have now been corrected. 3. The k=300-2000 page is missing 15392^228676-1. 4. The 9th drive page has 15392^228676-1 out of order within the k. After I get the corrected results, I'll complete final checking. Gary Last fiddled with by gd_barnes on 2009-04-17 at 00:01 Reason: add "out of order" wording to #4

2009-04-16, 21:10	#223
Mini-Geek Account Deleted "Tim Sorbera" Aug 2006 San Antonio, TX USA 17·251 Posts	1601-1607 complete. 3 new primes: (1 previously reported) 16052^272499-1 16072^319908-1 16072^339164-1 The results are too large to attach here, so I emailed them to Gary. I started on the port for the rally. I'll resume my individual k reservation after the rally. Edit: Oh yeah, just remembered, one result got put in an lprime.log file. (and I forgot to add it to the zip of results that I sent) Here it is: Code: 16032^240239-1 is not prime. LLR Res64: 377C6599D29D9D3A Time : 114.463 sec. Last fiddled with by Mini-Geek on 2009-04-16 at 21:13

2009-04-17, 01:47	#224
gd_barnes May 2007 Kansas; USA 2²×3×859 Posts	Results and primes verified for k=1601-1607. Everything looks good. Karsten, you'll just need to add the k=1607 primes to the k=300-2000 page and the 9th drive page. Last fiddled with by gd_barnes on 2009-04-17 at 01:49

2009-05-12, 12:54	#231
gd_barnes May 2007 Kansas; USA 2²·3·859 Posts	CRAP CRAP CRAP!! Yep, that's how I sent it alright. Since k>1800 is already being processed, it's too late now and would be a big mess to attempt to retract it at this point. Thankfully it's the final file of the drive, which makes it less of a problem. I'm sorry Karsten. Man, it's hard to keep all of these 10's of files on multiple drives straight. One time, I almost sent the entire k=1003-2000 range for the next n-range on port 8000. Now, THAT would have been a real mess! Besides making it annoying for Karsten by forcing him to wait until the end to finalize any k=1800-2000 ranges, it makes it hard to list them in the 1st post here. Ian, I'll assist with keeping them in k-value sequence here if you want. Gary Last fiddled with by gd_barnes on 2009-05-12 at 12:55

2009-04-17, 02:45	#225
gd_barnes May 2007 Kansas; USA 2844₁₆ Posts	Corrected results for k=1400-1600 for n=200K-350K were recieved from Karsten. All results and primes have now been verified against the 1st post here, the k=300-2000 page, and the 9th drive page. Everything now checks out. Karsten, this means something that warms my heart greatly: After you post that one missing prime stated in the prior post, you can now show all k=1400-1600 as complete to n=520K and remove most of those annoying (...) symbols! [For the uninitiated, that means a testing gap.] Gentlemen, very nice work on filling in this porous area of the primes world that had been previously searched in a fragmented and incomplete manner. All primes are now known and we now know exactly how many primes each k contains for the following ranges: k=300-350 to n=700K k=350-400 to n=620K (Ian and I are working on bringing this up to n=700K over the next 1-2 months.) k=400-600 to n=660K k=600-800 to n=630K k=800-1001 to n=660K k=1003-1400 to n=500K (Peter Benson has likely completed much higher but it is not known specifically.) k=1400-1600 to n=520K When this drive is complete, we'll also have all k=1600-2000 up to n=520K plus whatever additional range the 10th drive has completed by that point. Gary

2009-04-21, 11:24	#226
gd_barnes May 2007 Kansas; USA 2²×3×859 Posts	Reserving k=1700-1800 for port 9000.

2009-05-10, 00:57	#227
gd_barnes May 2007 Kansas; USA 24104₈ Posts	Reserving k=1800-2000 / n=200K-350K for port 9000. That will be all for this drive!

2009-05-12, 03:15	#228
MyDogBuster May 2008 Wilmington, DE 2²×23×31 Posts	That last range we added to IB9000 is not in k-n sequence but in n sequence. This is going to be a mess to keep straight.

2009-05-12, 08:24	#230
kar_bon Mar 2006 Germany B3D₁₆ Posts	that's right! i used to process the results, if a whole k-value was checked from n=200k to 350k. now i have to wait until the k-range from 1801 to 1999 is complete!

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
Team drive #10 k=1400-2000 n=500K-1M	gd_barnes	No Prime Left Behind	61	2013-01-30 16:08
Team drive #12 k=2000-3000 n=50K-425K	gd_barnes	No Prime Left Behind	96	2012-02-19 03:53
Team drive #11 k=2000-3000 n=425K-600K	gd_barnes	No Prime Left Behind	42	2010-11-19 10:42
Team drive #8 k=1400-2000 n=350K-500K	gd_barnes	No Prime Left Behind	101	2009-04-08 02:11
Sieving drive for k=1005-2000 n=200K-500K	gd_barnes	No Prime Left Behind	118	2009-01-17 16:05