Team drive #5: k=400-600 n=600K-1M

[gd_barnes]

This is team drive #5 for No Prime Left Behind. We will be searching all k=400-600 for n=600K-1M.

Karsten (kar_bon) has created a web page that shows details for the drive here. He maintains a site that has almost all known Riesel primes. There is a page for the range of 300<k<2000 here. The ranges searched and primes found from this project will be shown there.

An LLRnet server will be processing a large part of the range. To get the latest client for the server, see this thread. For general info. on setting up and running the server see this thread. The info. specific to the server that needs to be entered into your llr-clientconfig.txt file is:

server = "www.noprimeleftbehind.net"
port = 3000

We are also running a PRPnet server on this drive for those who prefer to use it. See this thread to get the latest PRPnet client, and this thread for information on our currently operating PRPnet servers. The info specific to this server that needs to be entered into your prpclient.ini file is:

server=G9000:100:1:noprimeleftbehind.net:9000

For manual reservations, we are posting one large file that people can cut individual reservations out of. This should give people more flexibility with their ranges. At the current n-range, tests take ~700 secs. each and there are ~3700 tests in each n=1000 range. Please reserve a range that will take no longer than ~2 weeks. IMPORTANT: Please reserve in multiples of no less than n=100 and begin your range with n=xxxx01 and end with n=xxxx00 to avoid missing or duplicating tests.

Please report all reservations/statuses/completions for this drive in this thread. Please report all primes found in Report all k<=1001 primes here thread. Please post all results files in this thread or send them to me at: gbarnes017 at gmail dot com.

Please report all top-5000 primes with a project ID of 'NPLB'.

New primes found from drive #5:

  Prime         found by
409*2^998261-1  gd_barnes
417*2^991349-1  Flatlander
503*2^989052-1  kar_bon
593*2^986574-1  Flatlander
573*2^986514-1  gd_barnes
471*2^984442-1  gd_barnes
477*2^978625-1  PCZ
437*2^978340-1  vaughan
537*2^965096-1  MyDogBuster
549*2^962377-1  gd_barnes
481*2^958909-1  vaughan
573*2^957476-1  PCZ
507*2^945498-1  Lennart
511*2^943223-1  MyDogBuster
455*2^937606-1  PCZ
437*2^937580-1  Beyond
475*2^931763-1  Lennart
507*2^926613-1  Lennart
597*2^925356-1  Lennart
423*2^924562-1  Sloth
511*2^924085-1  Sloth
511*2^921397-1  marco.bs
511*2^918351-1  Beyond
447*2^918282-1  MyDogBuster
571*2^912929-1  gd_barnes
445*2^910881-1  Sloth
563*2^901394-1  gd_barnes
445*2^901305-1  gd_barnes
425*2^900176-1  vaughan
561*2^900097-1  gd_barnes
469*2^892371-1  kar_bon
419*2^885792-1  gd_barnes
567*2^882408-1  vaughan
579*2^878796-1  Lennart
563*2^877856-1  Lennart
545*2^874596-1  Lennart
501*2^869927-1  gd_barnes
549*2^868860-1  vaughan
451*2^867501-1  gamer007
567*2^860497-1  gd_barnes
527*2^856404-1  Lennart
437*2^850256-1  henryzz
563*2^837448-1  vaughan
447*2^836966-1  vaughan
531*2^836707-1  Flatlander
483*2^834386-1  vaughan
423*2^833558-1  vaughan
545*2^829204-1  Flatlander
495*2^820086-1  Lennart
593*2^819630-1  kar_bon
577*2^813985-1  Sloth
577*2^811657-1  Sloth
475*2^811407-1  Lennart
435*2^810373-1  Sloth
531*2^807985-1  Flatlander
447*2^807089-1  gd_barnes
549*2^800603-1  gd_barnes
533*2^798022-1  gd_barnes
525*2^796560-1  Lennart
441*2^794409-1  gd_barnes
413*2^786824-1  vaughan
577*2^785121-1  Lennart
459*2^782168-1  Lennart
583*2^781515-1  Lennart
513*2^775455-1  kar_bon
407*2^769166-1  gd_barnes
545*2^764812-1  gd_barnes
411*2^762935-1  vaughan
597*2^760996-1  gd_barnes
521*2^759146-1  gd_barnes
441*2^749693-1  gd_barnes
411*2^746871-1  kar_bon
425*2^742506-1  Brucifer
451*2^740357-1  Brucifer
469*2^739729-1  gd_barnes
579*2^735459-1  gd_barnes
495*2^734277-1  gd_barnes
429*2^733315-1  gd_barnes
495*2^732566-1  gd_barnes
411*2^731153-1  gd_barnes
519*2^725471-1  gd_barnes
585*2^724530-1  gd_barnes
471*2^719122-1  gd_barnes
495*2^712468-1  vaughan
421*2^706219-1  vaughan
495*2^704130-1  vaughan
421*2^696385-1  gd_barnes
429*2^696361-1  vaughan 
435*2^695309-1  gd_barnes
497*2^688852-1  IronBits
429*2^686860-1  IronBits
555*2^686694-1  Ironbits
481*2^684665-1  IronBits
513*2^683547-1  vaughan
543*2^683355-1  IronBits
563*2^683292-1  IronBits
515*2^680196-1  IronBits
503*2^674214-1  IronBits
423*2^673728-1  IronBits
597*2^672336-1  IronBits
493*2^669151-1  SazanEyes
417*2^667878-1  vaughan
563*2^664568-1  gd_barnes
573*2^657807-1  mdettweiler
459*2^657272-1  gd_barnes
533*2^656000-1  gd_barnes
507*2^638296-1  gd_barnes
503*2^634134-1  gd_barnes
595*2^629757-1  gd_barnes
473*2^626184-1  gd_barnes
513*2^625011-1  glennpat
531*2^621426-1  gd_barnes
567*2^616877-1  MyDogBuster
455*2^615036-1  MyDogBuster
571*2^610371-1  henryzz
447*2^610250-1  Flatlander
423*2^609975-1  glennpat
543*2^609174-1  Kman1293
467*2^607118-1  gd_barnes
409*2^606805-1  gd_barnes
441*2^605849-1  Mini-Geek
587*2^605050-1  Mini-Geek
539*2^602564-1  gd_barnes

Primes confirmed from drive #5:

  Prime         found by
403*2^981831-1  PCZ
465*2^928115-1  MyDogBuster
405*2^902328-1  gd_barnes
465*2^825730-1  gd_barnes
489*2^780040-1  Lennart
405*2^765777-1  Beyond
465*2^722089-1  gd_barnes
465*2^716805-1  gd_barnes
405*2^705795-1  vaughan
483*2^703479-1  kar_bon
465*2^690044-1  vaughan
465*2^668701-1  IronBits
405*2^634608-1  gd_barnes

Status:

  n-range       tested by       Status        # primes
975.0K-1000.0K  LLRnet (G3000)  complete        8 (plus 1 confirmed)
965.0K-975.0K   PRPnet (G9000)  complete        1
955.0K-965.0K   LLRnet (G3000)  complete        3
945.0K-955.0K   PRPnet (G9000)  complete        1
935.0K-945.0K   LLRnet (G3000)  complete        3
920.0K-935.0K   PRPnet (G9000)  complete        6 (plus 1 confirmed)
912.0K-920.0K   LLRnet (G3000)  complete        3
910.0K-912.0K   PRPnet (G9000)  complete        1
892.0K-910.0K   LLRnet (G3000)  complete        5 (plus 1 confirmed)
890.0K-892.0K   PRPnet (G9000)  complete        0
880.0K-890.0K   LLRnet (G3000)  complete        2
870.0K-880.0K   PRPnet (G9000)  complete        3
860.0K-870.0K   LLRnet (G3000)  complete        4
850.0K-860.0K   PRPnet (G9000)  complete        2
827.0K-850.0K   LLRnet (G3000)  complete        6
820.0K-827.0K   PRPnet (G9000)  complete        1 (plus 1 confirmed)
815.0K-820.0K   LLRnet (G3000)  complete        1
810.0K-815.0K   PRPnet (G9000)  complete        4
798.0K-810.0K   LLRnet (G3000)  complete        4
796.0K-798.0K   PRPnet (G9000)  complete        1
786.0K-796.0K   LLRnet (G3000)  complete        2
780.0K-786.0K   PRPnet (G9000)  complete        3 (plus 1 confirmed)
748.0K-780.0K   LLRnet (G3000)  complete        7 (plus 1 confirmed)
740.0K-748.0K   PRPnet (G3000)  complete        3
700.0K-740.0K   LLRnet (IB4000) complete       12 (plus 4 confirmed)
638.0K-700.0K   LLRnet (IB4000) complete       21 (plus 2 confirmed)
637.0K-638.0K   PCZ             complete        0
635.0K-637.0K   MyDogBuster     complete        0
618.0K-635.0K   LLRnet (IB4000) complete        5 (plus 1 confirmed)
615.0K-618.0K   MyDogBuster     complete        2
606.2K-615.0K   LLRnet (IB4000) complete        6
606.0K-606.2K   mdettweiler     complete        0
605.0K-606.0K   Mini-Geek       complete        2
600.0K-605.0K   LLRnet (IB4000) complete        1

The drive is now complete! Thanks to everyone who contributed. :-)

Gary

[Mini-Geek]

Reserving 605-606. That would be about equivalent to a n=333 on Drive 1, right? (ignoring the slightly-increasing n-value and related FFT change...out of curiosity, just how many k's are in each drive now versus the full 400<k<1002 range?) I'll stay on IB400 until Drive 1 is finished and then move over to this manual reservation.

[gd_barnes]

Originally Posted by Mini-Geek

Reserving 605-606. That would be about equivalent to a n=333 on Drive 1, right? (ignoring the slightly-increasing n-value and related FFT change...out of curiosity, just how many k's are in each drive now versus the full 400<k<1002 range?) I'll stay on IB400 until Drive 1 is finished and then move over to this manual reservation.

OK, I'll send you the file; likely sometime on Monday when port 400 begins handing out n>600K.

Yes, an n=1000 range here would be like an n=333 range on the 1st drive. It will technically be slightly smaller because the new files are sieved to P=26T instead of P=5T...perhaps 3-5% smaller. I haven't checked them specifically just yet.

ALL odd k's are in the drives so you can almost take the k-range and divide by 2. But since we were including k=1001 in the 1st drive, that made for a total of 301 k's. So in the 5th drive here, there are 100 k's with 100 k's in the 6th drive and 101 k's in the 7th drive.

For the 8th and 9th drives for k=1005-2000, there will be 498 k's since we're excluding k=1001 included in the 7th drive and k=1003 that was previously searched by Max up to n=500K.


Gary

[henryzz]

are you going to do a double check of 1003 at some point Gary

[mdettweiler]

Originally Posted by henryzz

are you going to do a double check of 1003 at some point Gary

Well, the machines I did it on (primarily my dualcore, but a little bit from a P3 laptop) should be pretty stable--however, yes, I agree, we should still doublecheck it (albeit with less priority than the rest of 1005-2000 since it was already searched once through). Maybe we could do it as a special adjunct to the Doublecheck Drive #1?

In fact, users could even put unstable machines on a k=1003 doublecheck if they want, as a stability test of sorts--I have the original residuals, so thus there is essentially no margin of error in such a doublecheck. (This is different from the rest of the Doublecheck Drive #1, for which we do *not* have first-pass residuals.)

[gd_barnes]

Originally Posted by mdettweiler

Well, the machines I did it on (primarily my dualcore, but a little bit from a P3 laptop) should be pretty stable--however, yes, I agree, we should still doublecheck it (albeit with less priority than the rest of 1005-2000 since it was already searched once through). Maybe we could do it as a special adjunct to the Doublecheck Drive #1?

In fact, users could even put unstable machines on a k=1003 doublecheck if they want, as a stability test of sorts--I have the original residuals, so thus there is essentially no margin of error in such a doublecheck. (This is different from the rest of the Doublecheck Drive #1, for which we do *not* have first-pass residuals.)

IMHO, no, a double-check is not necessary as long as you have the results file available that you can send me. If so, then it becomes no different than NPLB searching new k's that had never been searched for the 1st drive or people searching the individual-k drive.

The key here is that it is a "known" regular NPLB searcher with stable machines that has the results file available. Had it been anyone outside of NPLB, I would have suggested that we include it in the sieving range to begin with and hence the drive.

That's only my opinion. If you'd like to add it on the end of the double-check drive, it's not a big deal one way or another.

Gary

[mdettweiler]

Originally Posted by gd_barnes

IMHO, no, a double-check is not necessary as long as you have the results file available that you can send me. If so, then it becomes no different than NPLB searching new k's that had never been searched for the 1st drive nor people searching the individual-k drive.

The key here is that it is a "known" regular NPLB searcher with stable machines that has the results file available. Had it been anyone outside of NPLB, I would have suggested that we include it in the sieving range to begin with and hence the drive.

That's only my opinion. If you'd like to add it on the end of the double-check drive, it's not a big deal one way or another.

Gary

Okay, yeah, I see what you mean about it being no different than any regular NPLB first-pass effort. Given that, I won't add it to the doublecheck drive; we'll just hit it a few years down the road when we eventually doublecheck k=1003-2000 for that range.

[gd_barnes]

Originally Posted by mdettweiler

Okay, yeah, I see what you mean about it being no different than any regular NPLB first-pass effort. Given that, I won't add it to the doublecheck drive; we'll just hit it a few years down the road when we eventually doublecheck k=1003-2000 for that range.

I said that assuming that you have the results files available to send me. Can you forward that when you get a chance?

[mdettweiler]

Originally Posted by gd_barnes

I said that assuming that you have the results files available to send me. Can you forward that when you get a chance?

Okay, sure. Actually, even better: you can see the post here where I reported completion of k=1003 to n=500K at RPS and attached the results. (That post contains the results for 100K-500K; I had previously posted the results for n=10K-100K a little earlier in that thread.)

[mdettweiler]

Hi all,

Now that all servers have passed n=600K, I'll post some manual files for the various n>600K drives, starting with this one. First of all, Mini-Geek, here's your file for 605K-606K:
NPLB5-605K-606K.txt

Secondly: I'll take 606K-606.2K for myself.

You guys should see some manual files showing up shortly...

Edit: Files now posted.

[Mini-Geek]

Originally Posted by mdettweiler

First of all, Mini-Geek, here's your file for 605K-606K:
NPLB5-605K-606K.txt

Got it. ETA for full range is 1/11, for the first two n=200's is 12/30. (I'll report it when I complete n=200x2, n=200x2, then n=100x2 finishing it. To make it simpler next time I'll reserve an even number of files.)