Paydirt! :big grin:

[url=http://primes.utm.edu/primes/page.php?id=93406]121736*6^298935+1[/url] is prime!

This eliminates the third heaviest k remaining in the conjecture, which should help move things along a bit faster.

Reserving 314k-316k.
There seems to have been lots of primes here lately so I will try my luck for finally finding my first large prime in ages.

[QUOTE=henryzz;220522]Reserving 314k-316k.
There seems to have been lots of primes here lately so I will try my luck for finally finding my first large prime in ages.[/QUOTE]
Cool, glad to have some help around here! :smile: One thing to note: I made a boo-boo when updating the first post of this thread to reflect my recent prime and forgot to change it to say that k=121736 has NOT been removed from the sieve file yet. So if you didn't remove it yourself already, you'll want to do that before starting your range as it's rather high weight and should save you a significant amount of testing time.

Heck, I'll take 316k-320k - just to remember how it goes.

[SIZE=1](I am wrapping up all my old reservations, too. Unfortunately, there's nothing to write home about in them...)[/SIZE]

[quote=mdettweiler;220528]Cool, glad to have some help around here! :smile: One thing to note: I made a boo-boo when updating the first post of this thread to reflect my recent prime and forgot to change it to say that k=121736 has NOT been removed from the sieve file yet. So if you didn't remove it yourself already, you'll want to do that before starting your range as it's rather high weight and should save you a significant amount of testing time.[/quote]
I had guessed that:smile:

I'll extend to 316k-322k. Almost done.

316-322K
 

316-322K is done. 0 primes.

292K-314K done, 1 prime previously reported.

Reserving 322K-324K.

314k-316k Complete. Prpnet results attached.
Would you mind if I took k=97131 from 324k-400k? It might take 3 weeks not the recommended 2 weeks as I am away for a week in a week's time(anyone know the correct way to type week's time? It's an expression I hear but haven't seen typed.). Especially as I tend to get distracted with small efforts during the holidays.

[quote=henryzz;221628]314k-316k Complete. Prpnet results attached.
Would you mind if I took k=97131 from 324k-400k? It might take 3 weeks not the recommended 2 weeks as I am away for a week in a week's time(anyone know the correct way to type week's time? It's an expression I hear but haven't seen typed.). Especially as I tend to get distracted with small efforts during the holidays.[/quote]

I'd prefer that we just stick with what we're doing right now. It's much easier to administer. Otherwise I'm stuck removing that k from the file for others and having to specify the k's already searched in the various ranges. I'm more apt to make the exceptions for large-resourced folks who can knock out a very large range of n for 1-2 k's in short order with few distractions, You could reserve an n=1K or 2K range. Although I'd prefer that we stick with at least a 1K range, it would also be OK to do an n=500 range as long as we don't make a habit of that. Another alternative is to go to one of our many bases that are not team drives and that already have presieved files and just test 1k out of them.

You typed "in a week's time" correctly. In this context, you could also say "starting (or beginning) a week from now".

[quote=henryzz;221628]314k-316k Complete. Prpnet results attached.
Would you mind if I took k=97131 from 324k-400k? It might take 3 weeks not the recommended 2 weeks as I am away for a week in a week's time(anyone know the correct way to type week's time? It's an expression I hear but haven't seen typed.). Especially as I tend to get distracted with small efforts during the holidays.[/quote]
Thanks for the results, I'll get to work processing them shortly. As for k=97131, I know we did that for the Riesel base 6 drive, and that worked out OK, but here due to the much larger number of k's I can forsee that degenerating into an administrative mess. Assuming Gary agrees with me on this one, I would suggest that we continue with everything together at least until 400K. At that point, since we'll have a natural dividing line between sieve files anyway, we can split off some k's from the drive by request as individual reservations like what we had for n<100K before.

Edit: ah, Gary beat me to the chase and said pretty much the same thing. :smile: