mersenneforum.org

mersenneforum.org (https://www.mersenneforum.org/index.php)
-   No Prime Left Behind (https://www.mersenneforum.org/forumdisplay.php?f=82)
-   -   Team drive #12 k=2000-3000 n=50K-425K (https://www.mersenneforum.org/showthread.php?t=12276)

gd_barnes 2009-08-14 00:38

Team drive #12 k=2000-3000 n=50K-425K
 
This is team drive #12 for NPLB.

We will be searching all k=2000-3000 for n=50K-425K. The drive will be processed by k-value and will be broken up into 3 n-ranges: n=50K-250K, 250K-350K, and 350K-425K.

Karsten has created web pages which show details for the ranges [URL="http://www.rieselprime.de/NPLB/Drives/NPLB_Drive12A.htm"]n=50K-250K[/URL], [URL="http://www.rieselprime.de/NPLB/Drives/NPLB_Drive12B.htm"]n=250K-350K[/URL] and [URL="http://www.rieselprime.de/NPLB/Drives/NPLB_Drive12C.htm"]n=350K-425K[/URL].

An LLRnet server will be processing a large part of the range.
To get the latest client for the server, see [URL="http://www.mersenneforum.org/showthread.php?t=13165"]LLRnet supports LLR V3.8[/URL].
For general info. on setting up and running the server see [URL="http://www.mersenneforum.org/showthread.php?t=9959"]Automated LLR testing with LLRnet[/URL].
The info. specific to the server that needs to be entered into your llr-clientconfig.txt file is:

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

For this drive, there will be no top-5000 primes. For ranges run on the server, the admins will take care of showing all primes in this post.

Please post requests for manual files and we will send them to you. For manual ranges, please wait until you have completed your range and then post primes in THIS THREAD along with your completion status.

[FONT=Verdana][COLOR=black]All primes found from drive #12 by k and n-value:[/COLOR][/FONT]
[code]
Prime found by new (n) or confirmed (c)?
[URL="http://www.noprimeleftbehind.net/crus/prime2000-2100-50K-250K.txt"]primes k=2000-2100 n=50K-250K[/URL]
[URL="http://www.noprimeleftbehind.net/crus/prime2100-2200-50K-250K.txt"][COLOR=#800080]primes k=2100-2200 n=50K-250K[/COLOR][/URL]
[URL="http://www.noprimeleftbehind.net/crus/prime2200-2300-50K-250K.txt"][COLOR=#800080]primes k=2200-2300 n=50K-250K[/COLOR][/URL]
[URL="http://www.noprimeleftbehind.net/crus/prime2300-2400-50K-250K.txt"][COLOR=#800080]primes k=2300-2400 n=50K-250K[/COLOR][/URL]
[URL="http://www.noprimeleftbehind.net/crus/prime2400-2500-50K-250K.txt"][COLOR=#800080]primes k=2400-2500 n=50K-250K[/COLOR][/URL]
[URL="http://www.noprimeleftbehind.net/crus/prime2500-2600-50K-250K.txt"][COLOR=#800080]primes k=2500-2600 n=50K-250K[/COLOR][/URL]
[URL="http://www.noprimeleftbehind.net/crus/prime2600-2700-50K-250K.txt"][COLOR=#800080]primes k=2600-2700 n=50K-250K[/COLOR][/URL]
[URL="http://www.noprimeleftbehind.net/crus/prime2700-2800-50K-250K.txt"][COLOR=#800080]primes k=2700-2800 n=50K-250K[/COLOR][/URL]
[URL="http://www.noprimeleftbehind.net/crus/prime2800-2900-50K-250K.txt"][COLOR=#800080]primes k=2800-2900 n=50K-250K[/COLOR][/URL]
[URL="http://www.noprimeleftbehind.net/crus/prime2900-3000-50K-250K.txt"][COLOR=#800080]primes k=2900-3000 n=50K-250K[/COLOR][/URL]
[URL="http://www.noprimeleftbehind.net/crus/prime2000-2200-250K-350K.txt"]primes k=2000-2200 n=250K-350K[/URL]
[URL="http://www.noprimeleftbehind.net/crus/prime2200-2400-250K-350K.txt"]primes k=2200-2400 n=250K-350K[/URL]
[URL="http://www.noprimeleftbehind.net/crus/prime2400-2600-250K-350K.txt"]primes k=2400-2600 n=250K-350K[/URL]
[URL="http://www.noprimeleftbehind.net/crus/prime2600-2800-250K-350K.txt"]primes k=2600-2800 n=250K-350K[/URL]
[URL="http://www.noprimeleftbehind.net/crus/prime2800-3000-250K-350K.txt"]primes k=2800-3000 n=250K-350K[/URL]
[URL="http://www.noprimeleftbehind.net/crus/prime2000-2200-350K-425K.txt"]primes k=2000-2200 n=350K-425K[/URL]
[URL="http://www.noprimeleftbehind.net/crus/prime2200-2400-350K-425K.txt"]primes k=2200-2400 n=350K-425K[/URL]
[URL="http://www.noprimeleftbehind.net/crus/prime2400-2600-350K-425K.txt"]primes k=2400-2600 n=350K-425K[/URL]
[/code][COLOR=black][FONT=Verdana]Status:[/FONT][/COLOR]
[code]
k-range n-range tested by Status # primes
2800-3000 350K-425K LLRnet (G7000) in progress
2600-2800 350K-425K LLRnet (G7000) in progress
2400-2600 350K-425K LLRnet (G7000) in progress 47 (plus 4 confirmed)
2200-2400 350K-425K LLRnet (G7000) in progress 41 (plus 9 confirmed)
2000-2200 350K-425K LLRnet (G7000) in progress 28 (plus 30 confirmed)
2800-3000 250K-350K LLRnet (G7000) in progress 70 (plus 10 confirmed)
2600-2800 250K-350K LLRnet (G7000) in progress 82 (plus 4 confirmed)
2477-2600 250K-350K LLRnet (G7000) in progress 66 (plus 4 confirmed)
2400-2475 250K-350K Sloth complete 41 (plus 1 confirmed)
2200-2400 250K-350K LLRnet (G7000) in progress 55 (plus 18 confirmed)
2000-2200 250K-350K LLRnet (G7000) in progress 58 (plus 33 confirmed)
2800-3000 50K-250K Brucifer complete 353 (plus 69 confirmed)
2600-2800 50K-250K Brucifer complete 473 (plus 2 confirmed)
2400-2600 50K-250K Brucifer complete 457 (plus 26 confirmed)
2200-2400 50K-250K LLRnet (G7000) complete 459 (plus 40 confirmed)
2000-2200 50K-250K LLRnet (G7000) complete 308 (plus 187 confirmed)
[/code]Time to fill in some huge ranges! :smile:

Gary

gd_barnes 2009-08-14 00:43

The drive has not started yet. Max is in the process of creating new port 7000 on my machine. After doing so, he will load the file in.

The 1st link in the 1st post will not work yet. Karsten for that, I just used your standard link naming convention. Let me know when you have created the page.


Gary

Mini-Geek 2009-08-14 01:36

What sort of k size chunk for the various n sizes would give a file that would take a few CPU days? Put another way: what would be a good size for a manual file for someone with small resources?

AMDave 2009-08-14 09:56

The stats site is ready and polling for those files.
Le'me-at-em :boxer:

mdettweiler 2009-08-14 15:31

LLRnet G7000 is officially online. I noticed that my status page still lists it as the 6-k minidrive instead of Drive #12; this is just a cosmetic error and I'll fix it later today. Meanwhile, gotta run. :smile:

kar_bon 2009-08-14 15:52

[QUOTE=mdettweiler;185536]LLRnet G7000 is officially online.[/QUOTE]

seems not!

the 'Last unprocessed k/n pair" is empty!

perhaps the header missing? or a blank line at end?

mdettweiler 2009-08-14 17:32

[quote=kar_bon;185541]seems not!

the 'Last unprocessed k/n pair" is empty!

perhaps the header missing? or a blank line at end?[/quote]
Ah, whoops, you're right, that's a blank line. I'll fix it (and the drive name error) momentarily.

Edit: Both problems fixed.

kar_bon 2009-08-14 17:43

there's still no communication with the server!

Edited by MyDog: No communications here either

gd_barnes 2009-08-14 18:38

[quote=Mini-Geek;185423]What sort of k size chunk for the various n sizes would give a file that would take a few CPU days? Put another way: what would be a good size for a manual file for someone with small resources?[/quote]

I don't know at this point. Maybe 2 k's but I'm just guessing. Each k is going to have a variable # of candidates. It's a 50K-250K range, similar to the double-check drive's 100K-260K range. You might use it as a guide.

mdettweiler 2009-08-14 18:42

[quote=kar_bon;185564]there's still no communication with the server!

Edited by MyDog: No communications here either[/quote]
Oh, poop! Every time I set up a server I always forget to set up the port forwarding at first. Hold on, let me do that. :redface:

Edit: Fixed.

MyDogBuster 2009-11-20 16:56

Might want to think about loading up gb7000. Brucifer is back with a vengeance. He's done 35K tests since the last copy off not quite half a day ago. 2200-2400 might keep him happy.

mdettweiler 2009-11-20 17:28

[quote=MyDogBuster;196503]Might want to think about loading up gb7000. Brucifer is back with a vengeance. He's done 35K tests since the last copy off not quite half a day ago. 2200-2400 might keep him happy.[/quote]
Oh, wow! That's some serious work being done on there. Okay, I'll load up k=2200-2400 in a few minutes.

Thanks Bruce for the much-needed boost! :smile:

Brucifer 2009-11-20 19:21

Twas time for a change again! LOL Hopefully the ISP issues are resolved and things are going to run okay. But the only way to tell is to just go for it. I've got some systems loading in 50 tests at a time per core. What is the time out on 7000??

gd_barnes 2009-11-20 21:53

Thanks for the big boost Bruce. I'm not sure what you mean by "time out on 7000". Perhaps Max can answer.

mdettweiler 2009-11-21 04:02

[quote=gd_barnes;196527]Thanks for the big boost Bruce. I'm not sure what you mean by "time out on 7000". Perhaps Max can answer.[/quote]
Ah, I think he's referring to the jobMaxTime. :smile: That's currently set to 1 day.

Brucifer 2009-11-21 06:24

According to the status report there's only like 62,xxx left in it, and I've gone through 8x,xxx today so far. I hope you are loading more into it. :-)

mdettweiler 2009-11-21 11:48

[quote=Brucifer;196555]According to the status report there's only like 62,xxx left in it, and I've gone through 8x,xxx today so far. I hope you are loading more into it. :-)[/quote]
Whoops, looks like the addition of more candidates somehow didn't go through. I'm not entirely sure why that happened, though I can think of a few reasons why. I'll try it again.

mdettweiler 2009-11-21 12:04

[quote=mdettweiler;196568]Whoops, looks like the addition of more candidates somehow didn't go through. I'm not entirely sure why that happened, though I can think of a few reasons why. I'll try it again.[/quote]
Much better, all set now. It seems Ubuntu 8.04 behaves a bit differently than 7.04 when you close a tab on a gnome-terminal window: it simply lets the contents within keep running, rather than immediately stopping them like 7.04 did. This means that the only way I can close the infinite loop which I use to automatically restart the LLRnet servers (which I need to do in order to add new candidates) is by closing out all the servers, killing the VNC session (i.e. "logging off"), then starting it again, and then finally restarting the servers.

Hey, at least I only have to add candidates to an LLRnet server once in a while. Nonetheless, this makes me very glad we're transitioning to PRPnet in the near future! :smile:

Brucifer 2009-11-21 16:24

[QUOTE=mdettweiler;196570]Hey, at least I only have to add candidates to an LLRnet server once in a while. Nonetheless, this makes me very glad we're transitioning to PRPnet in the near future! :smile:[/QUOTE]

Tell me more.................... where, what, when, yada yada yada

mdettweiler 2009-11-21 21:40

[quote=Brucifer;196582]Tell me more.................... where, what, when, yada yada yada[/quote]
More news on that will be forthcoming soon. It looks like we've finally got a version of PRPnet that is completely stable all around, so we'll begin our general transition in the very near future.

Brucifer 2009-11-27 03:35

gonna need some more pairs loaded in or it won't make it through the weekend.

mdettweiler 2009-11-27 04:48

[quote=Brucifer;197113]gonna need some more pairs loaded in or it won't make it through the weekend.[/quote]
Okay, I'll load up k=2400-2600 tonight.

Brucifer 2009-11-27 16:41

Thanks Max! :-)

gd_barnes 2009-12-02 02:57

I have changed the 1st post to reflect the fact that we will be changing this drive to a PRPnet server. I also removed the k=2400-2600 range from the reservation range since it had problems in the LLRnet server.

gd_barnes 2009-12-03 05:02

[quote=gd_barnes;197532]I have changed the 1st post to reflect the fact that we will be changing this drive to a PRPnet server. I also removed the k=2400-2600 range from the reservation range since it had problems in the LLRnet server.[/quote]

The drive has restarted with new PRPnet server port 7000. The 1st post has been changed accordingly.

Brucifer 2009-12-08 20:45

I like to reserve the next range here, I'm assuming it's k=2600-2800??? Could you send me the file please, or if it isn't this range then the next one along the line??? Thank you. :smile:

gd_barnes 2009-12-08 21:17

Thanks for offering Bruce. Max, can you send Bruce k=2600-2800? If you can, please make sure there are no extra headers in there.

Bruce, it is now our plan to go back to LLRnet for this drive after k=2400-2600 is done. We'll make sure there are no extra headers in there but I don't blame you for wanting to run it on your own LLRnet server. It's going to be faster and less risky.


Gary

mdettweiler 2009-12-09 03:07

[quote=gd_barnes;198265]Thanks for offering Bruce. Max, can you send Bruce k=2600-2800? If you can, please make sure there are no extra headers in there.

Bruce, it is now our plan to go back to LLRnet for this drive after k=2400-2600 is done. We'll make sure there are no extra headers in there but I don't blame you for wanting to run it on your own LLRnet server. It's going to be faster and less risky.


Gary[/quote]
I've suggested a plan for how to proceed with this over in the "PRPnet servers for NPLB" thread [url=http://www.mersenneforum.org/showpost.php?p=198292&postcount=82]here[/url]. Bruce, let me know how this would work for you.

Brucifer 2009-12-09 06:20

[QUOTE=mdettweiler;198293]I've suggested a plan for how to proceed with this over in the "PRPnet servers for NPLB" thread [url=http://www.mersenneforum.org/showpost.php?p=198292&postcount=82]here[/url]. Bruce, let me know how this would work for you.[/QUOTE]

No problem, go ahead and email me the file, or give me an url to download it. :smile:

gd_barnes 2009-12-09 09:16

Bruce is officially reserving k=2400-3000 for n=50K-250K for this drive. I have sent him the files.

Thanks Bruce! :smile:

Brucifer 2009-12-20 00:52

k=2400-2600 for n=50K-250K Completed and results have been sent to Max. 2600-2800-50K-250K is now in work.

Brucifer 2009-12-28 18:36

2700-2800 50k-250k was completed and sent to Max. About a third of the way through 2800-2900.

Brucifer 2009-12-31 17:06

2800-2900-50k-250k completed and the results emailed to Max. 2900-3000-50k-250k is now in progress. Happy New Year. :smile: I was hoping that I could have it all done for New Year's, however I had a hardware malfunction (memory chip) that threw me off schedule while waiting for that to "magically appear." :smile:

Brucifer 2010-01-05 07:31

2900-3000-50k-250k is completed and the results have been emailed to Max.

kar_bon 2010-01-05 09:09

now it's my time to fill in the whole range upto n=250k, i think.

this could take a bit time so the next range n>250k should be started after that work is done, please!

mdettweiler 2010-01-29 05:39

I noticed that this thread hasn't had its status table updated for a while despite the fact all the ranges shown within as "in progress" are now long complete. Gary, I know I've processed all of Bruce's results and sent them to you; did you get the processed results from Karsten (I think he's doing those, right?) from the LLRnet portion of the drive (k<2400)?

I held off on marking Bruce's range as complete since Ian needs to mark down all the primes for it first. Ian, I think I recall you mentioned somewhere that you were waiting for Gary to move out the primes in the table to a linked file before you could add more; if you need to, you could just put them in a text file and attach it to a post here. Then Gary could upload them and put the links in the table.

gd_barnes 2010-01-29 12:20

[quote=mdettweiler;203644]I noticed that this thread hasn't had its status table updated for a while despite the fact all the ranges shown within as "in progress" are now long complete. Gary, I know I've processed all of Bruce's results and sent them to you; did you get the processed results from Karsten (I think he's doing those, right?) from the LLRnet portion of the drive (k<2400)?

I held off on marking Bruce's range as complete since Ian needs to mark down all the primes for it first. Ian, I think I recall you mentioned somewhere that you were waiting for Gary to move out the primes in the table to a linked file before you could add more; if you need to, you could just put them in a text file and attach it to a post here. Then Gary could upload them and put the links in the table.[/quote]

Oh, I moved out the primes long before Bruce commenced with the manual processing of the range. Ian and I just need to follow up on listing all of the primes. It's an arduous task that I just haven't had time for yet. What usually has been happening is that he would list as many as he could until it fills up, then I would move them off. But for tons of them that came in so fast like that, it makes more sense for me to just format them first into file links to begin with and maybe have him list the last k=100 or so of them. In other words, it makes no sense for him to list them, then have me copy them off, then him list them, etc.

So it's on my shoulders, not his, to put them in file links at this point. It's a bit of an effort because I have to check whether they are confirmed or new, just like Ian does when he lists them in the 1st post here. But what is a pain to get started on it this time around is that I need to wade through Bruce's primes to see which one's Lennart's already found. I think I'll show them both as finding them.

So as you can see, it's no easy task. Tell you what...Monday is my admin day when I'm out of town...good day to catch up on paperwork and stuff. I'll write it on my task list for Monday to spend an hour checking what is new/confirmed, if Bruce/Lennart both found the same prime, etc. and creating file links. In an hour, I'm thinking I can finish the most difficult part, which is doing k=2400-2600. Even though we already have primes well above that listed, Bruce started manually at k=2400 because of the server problems that we had so I'll likely need to show both of them finding quite a few primes. Another day I'll get to k=2600-3000, which should take less time for twice the size since it's a clean manual run. I guess that's why I've procrastinated it a little...I know k=2400-2600 is going to be a pain administratively.

Karsten, please hold off on listing in k=2400-3000 for n=50K-250K primes found in this effort on your pages until after next Monday. That way, I can tell if they were confirmed or found new.

Regardless, Max, if you have time, I'd like to see LLRnet port 7000 get loaded up with k=2000-2100 (or 2000-2200) for n=250K-350K any time and then let Bruce know about it. LLRnet works great for this range. We only goofed last time because of the extra header-in-the-file problem. You might give him your personal guarantee that we've closely inspected the file for any error that could cause problems and that my LLRnet port 6000 has been running great with ~60-70 cores total on it right now. Also mention that since the tests aren't so small, the load on the server will be much smaller. (n=250K takes ~25 times as long to test as n=50K)


Gary

kar_bon 2010-01-29 14:37

[QUOTE=gd_barnes;203682]Karsten, please hold off on listing in k=2400-3000 for n=50K-250K primes found in this effort on your pages until after next Monday. That way, I can tell if they were confirmed or found new.
[/QUOTE]

As you can see on rieselprime for Drive 12A, I'm at k=2177 with including primes in the 2000-4000 summary page so far.
It's indeed very time-consuming to check for confirmed primes but i found some problems so far:
There're some primes not listed yet in the summary although the test-range was higher. Here are the issues so far:

2055: done to n=400k (S.Tjung) but missed n=216369 -> max-n=250k
2085: done to n=400k (S.Tjung) but missed n=193924 -> max-n=250k
2171: done to n=1.0M (Beyond?) but missed n=101974 -> max-n=250k
2175: done to n=400k (S.Tjung) but missed n=183243,224093 -> max-n=250k

I've therefore set the test-range down to n=250k.

More work will be done slowly the next weeks!
Don't worry, Gary, you got enough time.

mdettweiler 2010-01-29 17:34

[quote=gd_barnes;203682]Oh, I moved out the primes long before Bruce commenced with the manual processing of the range. Ian and I just need to follow up on listing all of the primes. It's an arduous task that I just haven't had time for yet. What usually has been happening is that he would list as many as he could until it fills up, then I would move them off. But for tons of them that came in so fast like that, it makes more sense for me to just format them first into file links to begin with and maybe have him list the last k=100 or so of them. In other words, it makes no sense for him to list them, then have me copy them off, then him list them, etc.

So it's on my shoulders, not his, to put them in file links at this point. It's a bit of an effort because I have to check whether they are confirmed or new, just like Ian does when he lists them in the 1st post here. But what is a pain to get started on it this time around is that I need to wade through Bruce's primes to see which one's Lennart's already found. I think I'll show them both as finding them.

So as you can see, it's no easy task. Tell you what...Monday is my admin day when I'm out of town...good day to catch up on paperwork and stuff. I'll write it on my task list for Monday to spend an hour checking what is new/confirmed, if Bruce/Lennart both found the same prime, etc. and creating file links. In an hour, I'm thinking I can finish the most difficult part, which is doing k=2400-2600. Even though we already have primes well above that listed, Bruce started manually at k=2400 because of the server problems that we had so I'll likely need to show both of them finding quite a few primes. Another day I'll get to k=2600-3000, which should take less time for twice the size since it's a clean manual run. I guess that's why I've procrastinated it a little...I know k=2400-2600 is going to be a pain administratively.[/quote]
Well, what I had in mind was that possibly Ian could take the primes and put them into flat text files, which he would attach to a forum post and you could upload to the web. Then you could just plop the file links here. (We wouldn't even necessarily need to list the last k=100 or so of them...there's so many of them that I imagine even just the file links will fill up the code box somewhat.) This is, of course, assuming that Ian doesn't mind. :smile:

As for k=2400-2600: that might be a tad tricky. You see, the results files from the PRPnet portion of that never got copied off due to the database mess that needs to be cleaned up; they're still sitting in G7000's folder on humpford's desktop. I can send the file to you if you'd like.

[quote]Karsten, please hold off on listing in k=2400-3000 for n=50K-250K primes found in this effort on your pages until after next Monday. That way, I can tell if they were confirmed or found new.

Regardless, Max, if you have time, I'd like to see LLRnet port 7000 get loaded up with k=2000-2100 (or 2000-2200) for n=250K-350K any time and then let Bruce know about it. LLRnet works great for this range. We only goofed last time because of the extra header-in-the-file problem. You might give him your personal guarantee that we've closely inspected the file for any error that could cause problems and that my LLRnet port 6000 has been running great with ~60-70 cores total on it right now. Also mention that since the tests aren't so small, the load on the server will be much smaller. (n=250K takes ~25 times as long to test as n=50K)[/quote]
About that, I'm still waiting for the database to be cleaned out from the old mess. I'll have to send Dave an email about that today.

gd_barnes 2010-01-30 00:43

[quote=kar_bon;203695]As you can see on rieselprime for Drive 12A, I'm at k=2177 with including primes in the 2000-4000 summary page so far.
It's indeed very time-consuming to check for confirmed primes but i found some problems so far:
There're some primes not listed yet in the summary although the test-range was higher. Here are the issues so far:

2055: done to n=400k (S.Tjung) but missed n=216369 -> max-n=250k
2085: done to n=400k (S.Tjung) but missed n=193924 -> max-n=250k
2171: done to n=1.0M (Beyond?) but missed n=101974 -> max-n=250k
2175: done to n=400k (S.Tjung) but missed n=183243,224093 -> max-n=250k

I've therefore set the test-range down to n=250k.

More work will be done slowly the next weeks!
Don't worry, Gary, you got enough time.[/quote]


That's why NPLB includes ALL k's in our drives (unless reserved and we would "run over" existing reservations). Way to go all! We found primes missed by others! Even the non-top-5000 primes are important.

On the 5 or so k's excluded from the 11th drive, we'll (mainly me but also whomever else might want to help) will be double checking those ~5 k's for n=425K-600K close to the time that the 11th drive is nearing n=600K. I'm shooting for mid-year on it getting there. Late in 2008, such a double check netted a missing top-5000 prime! :smile:

k=2400-2600 is really messy so I'll work on sorting it out and getting a file link for it on Monday. It's high on my task list now.

Max, good idea on just doing file links instead of listing the last 100k or so in the post. That's a bit of a nuisance. Yeah, I/we will just do file links for all of the primes...well, at least for all n=50K-250K primes. The file links are small and use little posting space. With all n=50K-250K primes in links, we'll likely be able to show all or a large portion of n=250K-350K primes as line items in the post. That's kind of a personal preference on my part. :-)

Max, one more thing. All of Lennart's k=2400-2600 primes are already shown in the 1st post here. I'll just take the primes file that you already sent me from Bruce (or that he sent me?) and add those to it. For primes that they both found, I'll just show both their names as having found them, with whomever found them first listed first. In other words, you don't need to do anything for me to be able to do that. That's my Monday task. :-)


Gary

gd_barnes 2010-02-02 04:33

Unfortunately I won't be able to get all of the primes brought together today for k=2400-2600. What I'm running into is that Bruce's list of primes from his manual LLRnet run is missing at least a couple of primes from the original run that we did on a public PRPnet/LLRnet server. I don't know if that's because he missed them or we have extras in the original run. Also, of course the original run here is missing many primes vs. Bruce's list, even in the middle of the run due to problems with the public server. That's not a concern but Bruce not having primes found by the public server in his list is a problem.

Fortunately Bruce was kind enough to send me/Max the immense amount of results from the range so I should be able to isolate the problems more easily.

This will take several hours to get it all together, matched up, proper credit given, and check the new/confirmed status. I'm about 1/3rd of the way into it and realized that it will take much longer than I originally expected. I'll post more details about the above problem late Tuesday.

I'll work on it more on Tuesday but can't guarantee completion depending on issues that I run into. It is my hope to at least have all of the k=2400-2600 primes listed by the end of this week. After that, k=2600-3000 should go much more quickly.


Gary

gd_barnes 2010-02-02 05:05

There were 4 primes found by Lennart on the public server that were not found by Bruce in his manual LLRnet run that effectively was a double-check of a large part of the range. Triple-checking by me confirmed that Bruce's list is correct. Here are the culprits:

2457*2^239794-1 is not prime. LLR Res64: 55D32DAFD42FB9B4 Time : 198.913 sec.
2463*2^170838-1 is not prime. LLR Res64: EC031A0DB6C2DCF2 Time : 127.062 sec.
2481*2^185187-1 is not prime. LLR Res64: A64A60A7D5942FD4 Time : 119.079 sec.
2505*2^154470-1 is not prime. LLR Res64: 07BE4011A7E08FF5 Time : 89.002 sec.

In all 4 cases, these were close to actual primes that were found by both Bruce and Lennart. They are:
2457*2^239814-1 (n=20 difference from above "composite prime")
2463*2^170842-1 (n=4 difference)
2481*2^185218-1 (n=31 difference)
2505*2^154475-1 (n=5 difference)

That is exactly what happened to me on 2 occassions when I had a laptop with bad memory. It would find a "composite prime" very close to an actual prime. I'll send Lennart a PM referencing this post. I have now deleted the erroneous primes from the 1st post here.

That's a start on the cleanup of k=2400-2600 here...still much work to do on it later Tuesday.


Gary

Lennart 2010-02-02 05:33

[quote=gd_barnes;204278]There were 4 primes found by Lennart on the public server that were not found by Bruce in his manual LLRnet run that effectively was a double-check of a large part of the range. Triple-checking by me confirmed that Bruce's list is correct. Here are the culprits:

2457*2^239794-1 is not prime. LLR Res64: 55D32DAFD42FB9B4 Time : 198.913 sec.
2463*2^170838-1 is not prime. LLR Res64: EC031A0DB6C2DCF2 Time : 127.062 sec.
2481*2^185187-1 is not prime. LLR Res64: A64A60A7D5942FD4 Time : 119.079 sec.
2505*2^154470-1 is not prime. LLR Res64: 07BE4011A7E08FF5 Time : 89.002 sec.

In all 4 cases, these were close to actual primes that were found by both Bruce and Lennart. They are:
2457*2^239814-1 (n=20 difference from above "composite prime")
2463*2^170842-1 (n=4 difference)
2481*2^185218-1 (n=31 difference)
2505*2^154475-1 (n=5 difference)

That is exactly what happened to me on 2 occassions when I had a laptop with bad memory. It would fine a "composite prime" very close to an actual prime. I'll send Lennart a PM referencing this post. I have now deleted the erroneous primes from the 1st post here.

That's a start on the cleanup of k=2400-2600 here...still much work to do on it later Tuesday.


Gary[/quote]


I can't answer the question. I need to know the computer (ClirntID) from log to see that. If there is a problem it should show up in Boinc becuse all is DC there so that computer should have many invalid wu,


But can you give me the log entrys frp server there clientid is i can mayby narrow it down. :smile:


Lennart

gd_barnes 2010-02-02 05:39

[quote=Lennart;204280]I can't answer the question. I need to know the computer (ClirntID) from log to see that. If there is a problem it should show up in Boinc becuse all is DC there so that computer should have many invalid wu,


But can you give me the log entrys frp server there clientid is i can mayby narrow it down. :smile:


Lennart[/quote]

OK, I'll see what I can do. It may be Thursday or Friday after I get back from a business trip. It's not easy to access the servers remotely right now.

mdettweiler 2010-02-02 05:44

[quote=Lennart;204280]I can't answer the question. I need to know the computer (ClirntID) from log to see that. If there is a problem it should show up in Boinc becuse all is DC there so that computer should have many invalid wu,


But can you give me the log entrys frp server there clientid is i can mayby narrow it down. :smile:


Lennart[/quote]
Right now we're having some issues with the server machine, so I might have a hard time pulling files off of it. I do still have the PPRnet G7000 original results sitting around on the server, so I'll try to get a hold of them as soon as possible and try to spot which machine(s) produced the culprit results.

gd_barnes 2010-02-03 05:06

[quote=mdettweiler;204284]Right now we're having some issues with the server machine, so I might have a hard time pulling files off of it. I do still have the PPRnet G7000 original results sitting around on the server, so I'll try to get a hold of them as soon as possible and try to spot which machine(s) produced the culprit results.[/quote]

Max, after I get back very late Thursday and get the machine rebooted, can you put it on your list to send Lennart this info. sometime on Friday? Thanks.

Lennart, something quirky in our remote setup is keeping us from viewing files on the server machine and one other machine right now. Sorry for the delay.


Gary

gd_barnes 2010-02-03 05:18

After much effort, the listing of k=2400-2600 primes is complete. The counts of new and confirmed primes have been verified against the results files that Bruce sent and Karsten's rieselprime web page.

I'll do k=2600-3000 later Weds. It should be child's play compared to k=2400-2600.

Max, I've let this slide on a # of drives right now due to heavy admin duties on both of the projects right now but while we're at it here, can you please sent me "regular LLR" formatted results for k=2000-2400 here so that I can verify the prime counts for that range? Bruce (or you) have already sent me results for k=2600-3000. Generally I leave the 1st post status as "in progress" until I'm able to verify the results but made an exception here since it would look odd to have k=2400-2600 complete and k=2000-2400 as in progress.

On the other hand, it's possible that I could have missed an Email or two from way back so if you've already sent the k=2000-2400 results, just let me know the date that they were sent and I'll find them.


Thanks,
Gary

mdettweiler 2010-02-03 05:27

[quote=gd_barnes;204381]After much effort, the listing of k=2400-2600 primes is complete. The counts of new and confirmed primes have been verified against the results files that Bruce sent and Karsten's rieselprime web page.

I'll do k=2600-3000 later Weds. It should be child's play compared to k=2400-2600.

Max, I've let this slide on a # of drives right now due to heavy admin duties on both of the projects right now but while we're at it here, can you please sent me "regular LLR" formatted results for k=2000-2400 here so that I can verify the prime counts for that range? Bruce (or you) have already sent me results for k=2600-3000. Generally I leave the 1st post status as "in progress" until I'm able to verify the results but made an exception here since it would look odd to have k=2400-2600 complete and k=2000-2400 as in progress.

On the other hand, it's possible that I could have missed an Email or two from way back so if you've already sent the k=2000-2400 results, just let me know the date that they were sent and I'll find them.


Thanks,
Gary[/quote]
The results in LLRnet format should be in the same place as always; last I recall, Karsten was the one doing the processing of those results into LLR format and sending them to you. Karsten, do you have those handy by chance?

mdettweiler 2010-02-03 05:29

[quote=gd_barnes;204380]Max, after I get back very late Thursday and get the machine rebooted, can you put it on your list to send Lennart this info. sometime on Friday? Thanks.

Lennart, something quirky in our remote setup is keeping us from viewing files on the server machine and one other machine right now. Sorry for the delay.


Gary[/quote]
Okay. I may actually be able to copy off the file via the command line before you get the machine rebooted, but I'll be out of the house for much of tomorrow so I might not get to it then. (It's too late to do it tonight.) I'll do it as soon as I get the chance, though.

gd_barnes 2010-02-03 12:03

[quote=mdettweiler;204382]The results in LLRnet format should be in the same place as always; last I recall, Karsten was the one doing the processing of those results into LLR format and sending them to you. Karsten, do you have those handy by chance?[/quote]

Karsten sent me a PM with a link to them. Thanks for checking.

[quote=mdettweiler;204383]Okay. I may actually be able to copy off the file via the command line before you get the machine rebooted, but I'll be out of the house for much of tomorrow so I might not get to it then. (It's too late to do it tonight.) I'll do it as soon as I get the chance, though.[/quote]

I won't be rebooting it until very late Thursday night; more like early Friday morning. So you should have most of Weds. and Thurs. to take care of it if you have time.


Gary

mdettweiler 2010-02-03 15:12

[quote=gd_barnes;204412]I won't be rebooting it until very late Thursday night; more like early Friday morning. So you should have most of Weds. and Thurs. to take care of it if you have time.[/quote]
Okay, I've got the file now and have found the false primes in there. But...the news is not good. I found three distinct machines that produced these results:
[code][2009-12-06 05:00:10 GMT] 2457*2^239794-1 received by Email: sm5ymt@*******.** User: sm5ymt Client: 6 Program: llr Prover: llr Residue: PRIME
[2009-12-06 07:03:16 GMT] 2463*2^170838-1 received by Email: sm5ymt@*******.** User: sm5ymt Client: 96 Program: llr Prover: llr Residue: PRIME
[2009-12-07 17:12:46 GMT] 2481*2^185187-1 received by Email: sm5ymt@*******.** User: sm5ymt Client: 150 Program: llr Prover: llr Residue: PRIME
[2009-12-07 20:01:51 GMT] 2505*2^154470-1 received by Email: sm5ymt@*******.** User: sm5ymt Client: 96 Program: llr Prover: llr Residue: PRIME [/code]
On is from client "6", two from "96", and one from "150". The most reasonable conclusion would seem to be that all three are bad (or at least were at the time they produced these results--either that or Lennart's house got hit with a real whammy of cosmic rays around that time :wink:).

Edit: I just thought of something. Lennart, do you name your clients individually per core, or per machine? If those are all cores of the same machine, then that might explain why there appeared to be three problematic clients.

gd_barnes 2010-02-04 11:16

It's too clunky to work with the huge results files while out of town. My plan now is to work on the primes for k=2600-3000 sometime this upcoming weekend. I'm just glad to have the messy k=2400-2600 range done.

gd_barnes 2010-02-09 15:33

All primes for this drive have now been confirmed and entered in the 1st post for n=50K-250K.

As soon as we can confirm the database cleanup for the range, we can begin on n=250K-350K. Max, what is the status of that?

mdettweiler 2010-02-09 17:34

[quote=gd_barnes;205051]All primes for this drive have now been confirmed and entered in the 1st post for n=50K-250K.

As soon as we can confirm the database cleanup for the range, we can begin on n=250K-350K. Max, what is the status of that?[/quote]
Still not happened yet. I'll email Dave about it.

gd_barnes 2010-03-26 08:26

Max,

Now that the database has been cleaned up, can we go ahead and load k=2000-2200 for n=250K-350K into LLRnet port 7000?


Gary

mdettweiler 2010-03-26 16:03

[quote=gd_barnes;209567]Max,

Now that the database has been cleaned up, can we go ahead and load k=2000-2200 for n=250K-350K into LLRnet port 7000?


Gary[/quote]
Yes, there's nothing to prevent us from doing that now. I'll go ahead and do that later today.

mdettweiler 2010-03-27 01:23

[quote=mdettweiler;209615]Yes, there's nothing to prevent us from doing that now. I'll go ahead and do that later today.[/quote]
Okay, all loaded up and tested. Everything should be all set to go. :smile:

kar_bon 2010-03-27 01:37

[QUOTE=mdettweiler;209662]Okay, all loaded up and tested. Everything should be all set to go. :smile:[/QUOTE]

the primelist is not cleared and also contains the false primes!

mdettweiler 2010-03-27 02:32

[quote=kar_bon;209663]the primelist is not cleared and also contains the false primes![/quote]
Ah, whoops, missed that. It's fixed now.

kar_bon 2010-04-27 18:53

Just these days I'm almost done with the Drive#12-page and the k2000-3000-summary page at rieselprime.de.

I'm also checking the primelist-files from the first post and mine and found many errors and missing primes there!
I'll send Gary an updated list of files checked against the LLRnet- and manual-results.
The number of candidates all over differs, too! So more checking needed!

gd_barnes 2010-04-27 19:02

[quote=kar_bon;213351]Just these days I'm almost done with the Drive#12-page and the k2000-3000-summary page at rieselprime.de.

I'm also checking the primelist-files from the first post and mine and found many errors and missing primes there!
I'll send Gary an updated list of files checked against the LLRnet- and manual-results.
The number of candidates all over differs, too! So more checking needed![/quote]

Karsten,

I know I did a very detailed check of all primes and counts in the 1st post here for all k>2400 due to the problems that we had with PRPnet and the fact that Bruce took over with a personal LLRnet server. It was a very large effort that I remember took the better part of an entire afternoon. Those should all be correct. I thought I also closely checked k<2400 but am not so sure about that.

If you are finding errors in the 1st posting primes here, they should all be for k<2400 but of course I welcome the doublecheck of them for k>2400 also.

Maybe I'm responding incorrectly. I could not tell if your final para. meant you were finding errors on your pages or errors in the 1st posting here.


Gary

kar_bon 2010-04-27 19:47

All errors I've found are in the files from the first post!
I've only checked k=2000 - 2300 so far but will check all upto k=3000 then.

Here're some missing primes:
2089*2^152151-1 Brucifer n
2145*2^214257-1 kar_bon c
2147*2^73550-1 kar_bon n
2147*2^82130-1 kar_bon n
2147*2^82714-1 kar_bon n
2153*2^99144-1 Bruce n

There're also some typos, misordered ones, 'confirmed' and 'new' not correct.

When I'm ready with all of them, I'll send you all updated files from 1st post and some info.

gd_barnes 2010-04-28 07:25

[quote=kar_bon;213360]All errors I've found are in the files from the first post!
I've only checked k=2000 - 2300 so far but will check all upto k=3000 then.

Here're some missing primes:
2089*2^152151-1 Brucifer n
2145*2^214257-1 kar_bon c
2147*2^73550-1 kar_bon n
2147*2^82130-1 kar_bon n
2147*2^82714-1 kar_bon n
2153*2^99144-1 Bruce n

There're also some typos, misordered ones, 'confirmed' and 'new' not correct.

When I'm ready with all of them, I'll send you all updated files from 1st post and some info.[/quote]


Ah, those are from when Ian was updating them. I failed to doublecheck them. I get to harrass Ian now. lol

I'd be very surprised if you find any problems for k>2400. I pulled the primes right out of the results file for those and then visually compared them to your page as to whether they had already been found or not.

I think I might have checked k=2200-2400 but I can't remember for sure but I'm positive on k>2400.

...kind of annoyed with myself for not checking k=2000-2200. I'm glad you are checking it.


Gary

kar_bon 2010-04-28 07:35

[QUOTE=gd_barnes;213418]
...kind of annoyed with myself for not checking k=2000-2200. I'm glad you are checking it.
[/QUOTE]

No problem! Better doublechecked than no check!
I got a few seconds I've nothing to do now! :grin:

kar_bon 2010-07-05 11:18

The results/primes for the range n=50k-250k and k~=2450 - 2600 are still missing in the result database, see [url=http://www.noprimeleftbehind.net/stats/index.php?content=drive_progress]NPLB Drive Progress[/url].

mdettweiler 2010-07-05 18:26

[QUOTE=kar_bon;220625]The results/primes for the range n=50k-250k and k~=2450 - 2600 are still missing in the result database, see [url=http://www.noprimeleftbehind.net/stats/index.php?content=drive_progress]NPLB Drive Progress[/url].[/QUOTE]
The main thing holding that up at this point is that we need an import process that logs specific duplicates so that we can know which results in that range need to be imported later into the doublecheck database. Dave, is that possible yet? If not, how long do you estimate it will be before it will be?

Thanks,
Max :smile:

gd_barnes 2010-07-05 20:42

Hum. That's strange. By the Emails that I remember seeing, the manual results for k=300-400 for n=600K-1M were imported long ago, yet the graph shows almost nothing for the range. Max, what's up with that?

mdettweiler 2010-07-09 20:00

[quote=gd_barnes;220646]Hum. That's strange. By the Emails that I remember seeing, the manual results for k=300-400 for n=600K-1M were imported long ago, yet the graph shows almost nothing for the range. Max, what's up with that?[/quote]
They're in the database, but the code that generates the graph has not yet been updated to include that range.

@Dave: :bump: :smile:

Flatlander 2010-09-17 19:24

Just in case this server is about to dry:
I'll have 4 cores on this until I get bored again. :rolleyes:

mdettweiler 2010-09-17 19:27

[quote=Flatlander;230159]Just in case this server is about to dry:
I'll have 4 cores on this until I get bored again. :rolleyes:[/quote]
Thanks for the heads-up. There should be plenty of work in there to keep 4 cores busy for quite a while, but I'll keep an eye on it just to be sure.

gd_barnes 2010-09-18 01:36

Thanks for chipping in Chris.

Flatlander 2010-09-25 13:22

Looks like 2057*2^345230-1 is a missed prime? Or maybe the test limit of 350k was wrong?
[URL="http://www.noprimeleftbehind.net/stats/index.php?content=prime_list"]Recently found primes[/URL]
[URL="http://www.rieselprime.de/Data/02000.htm"]Primes from k=2000[/URL]
NPLB, right? :smile:

kar_bon 2010-09-25 17:38

[QUOTE=Flatlander;231384]Looks like 2057*2^345230-1 is a missed prime? Or maybe the test limit of 350k was wrong?
[/QUOTE]

In 2006-2007 T.Ritschel tested the range k=2001-2599 (for most k not divisible by 3) and gave a testrange of n=200k-350k.
I've to look for that post, but he submitted many primes at the RPS-thread [url=http://www.mersenneforum.org/showthread.php?t=4938]POST LOTS AND LOTS AND LOTS OF PRIMES HERE[/url].
See the outdated page I've compiled those days [url=http://www.15k.org/Summary02000.htm]here[/url].

I've also found some missed primes in this range and Thomas got no results anymore to verify. So perhaps there're some more primes not known yet!

PS: IIRC there were also some missing primes caused by issues with LLR 3.6.2.

mdettweiler 2010-09-25 19:17

[QUOTE=Flatlander;231384]Looks like 2057*2^345230-1 is a missed prime? Or maybe the test limit of 350k was wrong?
[URL="http://www.noprimeleftbehind.net/stats/index.php?content=prime_list"]Recently found primes[/URL]
[URL="http://www.rieselprime.de/Data/02000.htm"]Primes from k=2000[/URL]
NPLB, right? :smile:[/QUOTE]
Hence why we're re-checking [i]all[/i] k's in the k=2000-3000 range in the 12th Drive. :smile:

vaughan 2010-10-01 01:50

2069*2^257024 is prime. Too small for Top 5000 list.

mdettweiler 2010-10-01 01:57

[QUOTE=vaughan;232154]2069*2^257024 is prime. Too small for Top 5000 list.[/QUOTE]
For this drive, you don't need to bother reporting the small primes you find; none of them will be top-5000-worthy and as such the plan is to itemize them all at the end.

mdettweiler 2010-10-19 06:59

Reserving k=2200-2400, n=250K-350K for port 7000. (It's not quite ready to dry out just yet, but it will be getting there soon, so I figured I'd do this now so I don't forget.)

mdettweiler 2010-12-21 01:42

Reserving 2400-2425 for Sloth PRPnet.

Sloth 2010-12-23 04:43

Please add 2426-2475 to the prpnet server. It looks like psp is going to take a while to get up and running with the new server and I don't want to have to keep up with things over the holidays.

mdettweiler 2010-12-23 05:19

[QUOTE=Sloth;243043]Please add 2426-2475 to the prpnet server. It looks like psp is going to take a while to get up and running with the new server and I don't want to have to keep up with things over the holidays.[/QUOTE]
Okay, I've extended your reservation to k=2475 and the new candidates are being loaded into the server right now. :smile:

mdettweiler 2011-01-06 02:58

1 Attachment(s)
Sloth has completed k=2400-2475, n=250K-350K. The processed results have been sent to Gary, and a list of all the primes found in this range is attached.

MyDogBuster 2011-07-06 17:04

Chart hole
 
On the drive progress chart [URL]http://www.noprimeleftbehind.net/stats/index.php?content=drive_progress[/URL] there is a hole for k=2500-2600 for n=0-250K. Looked to be a part of drive 12a. Anyone know what happened here? If someone would send me the candidates I could finish it.

mdettweiler 2011-07-06 18:04

[QUOTE=MyDogBuster;265661]On the drive progress chart [URL]http://www.noprimeleftbehind.net/stats/index.php?content=drive_progress[/URL] there is a hole for k=2500-2600 for n=0-250K. Looked to be a part of drive 12a. Anyone know what happened here? If someone would send me the candidates I could finish it.[/QUOTE]
That range has been a bit of a mess in the DB for a year or two now; we had initially attempted to test it with a PRPnet 2.4.x server, but discovered partway through that the non-multithreaded PRPnet 2.4 was unable to handle the load of more than a few clients on such small numbers, and Bruce offered to do the whole k=2400-2600 range (including some parts that were already in the database from the PRPnet server) manually. The plan, as outlined at the time, was to leave the original PRPnet data in the database, since it was accurate for the results that did get put in there, so that the original contributors wouldn't lose their credit, and then import the remainder from Bruce's manual run. His results that duplicated ones already in the database would then be credited as doublechecks in the future when we get that database mechanism set up.

Since then, Dave and I have been working off and on to develop an alternate data-loading mechanism that will allow us to import Bruce's manual results to the DB while logging which ones are already there (so we know which to later import to the doublecheck database). Both Dave and I have been rather cramped for time of late, so we've been making progress rather gradually, but we're nonetheless working on it. :smile:

The simplest fix would be to just delete all the data from the initial, incomplete PRPnet run, and load Bruce's manual results to replace it. This would, however, cause those who contributed to the PRPnet test run (mostly Lennart, if I remember correctly) to lose credit, which is why we have been pursuing the more complicated solution outlined above.

When Dave and I finish working on the alternate loading mechanism, we'll actually be able to kill two birds with one stone: in addition to cleaning up the Drive 12a mess, we can use the same scripts to handle the re-import of certain results from the 1st Drive that were never actually imported in the first place (back then it was all a manual process and we must have skipped over these). This will clean up the results in the database erroneously credited to user "Unknown", leaving only truly "Unknown" results (for instance, those credited to usernames like "PG_Username", the default userid in PrimeGrid PRPnet packages) credited as such.

MyDogBuster 2011-07-06 19:24

Thanks Max, I was just trying to get the chart to look purdy. LOL

MyDogBuster 2011-07-09 18:26

I'll pick up Drive 12 again as soon as I get a new PS for the machine running it.

POOF.

gd_barnes 2011-12-10 22:08

Reserving k=2477 to 2600 for port 7000.

gd_barnes 2011-12-11 19:04

Reserving k=2600 to 3000 for port 7000. This will be all for n=250K-350K. n=350K-425K remains.

gd_barnes 2011-12-31 22:29

Reserving k=2000-2400/n=350K-425K for port 7000.

gd_barnes 2012-01-06 06:45

Reserving k=2400-3000/n=350K-425K for port 7000.

gd_barnes 2012-01-31 05:38

I have now posted all of the primes up to n=350K as well as k<2600 for n=350K-425K on this drive in the 1st post here.

Karsten, please check the number of new and confirmed primes for all ranges for n>250K against your Riesel primes pages.

Max, please have Dave delete all k=2400-2600 for n=50K-250K and then re-add Brucifer's primes for this range. Let's get this done please! It's time to get rid of that hole in the DB graph.

Karsten or Max, please process the results (residues) to me for all n=250K-350K. Preferred would be in k=100 ranges. After we are done with n=350K-425K, then we can process that range.

Thanks!


Gary

AMDave 2012-02-01 13:42

email sent
patch applied
ready for Max to add the replacement results files

NB - there will be some changes to the stats on the NPLB stats and therefore also on Free-DC Stats

gd_barnes 2012-02-16 09:52

Port 7000 has dried out for new pairs. Only straggling pairs remain. Upon completion of the remaining pairs, NPLB will have completed the non-top-5000 portion of the project and all k<3000 will have been fully completed to n=600K! This was one of the major objectives of the project when it started...to leave no primes behind! :smile:

MyDogBuster 2012-02-16 20:28

Nice job guys. :banana::bow:

vaughan 2012-02-17 10:08

What now? There seems to be zilch on 9000 and 7000; and the 3500 tasks take too long.

gd_barnes 2012-02-17 10:12

[QUOTE=vaughan;289684]What now? There seems to be zilch on 9000 and 7000; and the 3500 tasks take too long.[/QUOTE]

Zilch on 9000?? There's plenty on both PRPnet ports 2000 and 9000. See the port 9000 status page at [URL]http://www.noprimeleftbehind.net:9000/all.html[/URL]. There are over 46000 pairs yet to be completed. Are you having problems connecting to it? You have many pairs assigned to you that are from 20 to 60 hours old as of this posting. Like I said yesterday, I did increase the expiration time to 72 hours on that port so it is the same as port 2000 now.

Port 3500 is the only LLRnet port left on the project. After those 6 k's are complete to n=2M, we'll probably load another 6 k's in there for n=1M-2M so the tests will be shorter for a period of time. We'll probably hang on to that port for a while for our folks who like longer tests and LLRnet.

Regardless, our rally on port 2000 starts in < 2 days. I'd suggest beginning to move some machines there. The tests are almost identical in length to the port 9000 tests (actually just slightly shorter).

vaughan 2012-02-17 15:04

Oh it's my bad! I was after LLR so it seems port 3500 is it.

Nevertheless I'm having all sorts of hardware and mains power problems at the moment; I'll try to complete the tasks I have before the deadlines.

gd_barnes 2012-02-19 03:53

Early this morning, all pairs were officially completed on this drive. The admins will be completing the listing of the remaining primes in the 1st post over the next few weeks to get official totals.


All times are UTC. The time now is 05:39.

Powered by vBulletin® Version 3.8.11
Copyright ©2000 - 2020, Jelsoft Enterprises Ltd.