S53 reached n=200K, releasing base. 3 primes found in that range, all reported.
Sieve file and results attached.

[QUOTE=MisterBitcoin;485874]S53 reached n=200K, releasing base. 3 primes found in that range, all reported.
Sieve file and results attached.[/QUOTE]

Two problems:

1. Your sieve file does not have k=62 in it for n=305K-1M. I have corrected it and posted it to the page. (The file was also named incorrectly as n=110K-1M even though it contained n=200K-1M.)

2. The original sieve file that came from Yoyo was missing k=1892. I cannot correct that without sieving it myself. I have made a note on the page that the file is missing k=1892.

Your mission should you choose to accept it:

1. Sieve k=1892 for n=100K-1M to whatever depth you want.

2. Test k=1892 for n=100K-200K to bring it up to where all of the other k's are at.

Assuming that you don't find a prime, even if the new k=1892 sieve is sieved less than all the others, you san send me your sieve file for n=200K-1M and I will still combine it with the rest of them into one bigger sieve file.

Unfortunately this means that S53 is still stuck at n=100K as a test depth for the time being.

(This is why those results files are important.) :smile:

[QUOTE=gd_barnes;485903]Two problems:

1. Your sieve file does not have k=62 in it for n=305K-1M. I have corrected it and posted it to the page. (The file was also named incorrectly as n=110K-1M even though it contained n=200K-1M.)

2. The original sieve file that came from Yoyo was missing k=1892. I cannot correct that without sieving it myself. I have made a note on the page that the file is missing k=1892.

Your mission should you choose to accept it:

1. Sieve k=1892 for n=100K-1M to whatever depth you want.

2. Test k=1892 for n=100K-200K to bring it up to where all of the other k's are at.

Assuming that you don't find a prime, even if the new k=1892 sieve is sieved less than all the others, you san send me your sieve file for n=200K-1M and I will still combine it with the rest of them into one bigger sieve file.

Unfortunately this means that S53 is still stuck at n=100K as a test depth for the time being.

(This is why those results files are important.) :smile:[/QUOTE]


I didn´t noticed that k=1892 was missing, I´ll check the yoyo@home results file maybe it was only missing in the sieve file.

If not I´ll do the sieve file for this k and will do test it up to n=200K. You can reserve this k. It wont take long.

[QUOTE=gd_barnes;485903]Two problems:

1. Your sieve file does not have k=62 in it for n=305K-1M. I have corrected it and posted it to the page. (The file was also named incorrectly as n=110K-1M even though it contained n=200K-1M.)

2. The original sieve file that came from Yoyo was missing k=1892. I cannot correct that without sieving it myself. I have made a note on the page that the file is missing k=1892.

Your mission should you choose to accept it:

1. Sieve k=1892 for n=100K-1M to whatever depth you want.

2. Test k=1892 for n=100K-200K to bring it up to where all of the other k's are at.

Assuming that you don't find a prime, even if the new k=1892 sieve is sieved less than all the others, you san send me your sieve file for n=200K-1M and I will still combine it with the rest of them into one bigger sieve file.

Unfortunately this means that S53 is still stuck at n=100K as a test depth for the time being.

(This is why those results files are important.) :smile:[/QUOTE]
If Mr.Bitcoin not found prime for 1892 ( that K is not in sieved K from Yoyo, and never was sieved) when tested to 200K send it to Yoyo. Then we can make same sieve depth as for rest of files ( and we can make small SR2 file and combine it with with K=62, to also got same sieve depth .

[QUOTE=pepi37;485907]If Mr.Bitcoin not found prime for 1892 ( that K is not in sieved K from Yoyo, and never was sieved) when tested to 200K send it to Yoyo. Then we can make same sieve depth as for rest of files ( and we can make small SR2 file and combine it with with K=62, to also got same sieve depth .[/QUOTE]

k=62 was already sieved. It was just missing in the file that MisterBitcoin sent me where he had removed the k's with primes. This happened because he did not test k=62 since it had already been tested to n>300K.

MisterBitcoin can sieve and test k=1892 however he wants. I have now reserved just that k for him to n=200K.

[QUOTE=gd_barnes;485945]k=62 was already sieved. It was just missing in the file that MisterBitcoin sent me where he had removed the k's with primes. This happened because he did not test k=62 since it had already been tested to n>300K.

MisterBitcoin can sieve and test k=1892 however he wants. I have now reserved just that k for him to n=200K.[/QUOTE]
I know that K062 has been sieved since I made that sieve. What I suggest is to resend both sequences ( if Mr Bitcoin not found prime in K= 1892) so all remain candidates has same sieve depth.

Progress update
 

K4 S53 at 1.26M

S48
 

S48 tested to 221K

1077*48^216501+1 is prime

Continuing to 250K

S53 k1892 is complete up to n=200K, no prime. Releasing this base.
Results and sieve file (p=500e12) attached.

Progress update
 

K4 S53 at 1.275M

43809*6[sup]681994[/sup]-1 is prime! 530700 digits.
31 k's remain on R36.
R36 is tested to 339k, sieved to 170T. Continuing.