Sierp base 3  minidrive Ia
We have started a mini drive for Sierp base 3. The range is k<50M and n=35K100K.
There were 154 k's remaining to begin with. The drive found 81 k's with primes so there are now 73 k's remaining for this krange. This is a very lowintensity drive. The files are small and you should be able to complete files at the current nrange in 47 days. Feel free to grab several if you like. As we find primes, like I did with primes that were previously found, we'll remove k's from files for larger nranges. Files up to n=100K are fully sieved to P=175G. Primes found: [code] prime found by 23243282*3^99009+1 Flatlander 29548672*3^96142+1 Flatlander 35382962*3^93533+1 Flatlander 48652642*3^92392+1 Flatlander 39809884*3^91905+1 Flatlander 28071866*3^91455+1 Flatlander 26261252*3^91020+1 Flatlander 30440162*3^90938+1 Flatlander 40809266*3^89759+1 Flatlander 9690724*3^87558+1 Flatlander 44249222*3^85781+1 henryzz 21175348*3^84575+1 em99010pepe 7111766*3^84512+1 em99010pepe 41118464*3^82674+1 em99010pepe 8090242*3^81633+1 em99010pepe 47214478*3^80452+1 em99010pepe 36173524*3^78327+1 em99010pepe 16693364*3^77129+1 em99010pepe 39834376*3^76224+1 nuggetprime 25207316*3^76109+1 nuggetprime 29450654*3^76010+1 nuggetprime 26393956*3^75239+1 nuggetprime 42497116*3^75136+1 nuggetprime 46490116*3^74892+1 nuggetprime 9240646*3^74356+1 nuggetprime 29348458*3^71822+1 michaf 9483244*3^65267+1 michaf 11242904*3^64614+1 michaf 42216418*3^64227+1 michaf 10224166*3^59777+1 em99010pepe 14994106*3^57376+1 em99010pepe 3938414*3^56779+1 em99010pepe 34960988*3^56350+1 em99010pepe 20856328*3^56338+1 em99010pepe 46511144*3^56138+1 em99010pepe 28964426*3^52608+1 em99010pepe 24925372*3^51893+1 em99010pepe 40316644*3^51786+1 em99010pepe 6859514*3^51502+1 em99010pepe 48886226*3^51212+1 em99010pepe 11785058*3^50252+1 em99010pepe 6123394*3^49821+1 em99010pepe 24763868*3^49675+1 em99010pepe 41443828*3^49528+1 em99010pepe 35164256*3^47916+1 em99010pepe 48563402*3^47888+1 em99010pepe 15895156*3^47532+1 em99010pepe 12087826*3^47344+1 em99010pepe 48501008*3^46896+1 em99010pepe 5574644*3^46587+1 em99010pepe 8828234*3^46265+1 em99010pepe 15396762*3^46233+1 em99010pepe 24725744*3^46211+1 em99010pepe 10504636*3^46184+1 em99010pepe 38804354*3^45875+1 em99010pepe 37160146*3^45496+1 em99010pepe 37158138*3^45035+1 em99010pepe 30237632*3^44437+1 em99010pepe 19947516*3^44420+1 em99010pepe 40677134*3^43415+1 em99010pepe 29772794*3^43415+1 em99010pepe 23862908*3^42999+1 em99010pepe 14892316*3^42972+1 em99010pepe 12203572*3^42792+1 em99010pepe 19450274*3^41878+1 Lennart 20258534*3^41706+1 Lennart 27704962*3^41561+1 Lennart 25095394*3^41459+1 Lennart 16939082*3^40745+1 Lennart 23727272*3^40665+1 Lennart 47807146*3^39904+1 Lennart 30032708*3^39872+1 Lennart 20436272*3^38146+1 CedricVonck 30494864*3^37165+1 MiniGeek 26804972*3^36314+1 henryzz 14454556*3^36283+1 henryzz 11658664*3^35879+1 CedricVonck 32565374*3^35794+1 CedricVonck 28675334*3^35458+1 CedricVonck 38353046*3^35109+1 CedricVonck 12562406*3^35092+1 CedricVonck [/code]Reservations: [code] range tested by status # primes 86K100K Flatlander complete 10 85K86K henryzz complete 1 77K85K em99010pepe complete 7 73K77K nuggetprime complete 7 67K73K michaf complete 1 66K67K nuggetprime complete 0 64K66K michaf complete 3 63K64K mdettweiler complete 0 62K63K michaf complete 0 42K62K em99010pepe complete 35 39K42K Lennart complete 8 38K39K CedricVonck complete 1 37K38K MiniGeek complete 1 36K37K henryzz complete 2 35K36K CedricVonck complete 5 [/code] [B]The drive is now complete. Thanks to all who helped![/B] Have fun and knock out a bunch of k's! :smile: Gary 
reserving : 35K36K

reserving : 36K37K

Two primes found:
12562406 35092 38353046 35109 Do I have to remove these k's (12562406 & 38353046 )from imy nput file? 
Taking 37K38K. Removing the two k's that Cedric found primes for.
This is mainly to balance the amount of work on my NPLB 530.0530.6 range between my cores. For some reason, 530.3530.6 has way more pairs to test that 530.0530.3 did, and I'd like to find a few small primes anyway. :smile: Edit: If I find a PRP with this, should I just report it here as a PRP or check it first? Either way, how do I check it for 100% certain primality instead of just PRP? 
[quote=MiniGeek;138448]Taking 37K38K. Removing the two k's that Cedric found primes for.
This is mainly to balance the amount of work on my NPLB 530.0530.6 range between my cores. For some reason, 530.3530.6 has way more pairs to test that 530.0530.3 did, and I'd like to find a few small primes anyway. :smile: Edit: If I find a PRP with this, should I just report it here as a PRP or check it first? Either way, how do I check it for 100% certain primality instead of just PRP?[/quote] u can use pfgw to prove them prime the options t tp and tc all prove primality 
[quote=CedricVonck;138446]Two primes found:
12562406 35092 38353046 35109 Do I have to remove these k's (12562406 & 38353046 )from imy nput file?[/quote] Yes, remove them (though if it's too much of a hassle, don't worry about it). Just a little warning, though: after you've removed the k's from the input file, make sure you adjust the current line being processed as stored in llr.iniotherwise, you'll end up skipping a whole chunk of the file. 
[quote=henryzz;138452]u can use pfgw to prove them prime
the options t tp and tc all prove primality[/quote] You would use the t option for +1 tests. tp is for 1 tests. tc tests both but is generally used for random forms (i.e. k*b^n+7) and would take an unnecessary amount of time for +1 or 1 tests. Gary 
[quote=CedricVonck;138446]Two primes found:
12562406 35092 38353046 35109 Do I have to remove these k's (12562406 & 38353046 )from imy nput file?[/quote] At this low nrange with so many k's remaining, I wouldn't even mess with removing them from your current file. Removing 2 out of 154 k's will only save you about 2 / 154 = 1.3% CPU time. I'll get them removed from the n>38K files later today. Gary 
30494864*3^37165+1 is prime! (from PFGW, so this is verified)
Removing from my file... I used t. It only took 10 seconds longer than it took to PRP it (~41 vs ~31). Edit: Is there any existing tool to more easily remove a k from an LLRformatted file? I'm not worried about the line number, as I could manually clear out the ones I've finished and restart it on line 1, but the new line number you need to run on would be nice too. 
[quote=MiniGeek;138470]Edit: Is there any existing tool to more easily remove a k from an LLRformatted file? I'm not worried about the line number, as I could manually clear out the ones I've finished and restart it on line 1, but the new line number you need to run on would be nice too.[/quote]
Never mind, I noticed that srfile can do this and found the command. (I can't still edit the above post.) 
[quote=MiniGeek;138473]Never mind, I noticed that srfile can do this and found the command. (I can't still edit the above post.)[/quote]
I've written a little Perl script that simplifies the process of running srfile to remove multiple k's (or just one, though if you're only removing one k you may as well just use srfile directly)essentially, it takes an input file in any format srfile supports, removes all the k's listed in a given file (one sequence on each line, in the same format as you'd use normally with srfile), and outputs in either NewPGen, ABC, or ABCD format. If anyone wants a copy of the program, just [email=bugmesticky@googlemail.com]email me[/email]. :smile: 
[quote=Anonymous;138476]I've written a little Perl script that simplifies the process of running srfile to remove multiple k's (or just one, though if you're only removing one k you may as well just use srfile directly)essentially, it takes an input file in any format srfile supports, removes all the k's listed in a given file (one sequence on each line, in the same format as you'd use normally with srfile), and outputs in either NewPGen, ABC, or ABCD format.
If anyone wants a copy of the program, just [EMAIL="bugmesticky@googlemail.com"]email me[/EMAIL]. :smile:[/quote] You can also use a batch process, which is what I do. Here is what I put in a file to remove the 3 k's with primes from the n=35K50K files: [code] srfile G d "12562406*3^n+1" sievesierpbase30M50M35K50K.txt srfile G d "30494864*3^n+1" t16_b3.prp srfile G d "38353046*3^n+1" t16_b3.prp copy t16_b3.prp sievesierpbase30M50M35K50Kb.txt del t16_b3.prp [/code] Just give the file a .bat extension and run it at the command prompt. Gary 
it looks like i am the unlucky one i am 23% done without a prime when CedricVonck has two primes at 11% and MiniGeek has one at 17%

14454556*3^36283+1 is prime

28675334 35458 is prime!

26804972*3^36314+1 is prime!

32565374 35794 is prime!

11658664 35879 is prime!

Range done  following primes found
[CODE]12562406 35092 38353046 35109 28675334 35458 32565374 35794 11658664 35879[/CODE] 
reserving 38k  39k

LLR
reserving 39k  42k
/Lennart 
1 Attachment(s)
3738 complete, 1 prime already reported. Just one prime...just...one...lone...Cedric got five and henry got two already and I get one. Oh well, that's the randomness of prime distribution for you...
Do you need the lresults? Edit: Ok, I attached the lresults. 
[quote=MiniGeek;138536]3738 complete, 1 prime already reported. Just one prime...just...one...lone...Cedric got five and henry got two already and I get one. Oh well, that's the randomness of prime distribution for you...
Do you need the lresults?[/quote] Yes, if people can post their lresults, that would be helpful. Thanks. 
1 Attachment(s)
Already 1 new prime to report
20436272 38146 
Result
1 Attachment(s)
4041 complete
Primes 23727272 40665 16939082 40745 /Lennart 
Result
1 Attachment(s)
3940 complete
Primes 32565374 39621 30032708 39872 47807146 39904 /Lennart 
1 Attachment(s)
41k42k
Primes 20436272 41381 25095394 41459 27704962 41561 20258534 41706 19450274 41878 /Lennart 
I have posted all primes found recently. The 9 k's will be removed from the remaining files shortly.
Lennart, on this effort, I'm only showing the lowest prime found for each k to help in 'balancing' the # of k's remaining. 2 of your k's that had primes already had lower primes so they are not being shown in post 1 of this thread. For everyone, I like to see the lowest prime found for each k so if someone finds a prime in a higher nrange than what you are searching, please leave that k in your file(s) to see if a lower prime is found. Of course it can be removed if you are searching a higher nrange. Edit: All k's with primes have now been removed. Gary 
Gary, can you send me the sieve file,
I have one core freed up now :) Also: what is the ideal sieve depth? thanks :) 
Taking 4250 (8 files). ETA ~24 hours.

[quote=michaf;138608]Gary, can you send me the sieve file,
I have one core freed up now :) Also: what is the ideal sieve depth? thanks :)[/quote] Well, I goofed. I accidently deleted my n=50K100K file that was sieved to P=100G. Fortunately I have a backup file but unfortunately it is only sieved to P=20G. I'm in the middle of sieving it to P=60G on 2 cores and will be done with that on Friday. I could send you the file sieved to P=20G now and it would only take a little bit longer to sieve for P>60G. Or I could send you a file sieved to P=60G on Friday. Let me know which you'd prefer. My estimate of the optimum sieve depth for breaking off n=50K75K would be around P=150175G but it could be lower...around P=120130G. The optimum is not going to come in much higher than the optimum for n=25K50K (P=100G) because there are going to be many less k's remaining. Do you want to sieve from P=60G to P=~150G175G yourself or do you need help? I assume you know to use srsieve for sieving. If you use more than one core, be sure and use the f switch for all instances so that it will write out factors for all of them for later removal. Gary 
1 Attachment(s)
38K39K Range Complete 1 prime found

1 Attachment(s)
36K37K Range Complete 2 primes found

To the sievers, primes found so far:
[quote] 19947516 44420 10504636 46184 24725744 46211 15396762 46233 8828234 46265 [/quote] 
I think I can use some help...
I only have one core free to chime in. I opt for the file on friday, and then distribute the load between us (or more people) to get to concluding the drive sooner. [quote=gd_barnes;138631]Well, I goofed. I accidently deleted my n=50K100K file that was sieved to P=100G. Fortunately I have a backup file but unfortunately it is only sieved to P=20G. I'm in the middle of sieving it to P=60G on 2 cores and will be done with that on Friday. I could send you the file sieved to P=20G now and it would only take a little bit longer to sieve for P>60G. Or I could send you a file sieved to P=60G on Friday. Let me know which you'd prefer. My estimate of the optimum sieve depth for breaking off n=50K75K would be around P=150175G but it could be lower...around P=120130G. The optimum is not going to come in much higher than the optimum for n=25K50K (P=100G) because there are going to be many less k's remaining. Do you want to sieve from P=60G to P=~150G175G yourself or do you need help? I assume you know to use srsieve for sieving. If you use more than one core, be sure and use the f switch for all instances so that it will write out factors for all of them for later removal. Gary[/quote] 
[quote=michaf;138645]I think I can use some help...
I only have one core free to chime in. I opt for the file on friday, and then distribute the load between us (or more people) to get to concluding the drive sooner.[/quote] OK, I'll send you the file sieved to P=60G on Friday. My 2 cores are kind of slow; 32bit operating system; but still sufficient for this small effort. If you want to sieve P=60G100G, I'll sieve P=100G150G or whatever optimal turns out to be. If it needs to be sieved further, we can coordinate at that point. I can sieve P=~20G per day so my 50G range would take 23 days, which would put it done to P=150G sometime on Monday. Gary 
[quote=em99010pepe;138642]To the sievers, primes found so far:[/quote]
Carlos, Thanks for helping and posting some primes now. Micha, Whatever k's Carlos finds primes for, I'll remove from the sieve file before sending to you on Friday. He said it'd be ~24 hours to complete his range so that timing would work out well. Gary 
Gary,
Here's another one: 30237632 44437 ETA is 32 hours...I think by tomorrow at this time all ranges will be completed. Carlos 
[quote=em99010pepe;138654]Gary,
Here's another one: 30237632 44437 ETA is 32 hours...I think by tomorrow at this time all ranges will be completed. Carlos[/quote] Great. My sieving to P=60G should complete by this time tomorrow plus ~2 hours, i.e. ~26 hours from now. So we'll have a nice efficient file to sieve for P>60G. 
12203572 42792
14892316 42972 23862908 42999 29772794 43415 40677134 43415 37158138 45035 37160146 45496 38804354 45875 5574644 46587 48501008 46896 12087826 47344 15895156 47532 48563402 47888 35164256 47916 41443828 49528 24763868 49675 6123394 49821 
4244 done.
[URL="http://em99010pepe.googlepages.com/lresults_42K44K.txt"]lresults_42K44K[/URL] 
4446 done.
[URL="http://em99010pepe.googlepages.com/lresults_44K46K.txt"]lresults_44K46K.txt[/URL] 4850 done [URL="http://em99010pepe.googlepages.com/lresults_48K50K.txt"]lresults_48K50K.txt[/URL] 
Gary,
4648 is still in progress, less than 100 tests but I won't be here at home in the next 4 hours to post the results. I hope you don't mind. Carlos 
[quote=em99010pepe;138698]Gary,
4648 is still in progress, less than 100 tests but I won't be here at home in the next 4 hours to post the results. I hope you don't mind. Carlos[/quote] No problem. I had a power outage for 4 hours in the apartment I'm staying at last night so my sieving won't be done until 45 hours from now. Micha, I won't be back to the apt. for > 12 hours so I'll send you the sieved file on Sat. morning. Gary 
4648 done.
[url=http://em99010pepe.googlepages.com/lresults_46K48K.txt]lresults_46K48K.txt[/url] 
Sieving for n=50K100K is complete to P=60G. I sent the file to Micha for sieving P=60G100G. I will be sieving P=100G150G or whatever optimal depth is for breaking off n=50K75K.
It should take ~23 days on my sieve range unless optimal depth is much higher (unlikely). Gary 
I have received the file, and am sieving away.
Results also expected in around 3 days. 
Factors for 60100G sent to Gary (all 2578 of them)

[quote=michaf;138825]Factors for 60100G sent to Gary (all 2578 of them)[/quote]
Very good. Thanks for the help. My 100G150G range finished yesterday and 150G is past optimum sieve depth so I'll restart the drive for n=50K75K within the next few hours. I'll continue sieving n=75K100K. Optimum depth on it will likely be not much more than P=200G225G. I'm thinking once we reach n=100K, we can do the same thing for k=50M100M. For that range, I won't test n=25K35K. We'll just start right in on a team drive at n=25K after sieving is done. After completing k<100M for n=25K100K, we can decide as a group how we want to attack both sides of base 3 from there. I'm hoping that KEP will be done with k<500M on the Riesel side within the next month or so and we can attack that instead. I'll follow up with him and see where he is at. I originally started the Sierp attack because it had a lower conjecture at the time. Subsequent programming and testing by others showed that the Riesel side has a lower conjecture. Therefore, maybe it makes more sense to attack the Riesel side once we complete the Sierp side to k<100M and n=100K. Gary 
The drive has now restarted for n=50K75K. Files sieved to P=150G are now posted.
I will be sieving n=75K100K further. Gary 
Taking 5062 (12 files)..lol

11785058 50252
46511144 56138 20856328 56338 34960988 56350 
Taking 62k63k

48886226 51212
3938414 56779 10224166 59777 
I advise all to share the primes found so that we all can take them out from our current files reducing the testing time. Thanks.
michaf, you can take the 7 I found so far from your range. It will eliminate 147 candidates, 5880 seconds of work taken using a 2.96GHz machine. 
[quote=em99010pepe;138889]I advise all to share the primes found so that we all can take them out from our current files reducing the testing time. Thanks.
michaf, you can take the 7 I found so far from your range. It will eliminate 147 candidates, 5880 seconds of work taken using a 2.96GHz machine.[/quote] Had already done so for the first 4... But thanks for warning anyway 
6859514 51502
40316644 51786 24925372 51893 14994106 57376 
I have removed the 11 k's with primes found from the remaining posted files.

5053 complete.
28964426 52608 [url=http://em99010pepe.googlepages.com/lresults_50K53K.txt]lresults_50K53K.txt[/url] 
Please stop finding primes until I'm done now :) It's starting to disencourage ;)
I'm at 75% of my range and still have found not a single prime... Does anyone know the expected number of primes in the say 60k / 70k region? 
5356 complete
[url=http://em99010pepe.googlepages.com/lresults_53K56K.txt]lresults_53K56K.txt[/url] 
[quote=michaf;138981]Please stop finding primes until I'm done now :) It's starting to disencourage ;)
I'm at 75% of my range and still have found not a single prime... Does anyone know the expected number of primes in the say 60k / 70k region?[/quote] The next primes will credit you. 
[quote=michaf;138981]Please stop finding primes until I'm done now :) It's starting to disencourage ;)
I'm at 75% of my range and still have found not a single prime... Does anyone know the expected number of primes in the say 60k / 70k region?[/quote] In your n=1K range, there are approximately 2140 canditates for k's that didn't currently have a prime before Carlos's most recent single prime. The chance of a prime on a sieve to P=150G for this base and nrange are 1 in ~1500. Therefore, you should expect, on average, 1.4 primes in your range. At the beginning of the range, you had a 76% chance of finding a prime. So it's not particularly unusual that you wouldn't find a prime. Here is what is truly remarkable: Carlos's n=53K56K range contained NO primes for MORE k's! If it were for the same # of k's, he would expect 4.3 primes with a 98.6% chance of finding at least one prime. But it was actually higher for both stats since he had more k's than the calculations that I am using. Primes are very strange! :smile: Gary 
Taking 63K64K, will start on it when the NPLB rally is over. :smile:

[quote=michaf;138881]Taking 62k63k[/quote]
Range done, no primes taking 6465k 
5659 done.
[url=http://em99010pepe.googlepages.com/lresults_56K59K.txt]lresults_56K59K.txt[/url] 
[quote=em99010pepe;138955]5053 complete.
28964426 52608 [URL="http://em99010pepe.googlepages.com/lresults_50K53K.txt"]lresults_50K53K.txt[/URL][/quote] [quote=Anonymous;139012]Taking 63K64K, will start on it when the NPLB rally is over. :smile:[/quote] [quote=michaf;139017]Range done, no primes taking 6465k[/quote] The only k that has a reported prime that I haven't removed from the files yet is the last one found by Carlos...k=28964426. You can feel free to remove it from your files if you want. Gary 
[quote=gd_barnes;139026]The only k that has a reported prime that I haven't removed from the files yet is the last one found by Carlos...k=28964426. You can feel free to remove it from your files if you want.
Gary[/quote] Okay, I removed it from my file. Since I haven't started the file yet, it was actually quite easy to remove the k, since I didn't have to worry about adjusting the current line in llr.ini as I normally would have. :smile: 
5962 done.
[url=http://em99010pepe.googlepages.com/lresults_59K62K.txt]lresults_59K62K.txt[/url] 
My 'first':
42216418 64227 
Got myself a nice bedtimestory:
11242904 64614 
All k's with primes have been removed from all posted files.

Range 6465k complete, no more primes then the two already reported.
Taking 6566k 
[quote=michaf;139099]
Taking 6566k[/quote] Range done, one yet unreported prime: 9483244 65267 
1 Attachment(s)
63K64K done, no primes. Results attached. :smile:

Reserving 66k67k jaat
This might take more time than usual. I'll check in every few days. 
Taking 6768k

[quote=michaf;139682]Taking 6768k[/quote]
Range done, no primes, taking 68k69k 
[quote=michaf;139823]
taking 68k69k[/quote] Range done, no primes, taking 69k70k 
We've gone a little dormant on primes on this drive. Ergh! :smile:
Interestingly the optimum sieve depth for n=75K100K appears to be the same as for n=50K75K. That's because we've found so many k's with primes and the file is only half the size (before removing k's) of the prior n=50K100K file that was being sieved. Regardless of that, I'm going ahead and sieving it up to P=175G (from P=150G) and it will be done in a few hours. It just doesn't seem right not to sieve it further. (lol) By Friday, I'll add some more files up to n=80K. After we get a little further here and I get my main sieving laptop back from the repair shop (hopefully within 12 weeks), I'll start sieving k=50M100M for n=25K100K. Once we hit n=100K on this k<50M effort, I'll start another minidrive (or continue this one) to LLR k=50M100M for n=25K100K. If anyone is interested in sieving k=50M100M for n=25K100K, feel free. If needed, I can assist you in getting started. Also, if anyone wants to search k<50M for n>100K, let me know. Perhaps we can coordinate sieving several or all k's in the range for n=100K200K (or 300K or 400K). For the time being, I won't make it a team effort since we'd like to get more k's searched to n=100K but however I/we can assist people in taking individual k's higher, we will do so. Gary 
[quote=michaf;140092]
taking 69k70k[/quote] Range done, once again no primes... Taking 7071k, expecting three primes to make up for the gap... 
[quote=michaf;140448]
Taking 7071k, expecting three primes to make up for the gap...[/quote] Range done, once again no primes... Taking 7172k, and now I need 4 primes to make up for the gap... 
'Whoopie' :)
Got one at last :) Finished previous range, with one prime to boot: 29348458*3^71822+1 Reserving 7273k 
[quote=jaat;139422]Reserving 66k67k jaat
This might take more time than usual. I'll check in every few days.[/quote] Jaat, Can you give us a status on your range? Any prime found in this range can potentially eliminate quite a bit of testing at higher nranges. Thanks, Gary 
Gary,
Firstly I should apologize for my uncompleted NPLB reservation. It was again a res lack. I guess you already done it? For now, I can guarantee a Q6600 in 24/7 mode for about two months from now. May I take 4 files(73K77K)? I can crunch them in less than 48 hours. It that good performance? Thanks, nuggetprime 
Very lucky start:
29450654*3^76010+1 is prime!:banana: one less to test! happy hunting, nuggetprime 
[quote=michaf;141006]
Reserving 7273k[/quote] Range done, no prime 
five more primes:
9240646 74356 42497116 75136 26393956 75239 25207316 76109 39834376 76224 nuggetprime 
hmm... I got the unlucky streak I guess... :)
way to go nuggetprime! 
[quote=nuggetprime;142703]Gary,
Firstly I should apologize for my uncompleted NPLB reservation. It was again a res lack. I guess you already done it? For now, I can guarantee a Q6600 in 24/7 mode for about two months from now. May I take 4 files(73K77K)? I can crunch them in less than 48 hours. It that good performance? Thanks, nuggetprime[/quote] Thanks nugget. Sorry I've been putting out fires on my other project and missed things here. Nice finds! The n=4K range is fine. People can take as many as they want as they can complete in ~2 weeks. I'll post some more files shortly. I'm also going to repost 66K67K to search. Jaat has not responded on his status in several weeks. If you reserve some more, please make 66K67K the priority. Thanks! Gary 
[quote=nuggetprime;142896]five more primes:
9240646 74356 42497116 75136 26393956 75239 25207316 76109 39834376 76224 nuggetprime[/quote] Nugget, Were you complete with the n=73K77K range? I'm curious because that was fast processing to find all those primes! If so, please post results here or email them to me at gbarnes017 at gmail dot com. Thanks, Gary 
Range complete with one more prime:
46490116 74892 Residues will be sent in next five minutes (I didn't bother to remove k's with primes). I'm sorry, I'll not take another range here, but reserve a big chunk at NPLB 4th. nuggetprime 
[quote=nuggetprime;143049]Range complete with one more prime:
46490116 74892 Residues will be sent in next five minutes (I didn't bother to remove k's with primes). I'm sorry, I'll not take another range here, but reserve a big chunk at NPLB 4th. nuggetprime[/quote] Thanks nugget. I've now removed k's with primes from all files for n>77K. Will you need manual files to reserve at NPLB? If you have all connected machines, running LLRnet on our port 7500 is probably the best place. If you need the manual files or need more info. on the LLRnet servers, let me know. Thanks, Gary 
I won't use llrnet since my machine isn't connected to the internet overnight. I've posted a manual reservation in the appropirate NPLB thread.
Thanks, nuggetprime 
[quote=nuggetprime;143054]I won't use llrnet since my machine isn't connected to the internet overnight. I've posted a manual reservation in the appropirate NPLB thread.
Thanks, nuggetprime[/quote] PM sent with specifics of the reservation. 
Gary,
I also have a P4 running 6/6. This one could do 6667. Thanks, nuggetprime 
All times are UTC. The time now is 20:28. 
Powered by vBulletin® Version 3.8.11
Copyright ©2000  2021, Jelsoft Enterprises Ltd.