Team drive #10 k=1400-2000 n=500K-1M

[mdettweiler]

Originally Posted by gd_barnes

HUH? No!! Why would you think that I was all of a sudden asking about he DB prime list? I've never seen an issue with that. I asked about how often the prime list that you created at http://www.noprimeleftbehind.net/llrnet/primes_8000.txt is updated. See my original link.

Dave, no need to respond to Max's question.

That one should be updated every 15 minutes with the rest of the status page. Looking right now at the llrnet-status-pagegen.pl code (which generates that page and handles the primes_xxxx.txt files), I confirm that it does indeed append primes to the respective log files immediately after counting up the totals for how many results each user has submitted since the start of the day.

I'm not sure how anything could end up temporarily missing from that log, then show up later; the script runs every 15 minutes (more precisely, at :01, :15, :30, and :45 after the hour) and at that time adds any new primes to the log. Any further script runs that day will see that the prime is already present in the log and not add it again. The only possibility I can think of is that a prime was reported in the forum before the 15-minute page update caught it, that is, you spotted the prime directly in one of your clients' logs rather than seeing it first in the notification email.

[gd_barnes]

Originally Posted by mdettweiler

That one should be updated every 15 minutes with the rest of the status page. Looking right now at the llrnet-status-pagegen.pl code (which generates that page and handles the primes_xxxx.txt files), I confirm that it does indeed append primes to the respective log files immediately after counting up the totals for how many results each user has submitted since the start of the day.

I'm not sure how anything could end up temporarily missing from that log, then show up later; the script runs every 15 minutes (more precisely, at :01, :15, :30, and :45 after the hour) and at that time adds any new primes to the log. Any further script runs that day will see that the prime is already present in the log and not add it again. The only possibility I can think of is that a prime was reported in the forum before the 15-minute page update caught it, that is, you spotted the prime directly in one of your clients' logs rather than seeing it first in the notification email.

The 2 primes were hours old. I should have cut-and-pasted it here along with the time that I got the Email for them. Oh well, all appears well. If it happens again, at least we'll have a history on it.

[gd_barnes]

We have an excellent offer from Ian. He has agreed to put up to half of his cores on this drive in exchange for an exclusive reservation for him up to n=1M. This will help NPLB tremendously. What we will do is finish up port 8000 through n=750K and he will take it from there. It will then become a private drive for him similar to Peter Benson's k=1000-1400 effort at RPS.

In the next couple of days, I'll move all my cores here to get the drive finished up to n=750K.

[gd_barnes]

Releasing n=700K-701K reserved and incompleted by Nuggetprime back in March. If anyone wants this range, please let us know and we'll send you the file. All that we would ask is that it be completed within about 2 weeks since the 5000th place prime is rapidly approaching that range.

At its current rate, port 8000 will dry out in about a week. If n=700K-701K is not reserved by then, I'll load it in there and we can all finish it up.

[gd_barnes]

Reserving n=700K-701K for port 8000. This will be loaded in after the current n=740K-750K range, which will finish up by early Tuesday.

I will load n=700K-701K later today. With the current load of cores on port 8000, it should take about 2 days to complete.

[MyDogBuster]

Real unusual find within minutes of each other.

1775*2^982466-1
1775*2^982446-1

Same k, 20 apart on the n. Amazing for such a high n.

[Thomas11]

Originally Posted by MyDogBuster

Real unusual find within minutes of each other.

1775*2^982466-1
1775*2^982446-1

Same k, 20 apart on the n. Amazing for such a high n.

That's indeed a pretty nice coincidence! Good work!