The Perils of k=285728

[em99010pepe]

Masser,

I think I'll reserve k=285728 until I find a prime...lol...just like I did on the Riesel reservation a few days ago. You can send me the file when you get back from your vacation because I still need to push here on a few k's from NPLB project.

Carlos

[masser]

Carlos,

File has been sent. Good luck - you are going to need it. That sequence is incredibly sparse. Let me know when you run out of patience with the long tests.

best regards,
masser

[em99010pepe]

masser,

Thanks. I still have 200 tests (~ 2 days) to complete from the llrnet server but then I'll start the attack on k=285728. Don't worry about the long tests...

Carlos

[em99010pepe]

Those tests are huge, between 22-30 ms per it. I'll go back to the Riesel candidates you sent me a few days ago.

Carlos

[mdettweiler]

Originally Posted by em99010pepe

Those tests are huge, between 22-30 ms per it. I'll go back to the Riesel candidates you sent me a few days ago.

Carlos

Yeah, I think we should probably wait for more sieving before doing any tests that high. In fact, from cursory examinations, it seems that we're not quite yet at optimal depth for even the current range, though it is acceptable to continue doing PRP tests.

[em99010pepe]

Originally Posted by Anonymous

Yeah, I think we should probably wait for more sieving before doing any tests that high. In fact, from cursory examinations, it seems that we're not quite yet at optimal depth for even the current range, though it is acceptable to continue doing PRP tests.

I gave up at n=800k with more than 10 hours of processing on quad-core at 2.9 GHz, it was something like 60 % completed!!!

Carlos