20090415, 07:22  #221 
May 2007
Kansas; USA
24006_{8} Posts 
Karsten,
When you get a chance, can you process the results to me for k=14001600 and n=200K350K 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 20090415 at 08:56 
20090416, 14:16  #222 
May 2007
Kansas; USA
2×47×109 Posts 
I have completed preliminary checking on results and primes for k=14001600 and n=200K350K. 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=3002000 page is missing 1539*2^2286761. 4. The 9th drive page has 1539*2^2286761 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 20090417 at 00:01 Reason: add "out of order" wording to #4 
20090416, 21:10  #223 
Account Deleted
"Tim Sorbera"
Aug 2006
San Antonio, TX USA
17·251 Posts 
16011607 complete. 3 new primes: (1 previously reported)
1605*2^2724991 1607*2^3199081 1607*2^3391641 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^2402391 is not prime. LLR Res64: 377C6599D29D9D3A Time : 114.463 sec. Last fiddled with by MiniGeek on 20090416 at 21:13 
20090417, 01:47  #224 
May 2007
Kansas; USA
10246_{10} Posts 
Results and primes verified for k=16011607. Everything looks good.
Karsten, you'll just need to add the k=1607 primes to the k=3002000 page and the 9th drive page. Last fiddled with by gd_barnes on 20090417 at 01:49 
20090417, 02:45  #225 
May 2007
Kansas; USA
2·47·109 Posts 
Corrected results for k=14001600 for n=200K350K were recieved from Karsten. All results and primes have now been verified against the 1st post here, the k=3002000 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=14001600 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=300350 to n=700K k=350400 to n=620K (Ian and I are working on bringing this up to n=700K over the next 12 months.) k=400600 to n=660K k=600800 to n=630K k=8001001 to n=660K k=10031400 to n=500K (Peter Benson has likely completed much higher but it is not known specifically.) k=14001600 to n=520K When this drive is complete, we'll also have all k=16002000 up to n=520K plus whatever additional range the 10th drive has completed by that point. Gary 
20090421, 11:24  #226 
May 2007
Kansas; USA
2·47·109 Posts 
Reserving k=17001800 for port 9000.

20090510, 00:57  #227 
May 2007
Kansas; USA
2×47×109 Posts 
Reserving k=18002000 / n=200K350K for port 9000.
That will be all for this drive! 
20090512, 03:15  #228 
May 2008
Wilmington, DE
2^{2}·23·31 Posts 
That last range we added to IB9000 is not in kn sequence but in n sequence. This is going to be a mess to keep straight.

20090512, 03:37  #229 
A Sunny Moo
Aug 2007
USA (GMT5)
3×2,083 Posts 
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=18002000 range is complete.

20090512, 08:24  #230 
Mar 2006
Germany
2^{3}×3×7×17 Posts 
that's right!
i used to process the results, if a whole kvalue was checked from n=200k to 350k. now i have to wait until the krange from 1801 to 1999 is complete! 
20090512, 12:54  #231 
May 2007
Kansas; USA
24006_{8} 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=10032000 range for the next nrange 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=18002000 ranges, it makes it hard to list them in the 1st post here. Ian, I'll assist with keeping them in kvalue sequence here if you want. Gary Last fiddled with by gd_barnes on 20090512 at 12:55 
Thread Tools  
Similar Threads  
Thread  Thread Starter  Forum  Replies  Last Post 
Team drive #10 k=14002000 n=500K1M  gd_barnes  No Prime Left Behind  61  20130130 16:08 
Team drive #12 k=20003000 n=50K425K  gd_barnes  No Prime Left Behind  96  20120219 03:53 
Team drive #11 k=20003000 n=425K600K  gd_barnes  No Prime Left Behind  42  20101119 10:42 
Team drive #8 k=14002000 n=350K500K  gd_barnes  No Prime Left Behind  101  20090408 02:11 
Sieving drive for k=10052000 n=200K500K  gd_barnes  No Prime Left Behind  118  20090117 16:05 