422K-423K complete, no primes. lresults attached. :smile:

[quote=em99010pepe;130282]Which k's between 300<k<400 are we looking for some primes?

301, 305, 307, 309, 311, 313, 315, etc...[/quote]

First answer:

1. For n=260K-500K, all k's except 343, 359, 361, and 375 that are reserved by Curtis at RPS for his mini-drive.

2. For n=500K-600K, all 50 k's.


2nd answer:

Are you referring to which k's we will be looking for primes for n=600K-1M when I'm done sieving that range in a couple of days?

If so, that would be the k's that have a contiguous search range up to n=600K by others on Karsten's k=300-2000 page. They are:

k=301, 307, 311, 323, 331, 337, and 373.

These k's will be opened up for individual-k reservations after I'm done with that sieving. People will be able to take all of part of the n=600K-1M range for them at that time.

If there is little interest in individual-k reservations, we'll combine them in a team drive at some point.

Edit: The k's that we are not searching for n<500K are also shown in [URL="http://www.mersenneforum.org/showthread.php?t=9995"]this thread[/URL].


Gary

You can reserve 301 for me. Thanks.

[quote=em99010pepe;130307]You can reserve 301 for me. Thanks.[/quote]

OK, will do.

Possible correction on scoring...
 

Karsten,

There might be a correction in scoring as follows:

301*2^314825-1 found by Beyond is actually a confirmed prime. It was incorrectly shown as a new prime in post 1 of this thread because I never listed it as a previously found prime due to the fact that it is not on the top-5000 site. But I see that it was previously on the Primesearch site.

When looking for previously found primes, I only looked at top-5000 and its archives, which of course have many prime for n<333333. So there could be others like this, although I think there will be very few of them. There were so many on top-5000 that I didn't think there'd be any missing there that were previously found.

I'll make a note to check all of our primes for n<333333 to see if they were previously found on Primesearch later this week.

I have corrected post 1 of this thread.


Gary

Taking 463-464.

[quote=em99010pepe;130307]You can reserve 301 for me. Thanks.[/quote]

With sieving now done and several machines freed up, I will reserve k=323 for n=600K-1M.

I'll set up a separate thread for the 'effort' (not a drive) here shortly.


Gary

406-408
410-412
414-416
418-420

done

I noticed that in my 400-402 range it had some trouble writing to the lresults.txt shortly after I found a prime (I think a bug in AES's prime-checkin' program). Here's the log file of those.

[quote=Mini-Geek;130630]I noticed that in my 400-402 range it had some trouble writing to the lresults.txt shortly after I found a prime (I think a bug in AES's prime-checkin' program). Here's the log file of those.[/quote]
Ah, that's it--a file locking contention. AES's program is trying to access the lresults file, and LLR finishes a candidate at the same time, but AES's program has a lock on the file, so thus LLR can't get to it. LLR then puts it in the lprime.log file so that the result isn't lost. :smile:

[quote=Mini-Geek;130630]I noticed that in my 400-402 range it had some trouble writing to the lresults.txt shortly after I found a prime (I think a bug in AES's prime-checkin' program). Here's the log file of those.[/quote]


Thanks for forwarding those. I just merged them in with your original results file. The total line count of 3482 now matches the original sieved file.


Gary