Sierp base 3 - mini-drive Ia
 

We have started a mini drive for Sierp base 3. The range is k<50M and n=35K-100K.

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 k-range.

This is a very low-intensity drive. The files are small and you should be able to complete files at the current n-range in 4-7 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 n-ranges. 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 Mini-Geek
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
86K-100K Flatlander complete 10
85K-86K henryzz complete 1
77K-85K em99010pepe complete 7
73K-77K nuggetprime complete 7
67K-73K michaf complete 1
66K-67K nuggetprime complete 0
64K-66K michaf complete 3
63K-64K mdettweiler complete 0
62K-63K michaf complete 0
42K-62K em99010pepe complete 35
39K-42K Lennart complete 8
38K-39K CedricVonck complete 1
37K-38K Mini-Geek complete 1
36K-37K henryzz complete 2
35K-36K 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 : 35K-36K

reserving : 36K-37K

Two primes found:

12562406 35092
38353046 35109

Do I have to remove these k's (12562406 & 38353046 )from imy nput file?

Taking 37K-38K. Removing the two k's that Cedric found primes for.
This is mainly to balance the amount of work on my NPLB 530.0-530.6 range between my cores. For some reason, 530.3-530.6 has way more pairs to test that 530.0-530.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=Mini-Geek;138448]Taking 37K-38K. Removing the two k's that Cedric found primes for.
This is mainly to balance the amount of work on my NPLB 530.0-530.6 range between my cores. For some reason, 530.3-530.6 has way more pairs to test that 530.0-530.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.ini--otherwise, 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 n-range 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 LLR-formatted 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=Mini-Geek;138470]Edit: Is there any existing tool to more easily remove a k from an LLR-formatted 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.)