PRPnet 2nd drive-51 bases with <= 5 k's to n=250K

[mdettweiler]

Very nice! We've had a few people slowly, but steadily plugging away on this server for a number of months now without a prime--it's definitely time for one! (And a proof no less--superb!)

[gd_barnes]

Excellent! Great find Mathew.

It's about time for this server!

[MyDogBuster]

http://primes.utm.edu/primes/page.php?id=104194

948*112^173968-1 is prime

R112 is now a 2ker

Talk about luck, I have only 1 core working on that port.

[gd_barnes]

Nice one Ian.

[MyDogBuster]

http://primes.utm.edu/primes/page.php?id=105413

86*123^176510-1 is prime

R123 is now a 1ker

And my luck with this 1 core continues

[gd_barnes]

Another nice one. Way to go Ian!

[Siemelink]

Originally Posted by MyDogBuster

http://primes.utm.edu/primes/page.php?id=105413

86*123^176510-1 is prime

R123 is now a 1ker

And my luck with this 1 core continues

I also found this prime in my queue. I take it we're doing double checks?

Willem.

[gd_barnes]

Originally Posted by Siemelink

I also found this prime in my queue. I take it we're doing double checks?

Willem.

No. That's odd. Mark or Max, can you answer why the same test may have been handed out twice?

Willem, did you test the pair, return it to the server, and the server rejected or accepted it? There's no indication on the port 1400 page that it was tested more than once. It only shows that Ian found the prime. I'm not in a position to check the server logs so I don't know the specifics.

[Siemelink]

Originally Posted by gd_barnes

No. That's odd. Mark or Max, can you answer why the same test may have been handed out twice?

Willem, did you test the pair, return it to the server, and the server rejected or accepted it? There's no indication on the port 1400 page that it was tested more than once. It only shows that Ian found the prime. I'm not in a position to check the server logs so I don't know the specifics.

Ah, it wasn't handed it yet I think. I have the entry in pfgw.log on the fourth of march. Currently the client is at:

Primality testing 86*123^176510-1 [N+1, Brillhart-Lehmer-Selfridge]
Running N+1 test using discriminant 3, base 1+sqrt(3)
N+1: 86*123^176510-1 402500/1225431 mro=0

Oh! My PC is not on 24x7, and when I shut it down the progress is lost. I just killed the process and the restart is back at 1/1225431.
Is this normal or did I screw up something in my installation?

Willem.

[rogue]

Originally Posted by Siemelink

Ah, it wasn't handed it yet I think. I have the entry in pfgw.log on the fourth of march. Currently the client is at:

Primality testing 86*123^176510-1 [N+1, Brillhart-Lehmer-Selfridge]
Running N+1 test using discriminant 3, base 1+sqrt(3)
N+1: 86*123^176510-1 402500/1225431 mro=0

Oh! My PC is not on 24x7, and when I shut it down the progress is lost. I just killed the process and the restart is back at 1/1225431.
Is this normal or did I screw up something in my installation?

Unfortunately that is a caveat of pfgw. It doesn't checkpoint primality tests. I really want to fix it so that it can checkpoint point them, but it isn't an easy change and I am working on other things that have a higher priority.

[gd_barnes]

OK, it sounds like you didn't get the test returned within 3 days so it was handed back out to someone else. I'm sorry that happened to you on a large prime.

Moral of the story: Make sure that your tests are returned to the server within 3 days. If unsure on machines that aren't connected all of the time, check our server status page for port 1400, which shows how long each test has before it expires.