[quote=gd_barnes;150732]Of course we can! Perhaps we'll make the last rally 3 days! :smile:[/quote]
Maybe the last rally should run until Drive 1 ends. Of course, don't start it so early that the rally will last weeks, but maybe a few days. BTW so I don't slow down the ending edge of drive 1 (i.e. I'm not the last reservation to finish), do you think I should just run LLRnet after my current reservation ends or run small increments of manual files and then for the last bit run LLRnet? I'm thinking the latter, but that would mean taking new files every ~4.5 or ~9 days (either n=100 over both cores or n=100 per core) and getting the files ready, loading it into my spreadsheet to keep track of times, etc.
Will another drive start up before this one ends or not?

[quote=Mini-Geek;150734]Maybe the last rally should run until Drive 1 ends. Of course, don't start it so early that the rally will last weeks, but maybe a few days. BTW so I don't slow down the ending edge of drive 1 (i.e. I'm not the last reservation to finish), do you think I should just run LLRnet after my current reservation ends or run small increments of manual files and then for the last bit run LLRnet? I'm thinking the latter, but that would mean taking new files every ~4.5 or ~9 days (either n=100 over both cores or n=100 per core) and getting the files ready, loading it into my spreadsheet to keep track of times, etc.
Will another drive start up before this one ends or not?[/quote]


Interesting idea on the last rally. We'll consider that.

Whatever you want to do on your manual reservations is fine. Taking smaller ranges every week or so and then filling in at the end with LLRnet is no problem. You know the objective so I'm sure you won't bite off more than you can finish before year end. Thanks for asking.

On starting up a new drive before this one ends; I was personally thinking that when this one is likely down to less than a week remaining, we'll start k=400-600 for n=600K-1M for manual reservations only to start with and when this drive completes, then we'll open it up for LLRnet. At that time, we'll also open up k=600-800 and 800-1001 for n=600K-1M as well as k=1005-2000 for at least n=50K-100K if not higher. Once we get more sieving done on k=1005-2000, perhaps we'll start another drive for that k-range for top-5000 work; perhaps n=350K-500K. All of the k=1005-2000 work is still open to team discussion on how to process it.


Gary

[QUOTE]On starting up a new drive before this one ends; I was personally thinking that when this one is likely down to less than a week remaining, we'll start k=400-600 for n=600K-1M for manual reservations only to start with and when this drive completes, then we'll open it up for LLRnet. At that time, we'll also open up k=600-800 and 800-1001 for n=600K-1M as well as k=1005-2000 for at least n=50K-100K if not higher. Once we get more sieving done on k=1005-2000, perhaps we'll start another drive for that k-range for top-5000 work; perhaps n=350K-500K. All of the k=1005-2000 work is still open to team discussion on how to process it.

[/QUOTE]

I wouldn't mind seeing a server (maybe IB5000) doing some K work, like loading it with a couple of higher weight k's. It would help clean that out. I fear the manual k effort being left behind. People could then point a core or 2 towards that. JMHO

[quote=MyDogBuster;150754]I wouldn't mind seeing a server (maybe IB5000) doing some K work, like loading it with a couple of higher weight k's. It would help clean that out. I fear the manual k effort being left behind. People could then point a core or 2 towards that. JMHO[/quote]


You'll see me start to do much more of the individual-k work after the 1st drive is done. I'll likely do it in 'mini-drive' type fashion, where I'll reserve 5 k's at a time for n=600K-700K while others are free to reserve those same k's for n>700K. Searching above n=~900K doesn't really appeal to me very much at this point.

I'm not too concerned about them being left behind because the regular drives will have 100 k's each in them and will move along quite slowly due to the high n-ranges. If any k=300-400 gets left at n=600K for too long, we'll promote them or we (meaning me or others such as yourself with significant resources) can pick them up and move them a little higher.

I agree that k=300-400 should technically stay somewhat ahead of k=400-1001 as for how high it has been searched.

David has offered to host a private LLRnet server for anyone who wants to use one. Max is currently using one and I used one in the past.


Gary

[QUOTE] Searching above n=~900K doesn't really appeal to me very much at this point.
[/QUOTE]

I'm not thrilled about them either. Maybe we could take all the 900's that we (or anyone else who doesn't want to do them) reserve and put them in a private server at Davids and just point a core or 2 at them. Sort the pairs by n so that no k gets priority and have at it. I'm not sure how the output is handled, but at least we wouldn't have to monitor them. I hate to create work for others. I'm sure we could think of other things to put in that server.

i think we should have a last rally on drive 1 from just before christmas(so people dont have to bother on christmas day) until new year or until the drive finishes

Every day should be a drive day. :wink:
Come on over when ever you feel like it, Gary says I have plenty of pairs to go around :grin:

[quote=MyDogBuster;150772]I'm not thrilled about them either. Maybe we could take all the 900's that we (or anyone else who doesn't want to do them) reserve and put them in a private server at Davids and just point a core or 2 at them. Sort the pairs by n so that no k gets priority and have at it. I'm not sure how the output is handled, but at least we wouldn't have to monitor them. I hate to create work for others. I'm sure we could think of other things to put in that server.[/quote]

I'm assuming that you are implying to take a bunch of k's ranges for k=300-400 for n=900K-1M and put them in a server, regardless of whether those k's are reserved or are being tested for n=600K-900K. Keep in mind that when we get n-ranges thrown around with large gaps in between, it takes extra time to administer the results afterwords. It's also a little messier for Karsten to show it on his pages. The best thing to do would be for you or whomever reserves k's in the individual-k drive if you don't like n>900K is to only reserve n=600K-900K and let others who'd like to search n>900K take those. In that drive, I state that partial reservations are perfectly fine.

Why don't we discuss it more as we get closer to finishing the 1st drive? I'm still trying to sort out the mess of results from the 4th drive right now and I want to get some things moving on the CRUS project at the moment. I'm trying to avoid administering any more different efforts here at this particular moment so I can get ready for the large amount of drives we'll have here after the 1st drive is done.


Gary

I don't mind doing all the 900's work...

[quote=em99010pepe;150783]I don't mind doing all the 900's work...[/quote]

Hum. Perhaps we can work something out.

547.1-.3 complete no primes. ETA for .3-.5 is 12/7, for .5-.7 is 12/17.

More two days and 567.0-570.0 is done...taking 577.0-578.0 for C443.

575.0 - 575.2 Complete No Primes Results emailed

I just got a PM from Beyond requesting a large range :grin:, so I'll put him down for 590K-600K. :smile:

[quote=mdettweiler;151319]I just got a PM from Beyond requesting a large range :grin:, so I'll put him down for 590K-600K. :smile:[/quote]
brilliant that should help a lot with finishing the 1st drive before new year

[quote=mdettweiler;151319]I just got a PM from Beyond requesting a large range :grin:, so I'll put him down for 590K-600K. :smile:[/quote]

So are we in schedule to finish Drive 1 by the end of the year? Lennart has the answer.
Meanwhile C443 is already sending work beyond 577k and I suppose more 2-3 days to receive the last results from 567-570 range.

Carlos

555.0 - 555.6 Complete 2 primes previously reported

Results emailed

Beyond has withdrawn his reservation of n=590K-600K.

[quote=gd_barnes;151465]Beyond has withdrawn his reservation of n=590K-600K.[/quote]

:cry:

567-570 done only waiting for Max confirmation. Please see results from 30/11/2008 and 01/12/2008. Thank you.

Carlos

Max, Carlos, Ian, and/or Mini-Geek:

Can you guys coordinate and calculate exactly how many k/n pairs that we are processing per day on this drive at this point? I just upped it to 8 quads (from 7) on port 400 and will leave it there until this drive is done so you could use my count from yesterday (or the day before) off of port 400 and add 14% to it.

Max, once that calculation is done, can you calculate approximately how many k/n pairs remain?

We need to see exactly where we are at and see if the end-of-year goal is feasible and if so, how long we need to plan a rally for.

Thanks guys.


Gary

It's going to be very close counting with the increase of n size.
G4000 is doing 4200 pairs/day, IB400 8814 pair/day and C443 1800 pairs/day. I'm doing 1000 pairs/day, Mini-Geek 236 pairs/day, what about you Ian?

I'll leave a message on XS forum to see if Glenn can add a few more cores for a week.

[quote=em99010pepe;151545]567-570 done only waiting for Max confirmation. Please see results from 30/11/2008 and 01/12/2008. Thank you.

Carlos[/quote]
LLRnet C443 has officially completed 567K-570K, lresults emailed to Gary. :smile:

[quote=em99010pepe;151550]It's going to be very close counting with the increase of n size.
G4000 is doing 4200 pairs/day, IB400 8814 pair/day and C443 1800 pairs/day. I'm doing 1000 pairs/day, Mini-Geek 236 pairs/day, what about you Ian?

I'll leave a message on XS forum to see if Glenn can add a few more cores for a week.[/quote]
Hmm...if I add up all those numbers, I get 16050 k/n pairs per day (not counting Ian's manual work, of course, which we don't yet have figures for). Based on an average of 1100 k/n pairs per n=100 range, and about n=25K left in Drive #1, there are ~275000 k/n pairs left to do.

If I divide 275000 by 16050, I get approximately 17 days to complete Drive #1. Of course, that is not factoring in any increases in the amount of time it takes to run each k/n pair, nor is it factoring in the amount of manual work that Ian does each day.

I'll see if I can come up with some more accurate calculations later, factoring in FFT jumps and Ian's manual work. :smile:

[quote=mdettweiler;151564]Hmm...if I add up all those numbers, I get 16050 k/n pairs per day (not counting Ian's manual work, of course, which we don't yet have figures for). Based on an average of 1100 k/n pairs per n=100 range, and about n=25K left in Drive #1, there are ~275000 k/n pairs left to do.

If I divide 275000 by 16050, I get approximately 17 days to complete Drive #1. Of course, that is not factoring in any increases in the amount of time it takes to run each k/n pair, nor is it factoring in the amount of manual work that Ian does each day.

I'll see if I can come up with some more accurate calculations later, factoring in FFT jumps and Ian's manual work. :smile:[/quote]
Okay...I just checked and it turns out that there are no more FFT jumps (based on a median k of k=701) in the 1st Drive! :grin: All the remaining work will be at the 40960 FFT length.

On my 2.2Ghz Core 2 Duo, I get about 0.82 ms per iteration at n=600K, again for k=701. For n=570K, I get [B]almost the exact same time per iteration[/B] - 0.82 ms!

Based on this, and presuming that my assumption of 11000 k/n pairs per n=1K is correct, then we're on course to finish Drive #1 by December 17! :grin:

If you guys see any glaring errors in these calculations, feel free to point them out. :smile:

[quote=mdettweiler;151565]Based on this, and presuming that my assumption of 11000 k/n pairs per n=1K is correct, then we're on course to finish Drive #1 by December 17! :grin:

If you guys see any glaring errors in these calculations, feel free to point them out. :smile:[/quote]
I don't see any glaring errors, but something you're not taking in to account is that not everything will finish at the same moment. I'm currently on course to finish on December 18th, so I shouldn't hold us up too much, but still...It should probably only be 1-5 days longer and still well within the end of the year, but it is something to consider.

I should easily finish my ranges by the 17th. Don't want to hold anything up. We certainly picked up some speed somewhere.

I also think I can sieve 1005-2000K to 1T by then. Should make for an interesting last 2 weeks this year in NPLB land.

Manually I'm doing about 800/day.

Reserve
 

[URL="http://gbarnes017.googlepages.com/NPLB-5780-5781.txt"]578.0-578.1[/URL]
[URL="http://gbarnes017.googlepages.com/NPLB-5781-5782.txt"]578.1-578.2[/URL]
[URL="http://gbarnes017.googlepages.com/NPLB-5782-5783.txt"]578.2-578.3[/URL]
[URL="http://gbarnes017.googlepages.com/NPLB-5783-5784.txt"]578.3-578.4[/URL]
[URL="http://gbarnes017.googlepages.com/NPLB-5784-5785.txt"]578.4-578.5[/URL]

Taking those.

/Lennart

[quote=mdettweiler;151565]Okay...I just checked and it turns out that there are no more FFT jumps (based on a median k of k=701) in the 1st Drive! :grin: All the remaining work will be at the 40960 FFT length.

On my 2.2Ghz Core 2 Duo, I get about 0.82 ms per iteration at n=600K, again for k=701. For n=570K, I get [B]almost the exact same time per iteration[/B] - 0.82 ms!

Based on this, and presuming that my assumption of 11000 k/n pairs per n=1K is correct, then we're on course to finish Drive #1 by December 17! :grin:

If you guys see any glaring errors in these calculations, feel free to point them out. :smile:[/quote]


HOLY SMOLY!! :surprised:surprised:surprised

Something in my gut tells me this is incorrect. It's taking a good couple of weeks for us to process the only n=~11K range that is currently loaded in
port 400. I still can't see how we'll do the entire n=578K-600K range that is left in just 2.5 weeks. Perhaps BlisteringSheep adding the equivalent of ~2 quads has helped more than I expected. I'm going to have to do a very detailed check on this since I'll quickly be able to get the exact k/n pairs remaining for unreserved ranges.

But if it is correct, heck we don't need rallies or anything else. That said, we'll still have at least 1 rally because they're fun! :smile: Regardless, to finish 2 weeks early would be very exciting!

Edit: BTW, if some people's reservations are still being worked on a few days after the servers are dry, that's no big deal as long as they're done before year end! :-)


Gary

In the past 5 days, we have completed (now located at the top of the stats page) [url]http://nplb.ironbits.net/progress_400.html[/url]
Total knpairs for all days shown: [B]41408

[/B]

[quote=mdettweiler;151564]Hmm...if I add up all those numbers, I get 16050 k/n pairs per day (not counting Ian's manual work, of course, which we don't yet have figures for). Based on an average of 1100 k/n pairs per n=100 range, and about n=25K left in Drive #1, there are ~275000 k/n pairs left to do.

If I divide 275000 by 16050, I get approximately 17 days to complete Drive #1. Of course, that is not factoring in any increases in the amount of time it takes to run each k/n pair, nor is it factoring in the amount of manual work that Ian does each day.

I'll see if I can come up with some more accurate calculations later, factoring in FFT jumps and Ian's manual work. :smile:[/quote]

I couldn't resist going into more detail now that we have all of the figures. There were no glaring errors although there was a "moderate-sized" error in that the amount that we have remaining was underestimated by a fair amount. Thanks to everyone's info., we can now get a very detailed estimate:

First some assumptions:

Port 400:
1. Apparently BlisteringSheep dropped his machines off of port 400 sometime yesterday so I'm assuming that he won't have any on for the rest of the time.
2. I added an 8th quad to port 400 about the same time yesterday.

The approximate average on port 400 the last few days without Blis is 7150. Adding my additional quad adds another 750. This results in an average of 7900 / day for port 400; moderately lower than Carlos's 8800 / day figure.

Manual ranges:
I will assume that everyone is approximately 1/3rd done with their currently reserved manual ranges. I will exclude Lennart's range altogether because I'll assume that he'll be done well before Dec. 17th with it.

Misc.:
The port 4000 figure looked close and I'll use everyone else's estimates for port 443 and their manual ranges.

Although we're losing about 900 pairs / day on port 400 with this estimate, my estimate WILL include the 800 pairs / day done manually by Ian. So the 2 will almost offset one another.

Now to the remaining pairs. There are a lot more remaining than originally calculated. Calculations as of ~8 AM GMT on Dec. 2nd:

[code]
n=578.5K-600K 250,170
port 400 39,569
port 4000 16,237
port 443 8,384
n=547.3K-547.7K 4,798 * 2/3 = 3,200 (assumes 1/3rd done)
n=575.2K-576K 9,278 * 2/3 = 6,185
n=576K-577K 11,613 * 2/3 = 7,742

Total remaining: 331,487

Process per day:
port 400 7,900
port 4000 4,200
port 443 1,800
Carlos 1,000
Ian 800
Mini 236

Total processing per day: 15,936
[/code]

Days remaining: 331,487 / 15,936 = 20.8

Now, even though there are no fftlen increases, the # of iterations per test still goes up. Example, let's say n=100K takes 100 secs. to test. For the same fftlen at n=120K, it would take 120 secs. to test.

The approximate average current test is n=572K. If you split the difference on what is left, you have (600K+572K)/2=586K. So the added time that it will take for the average remaining test will be 586K / 572K or 2.45% longer.

Adding 2.45% to 20.8 gives 21.3 days. Argh! That was a worthless adjustment. lol

So we're looking at finishing 21 days after Dec. 2nd or Dec. 23rd. Alas, Santa Claus arrives a bit early! :smile:

Hopefully Blis will be back, which will help. Regardless, let's see if we can get a rally in there and finish by the 20th or 21st!

It looks like I was way off base in thinking that there must be a serious error in the original calculations. I really thought it would be shortly after the end of the year when we would finish. Before Ian came on board, I was figuring on mid-late Jan.

Thanks to everyone for calculating your processing rates and for contributing all of your mean machines to our effort!


Gary

[QUOTE]Hopefully Blis will be back, which will help. Regardless, let's see if we can get a rally in there and finish by the 20th or 21st!
[/QUOTE]

So everyone has been challenged to finish this BEFORE the fat guy gets stuck in my chimmney again. I read Gary's analysis post and got a headache halfway thru, but all seems plausible barring any unforseen disasters.

[quote=MyDogBuster;151599]So everyone has been challenged to finish this BEFORE the fat guy gets stuck in my chimmney again. I read Gary's analysis post and got a headache halfway thru, but all seems plausible barring any unforseen disasters.[/quote]


He he. My estimate posts create headaches for many folks. Math is fun!

My estimates of times to complete ranges at CRUS get even worse. I won't go there. The problem is that people will sometimes reserve 50-100 CPU years of work and won't even realize it thinking that they can complete it in a few months on their single quad! lol

[quote=gd_barnes;151601]He he. My estimate posts create headaches for many folks. Math is fun!

My estimates of times to complete ranges at CRUS get even worse. I won't go there. The problem is that people will sometimes reserve 50-100 CPU years of work and won't even realize it thinking that they can complete it in a few months on their single quad! lol[/quote]
no matter how hard i try i cannot work how you get some of your results from some of your CRUS estimates

[quote=henryzz;151603]no matter how hard i try i cannot work how you get some of your results from some of your CRUS estimates[/quote]


It isn't easy. You have to remember that the testing times vary by the square of the exponent. n=200K takes 4 times as long to test as n=100K. Also, the k's remaining reduce at a reverse logarithmic rate (or a reverse compound-interest rate; not sure what the correct term really is there). That is at n=10K, there might be 48 k's remaining and at n=20K, there might be 36 k's remaining; which means that there is a 25% reduction in k's remaining for each doubling of the n-value. Therefore, the estimate is that you should have 36*.75=27 k's remaining at n=40K.

Since I put some of those estimates up, I realized that there is a slight error in my calculations: The k's remaining do NOT reduce at a reverse logarithmic rate because the average weight of the final few k's is much lower than previous k's. I do not know the proper way to make such an adjustment. Using the above situation with 36 k's remaining at n=20K, it could be that the estimate should be that there should be 29 k's remaining at n=40K but that is only a guess. Still, using the above estimate gives the least amount of time that it SHOULD take. It gives a general idea of the amount of work reserved.


Gary

my 2 cent :-)
last days pairs submitted to all server:
2008-11-25: 13427
2008-11-26: 13809
2008-11-27: 14163
2008-11-28: 15093
2008-11-29: 15169
2008-11-30: 14953

there're about 320,000 pairs remain (in server-pool or not reserved yet).
so with about 15,000 pairs per day we have 21 days left!

[quote]
The problem is that people will sometimes reserve 50-100 CPU years of work and won't even realize it thinking that they can complete it in a few months on their single quad! lol [/quote]

That's why when I start something new, like I just did this week over at CRUS, I ALWAYS start small and build up. That way I know I can finish before the house falls down around me. (Probably caused by the fat guy being stuck in the chimmney).

575.2K-576K is 50 % completed.
I think today I'll receive a quad-core for my work....hehehe

Complete
 

[URL="http://gbarnes017.googlepages.com/NPLB-5780-5781.txt"]578.0-578.1[/URL]
[URL="http://gbarnes017.googlepages.com/NPLB-5781-5782.txt"]578.1-578.2[/URL]
[URL="http://gbarnes017.googlepages.com/NPLB-5782-5783.txt"]578.2-578.3[/URL]
[URL="http://gbarnes017.googlepages.com/NPLB-5783-5784.txt"]578.3-578.4[/URL]
[URL="http://gbarnes017.googlepages.com/NPLB-5784-5785.txt"]578.4-578.5[/URL]

They are done.

/Lennsrt

what pc has Wabbit98 got on port 400
he is only managing 1 or 2 pairs an hour
i would guess he is puting an old amd to use:smile:
[U][/U]

Is it possible to put more work available?

[quote=em99010pepe;151712]Is it possible to put more work available?[/quote]
Okay, I can add more shortly. How much are you specifically interested in? If you're looking for a larger range, I can make a big file of that size for you.

[quote=mdettweiler;151720]Okay, I can add more shortly. How much are you specifically interested in? If you're looking for a larger range, I can make a big file of that size for you.[/quote]
Okay, I've added another n=1K worth of work (10 files). :smile:

[quote=henryzz;151687]what pc has Wabbit98 got on port 400
he is only managing 1 or 2 pairs an hour
i would guess he is puting an old amd to use:smile:
[/quote]


You should have seen BlisteringSheep for a while. For several days to a couple of weeks, he was processing something like 3 pairs per day. lmao

Oh well, we welcome prime searchers of all resources. LLRnet is a great place for very old connected machines. Every little bit helps.


Gary

[quote=Lennart;151657][URL="http://gbarnes017.googlepages.com/NPLB-5780-5781.txt"]578.0-578.1[/URL]
[URL="http://gbarnes017.googlepages.com/NPLB-5781-5782.txt"]578.1-578.2[/URL]
[URL="http://gbarnes017.googlepages.com/NPLB-5782-5783.txt"]578.2-578.3[/URL]
[URL="http://gbarnes017.googlepages.com/NPLB-5783-5784.txt"]578.3-578.4[/URL]
[URL="http://gbarnes017.googlepages.com/NPLB-5784-5785.txt"]578.4-578.5[/URL]

They are done.

/Lennart[/quote]


I think Lennart is just showing off here. lol

Nice work. :smile:

Edit: Max, when you get a chance, can you do a quickie conversion of Lennart's results file to the standard LLR format. I'd do it if I wasn't on a business trip. Thanks.


Gary

Someone please check the first post of this thread...someone made a really big mess.

Carlos

[quote=em99010pepe;151775]Someone please check the first post of this thread...someone made a really big mess.

Carlos[/quote]
Uh oh :surprised I hope all that info is easily recoverable!

[quote=Mini-Geek;151780]Uh oh :surprised I hope all that info is easily recoverable![/quote]
Yep, it's recoverable. Thank God that didn't happen a few months ago, before Xyzzy upgraded the forum and added the "edit-log" feature for moderators! :surprised

Edit: Aw man, now all the manually-spaced tables got messed up in the restore. I'll get them fixed up within the next few hours...at least the data itself isn't lost. That would have been a huge pain in the butt to piece together all over again from scratch.

[quote=gd_barnes;151763]I think Lennart is just showing off here. lol

Nice work. :smile:

Edit: Max, when you get a chance, can you do a quickie conversion of Lennart's results file to the standard LLR format. I'd do it if I wasn't on a business trip. Thanks.


Gary[/quote]
No problem, will do as soon as I get the range tables fixed. :smile:

Okay, I've fixed the range tables. Phew! :smile:

Now on to Lennart's results...

[quote=mdettweiler;151788]Yep, it's recoverable. Thank God that didn't happen a few months ago, before Xyzzy upgraded the forum and added the "edit-log" feature for moderators! :surprised

Edit: Aw man, now all the manually-spaced tables got messed up in the restore. I'll get them fixed up within the next few hours...at least the data itself isn't lost. That would have been a huge pain in the butt to piece together all over again from scratch.[/quote]
maybe someone should make backups of the first post of all our drives every week of something like that

[quote=henryzz;151812]maybe someone should make backups of the first post of all our drives every week of something like that[/quote]
Well, they're automatically backed up by the forum. For moderators, all the "last fiddled with by so-and-so" things at the bottom of edited posts are links, which, when clicked on, will show you a full history of all the edits that have been made to that post.

The only problem with this, however, is that apparently multiple spaces are compressed into one single space in the archive. That's why I had to painstakingly re-add all the spaces after restoring from the backup.

Maybe I'll send a PM to Xyzzy asking if it's possible to have the backups display in a fixed-width font instead of variable-width; that might just do the trick.

[quote=gd_barnes;151763]I think Lennart is just showing off here. lol

Nice work. :smile:

Edit: Max, when you get a chance, can you do a quickie conversion of Lennart's results file to the standard LLR format. I'd do it if I wasn't on a business trip. Thanks.


Gary[/quote]
Okay, here you go. :smile:

Reserving 578.5K-582K for LLRnet G4000, and 582K-587K for LLRnet IB400. :smile:

Edit: 578.5K-582K has been loaded into G4000, and 582K-587K sent to David.

Reserving 587.0k-587.4k. Please send me the files, thank you.

[quote=em99010pepe;151775]Someone please check the first post of this thread...someone made a really big mess.

Carlos[/quote]


Hum. That must have been me based on the timing of this.

Can anyone tell me what happened and what it looked like? It looks good now. I thought I just added the 2 primes that I found late yesterday.

[quote=em99010pepe;151829]Reserving 587.0k-587.4k. Please send me the files, thank you.[/quote]


File sent in a PM.

Looked something like this:

[quote=gd_barnes;123330][COLOR=black][FONT=Verdana]This is team drive #1 for No Prime Left Behind. We will be searching all 400 < K <= 1001 for n=333.2K to 600K.[/FONT][/COLOR]

Karsten (kar_bon) has created a web page [URL="http://www.rieselprime.org/NPLB/Drives/NPLB_Drive1.htm"]here[/URL] that shows details for the drive. He also maintaines a site that has almost all known Riesel primes. There is a page for the range of 300<k<2000 [URL="http://www.rieselprime.org/Data/00300.htm"]here[/URL]. The ranges searched and primes found from this project will be shown there.

Two excellent LLRnet server will be processing a large part of the range. For general info. on setting up and running the servers see [URL="http://www.mersenneforum.org/showthread.php?t=9959"][COLOR=#22229c]this thread[/COLOR][/URL]. The info. specific to the servers that needs to be entered into your llr-clientconfig.txt file is:

#1
server = "nplb.ironbits.net"
port = 400

#2:
server = "nplb.dynip.telepac.pt"
port = 443

[COLOR=black][FONT=Verdana]We have divided the manual files up into n=100 pieces. [/FONT][/COLOR][COLOR=black][FONT=Verdana]There should be an average of around 1100-1150 candidates in each file and should take around 5-9 CPU days to test for the current level of n-ranges. Feel free to take as many files as you can complete in around 2 weeks.[/FONT][/COLOR]

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

IMPORTANT NOTE: Please report all top-5000 primes with a project ID of 'PrimeSearch' to properly credit Michael Hartley's original project.

The project Admin's will take care of reserving ranges and entering primes at Michael's site after each n=20K range is completed.

[FONT=Verdana][COLOR=black]New primes found from drive #1:[/COLOR][/FONT]

Prime found by
791*2^576238-1 MyDogBuster
999*2^576128-1 MyDogBuster
749*2^573524-1 MyDogBuster
855*2^572656-1 MyDogBuster
439*2^572313-1 MyDogBuster
615*2^571871-1 MyDogBuster
615*2^571623-1 MyDogBuster

(more will be posted later)
[/code]Known primes not yet found in uncompleted reserved ranges:
735*2^547661-1
735*2^577763-1
675*2^578746-1

Known primes in unreserved ranges:
(none)

Known primes in ranges not yet posted:
861*2^599041-1
675*2^599539-1

[FONT=Verdana]Have fun and take down boat loads of top-5000 primes! :grin:[/FONT]


[FONT=Verdana]Gary[/FONT][/quote]

I think it was more like this (like it was truncated a few lines in to the prime list, not like random data in the middle was gone):
[quote=gd_barnes;123330][COLOR=black][FONT=Verdana]This is team drive #1 for No Prime Left Behind. We will be searching all 400 < K <= 1001 for n=333.2K to 600K.[/FONT][/COLOR]

Karsten (kar_bon) has created a web page [URL="http://www.rieselprime.org/NPLB/Drives/NPLB_Drive1.htm"]here[/URL] that shows details for the drive. He also maintaines a site that has almost all known Riesel primes. There is a page for the range of 300<k<2000 [URL="http://www.rieselprime.org/Data/00300.htm"]here[/URL]. The ranges searched and primes found from this project will be shown there.

Two excellent LLRnet server will be processing a large part of the range. For general info. on setting up and running the servers see [URL="http://www.mersenneforum.org/showthread.php?t=9959"][COLOR=#22229c]this thread[/COLOR][/URL]. The info. specific to the servers that needs to be entered into your llr-clientconfig.txt file is:

#1
server = "nplb.ironbits.net"
port = 400

#2:
server = "nplb.dynip.telepac.pt"
port = 443

[COLOR=black][FONT=Verdana]We have divided the manual files up into n=100 pieces. [/FONT][/COLOR][COLOR=black][FONT=Verdana]There should be an average of around 1100-1150 candidates in each file and should take around 5-9 CPU days to test for the current level of n-ranges. Feel free to take as many files as you can complete in around 2 weeks.[/FONT][/COLOR]

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

IMPORTANT NOTE: Please report all top-5000 primes with a project ID of 'PrimeSearch' to properly credit Michael Hartley's original project.

The project Admin's will take care of reserving ranges and entering primes at Michael's site after each n=20K range is completed.

[FONT=Verdana][COLOR=black]New primes found from drive #1:[/COLOR][/FONT]
[code]
Prime found by
791*2^576238-1 MyDogBuster
999*2^576128-1 MyDogBuster
749*2^573524-1 MyDogBuster
855*2^572656-1 MyDogBuster
439*2^572313-1 MyDogBuster[/quote]Can't you just use your mod powers, like Max used to restore it, to see the old version?

[quote=Mini-Geek;151843]I think it was more like this (like it was truncated a few lines in to the prime list, not like random data in the middle was gone):
Can't you just use your mod powers, like Max used to restore it, to see the old version?[/quote]
Here's approximately what it looked like, according to the edit log. I say "approximately" because the edit log doesn't preserve all spacing quite accurately...but, you can still get the general idea. :smile:
[quote]
[COLOR=black][FONT=Verdana]This is team drive #1 for No Prime Left Behind. We will be searching all 400 < K <= 1001 for n=333.2K to 600K.[/FONT][/COLOR]
Karsten (kar_bon) has created a web page [URL="http://www.rieselprime.org/NPLB/Drives/NPLB_Drive1.htm"]here[/URL] that shows details for the drive. He also maintaines a site that has almost all known Riesel primes. There is a page for the range of 300<k<2000 [URL="http://www.rieselprime.org/Data/00300.htm"]here[/URL]. The ranges searched and primes found from this project will be shown there.

Two excellent LLRnet server will be processing a large part of the range. For general info. on setting up and running the servers see [URL="http://www.mersenneforum.org/showthread.php?t=9959"][COLOR=#22229c]this thread[/COLOR][/URL]. The info. specific to the servers that needs to be entered into your llr-clientconfig.txt file is:

#1
server = "nplb.ironbits.net"
port = 400

#2:
server = "nplb.dynip.telepac.pt"
port = 443

[COLOR=black][FONT=Verdana]We have divided the manual files up into n=100 pieces. [/FONT][/COLOR][COLOR=black][FONT=Verdana]There should be an average of around 1100-1150 candidates in each file and should take around 5-9 CPU days to test for the current level of n-ranges. Feel free to take as many files as you can complete in around 2 weeks.[/FONT][/COLOR]

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

IMPORTANT NOTE: Please report all top-5000 primes with a project ID of 'PrimeSearch' to properly credit Michael Hartley's original project.

The project Admin's will take care of reserving ranges and entering primes at Michael's site after each n=20K range is completed.

[FONT=Verdana][COLOR=black]New primes found from drive #1:[/COLOR][/FONT]
[code]Prime found by
791*2^576238-1 MyDogBuster
999*2^576128-1 MyDogBuster
749*2^573524-1 MyDogBuster
855*2^572656-1 MyDogBuster
439*2^572313-1 MyDogBuster
615*2^571871-1 MyDogBuster
615*2^571623-1 MyDogBuster
459*2^571508-1 MyDogBuster

999*2^571360-1 MyDogBuster[/quote]

I'm not familiar with the edit log.

Reference what you guys are showing that it looked like here. Is that ALL that is was showing? Was that much data really missing?

[quote=gd_barnes;151858]I'm not familiar with the edit log.

Reference what you guys are showing that it looked like here. Is that ALL that is was showing? Was that much data really missing?[/quote]
Yes, that is all that was showing.

BTW, you can get to the edit log by clicking on the text "Last fiddled with by..." at the bottom of each post that has been edited at some point or another. (This also works for non-mods, too, on their own posts, at least until the edit timeout is reached.)

Send me all that stuff in a text file and I'll put it up on the nplb.ironbits.net website, until I can get it moved over the the stats.ironbits.net site.
That, or, I should have most of that information in the database already right?
Just need to get some php/mysql action going...

[quote=IronBits;151879]Send me all that stuff in a text file and I'll put it up on the nplb.ironbits.net website, until I can get it moved over the the stats.ironbits.net site.
That, or, I should have most of that information in the database already right?
Just need to get some php/mysql action going...[/quote]
Hmm...well, that could possibly work, though putting it all up on a website would probably be overkill for the range info (which, besides, isn't even the type of data that easily lends itself to an SQL database, as far as I can tell). Probably a better solution would be to, first of all, be more careful when editing the range tables in this thread and other threads like it, and secondly, to keep periodic backups in a text file on Gary and I's hard drives in case mersenneforum.org goes down for whatever reason. :smile:

We backup the forum twice a month.

We've had to recover data before so we learned to load the backup to a dummy forum. It isn't terribly difficult but it is time consuming, and boring.

I can't possibly figure out what I could have done to cause it to lose 90% of the info. Perhaps I accidentally deleted or changed the "[/code]" at the end of one of the boxes? I've done that before and all of the proper spacing is lost. It's a nuisance to get it back the way it was but the data is always all still there; just in poor looking format with few of the lines lining up properly.

I haven't a clue what caused it so I have no way to be "more careful" when editing it. lol

One thought: Max, is there any possibility that both you and I were trying to edit it at the same time and somehow stepped on each other?


Gary

[quote=gd_barnes;151912]I can't possibly figure out what I could have done to cause it to lose 90% of the info. Perhaps I accidentally deleted or changed the "[/code]" at the end of one of the boxes? I've done that before and all of the proper spacing is lost. It's a nuisance to get it back the way it was but the data is always all still there; just in poor looking format with few of the lines lining up properly.

I haven't a clue what caused it so I have no way to be "more careful" when editing it. lol

One thought: Max, is there any possibility that both you and I were trying to edit it at the same time and somehow stepped on each other?


Gary[/quote]
With how it was truncated, I'd guess that what happened is someone clicked Submit to edit it, but for some reason the communication was cut short a little in to the prime list. It wasn't as simple as a missing [/code] tag. After Max restored it from the log, things weren't lining up correctly because apparently the log doesn't store multiple spaces inside code tags correctly.

[quote=gd_barnes;151912]I can't possibly figure out what I could have done to cause it to lose 90% of the info. Perhaps I accidentally deleted or changed the "[/code]" at the end of one of the boxes? I've done that before and all of the proper spacing is lost. It's a nuisance to get it back the way it was but the data is always all still there; just in poor looking format with few of the lines lining up properly.

I haven't a clue what caused it so I have no way to be "more careful" when editing it. lol

One thought: Max, is there any possibility that both you and I were trying to edit it at the same time and somehow stepped on each other?


Gary[/quote]
No, there's no way we could have both been editing it at the same time. First of all, I wasn't on at all at 4 AM my time (which is roughly when you made the problematic edit.)

My best guess as to what happened is something along the lines of what Mini-Geek described. Which is quite believable, since you're connecting from a hotel internet connection, and those can sometimes be less reliable than yours at home. And there's probably no way to prevent it in that case, now that I think about it; the best you can do is to carefully look over the newly-edited post once it loads after you click "Submit". (I always do this after editing a post.)

Yep, I'm connecting from a hotel room but I hadn't had the connection drop yet. Oh well, yeah, that sounds like the most plausible explanation. While I'm out of town, what I think I'll do is copy-and-paste it into a Notepad document before editing it and then verify it afterwords.

I understand the edit log now. I never knew about that...interesting stuff. It's nice to know that we can get a prior version of a post back like that. Thank gish for the edit log and thanks for fixing it Max! :smile:


Gary

[quote=gd_barnes;151989]Yep, I'm connecting from a hotel room but I hadn't had the connection drop yet. Oh well, yeah, that sounds like the most plausible explanation. While I'm out of town, what I think I'll do is copy-and-paste it into a Notepad document before editing it and then verify it afterwords.

I understand the edit log now. I never knew about that...interesting stuff. It's nice to know that we can get a prior version of a post back like that. Thank gish for the edit log and thanks for fixing it Max! :smile:


Gary[/quote]
Oh, one more thing: when copying and pasting it into Notepad, be sure to copy the "full code" version of the post, i.e. including all the bbCode tags that define formatting. You can get to that by clicking the little button on the top-right corner of the post composition box (as shown in the attached screenshot); that button toggles between the "enhanced interface" and "standard interface". This will ensure that all formatting is kept.

For example, if I just copy and past ethis text from the beginning of the 1st post of this thread from the edit box normally, into Notepad, and then back here, I get this:
[quote]This is team drive #1 for No Prime Left Behind. We will be searching all 400 < K <= 1001 for n=333.2K to 600K.

Karsten (kar_bon) has created a web page here that shows details for the drive. He also maintaines 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.

Two excellent LLRnet server will be processing a large part of the range. For general info. on setting up and running the servers see this thread. The info. specific to the servers that needs to be entered into your llr-clientconfig.txt file is:

#1
server = "nplb.ironbits.net"
port = 400[/quote]As you can see, all the links and smilies have been zapped. And if there were any [noparse][code], [quote], or formatting tags in there, then it would be even worse.[/noparse]

However, if I copy and paste the version including the full bbCode into Notepad, it looks like this in Notepad:
[quote][noparse][color=black][font=Verdana]This is team drive #1 for No Prime Left Behind. We will be searching all 400 < K <= 1001 for n=333.2K to 600K.[/font][/color]

Karsten (kar_bon) has created a web page [url="http://www.rieselprime.org/NPLB/Drives/NPLB_Drive1.htm"]here[/url] that shows details for the drive. He also maintaines a site that has almost all known Riesel primes. There is a page for the range of 300<k<2000 [url="http://www.rieselprime.org/Data/00300.htm"]here[/url]. The ranges searched and primes found from this project will be shown there.

Two excellent LLRnet server will be processing a large part of the range. For general info. on setting up and running the servers see [url="http://www.mersenneforum.org/showthread.php?t=9959"][color=#22229c]this thread[/color][/url]. The info. specific to the servers that needs to be entered into your llr-clientconfig.txt file is:

#1
server = "nplb.ironbits.net"
port = 400[/noparse][/quote]And then it looks like this in the forum once you paste it into the edit box and submit it (or if you hit the "Preview Post" button):
[quote][COLOR=black][FONT=Verdana]This is team drive #1 for No Prime Left Behind. We will be searching all 400 < K <= 1001 for n=333.2K to 600K.[/FONT][/COLOR]

Karsten (kar_bon) has created a web page [URL="http://www.rieselprime.org/NPLB/Drives/NPLB_Drive1.htm"]here[/URL] that shows details for the drive. He also maintaines a site that has almost all known Riesel primes. There is a page for the range of 300<k<2000 [URL="http://www.rieselprime.org/Data/00300.htm"]here[/URL]. The ranges searched and primes found from this project will be shown there.

Two excellent LLRnet server will be processing a large part of the range. For general info. on setting up and running the servers see [URL="http://www.mersenneforum.org/showthread.php?t=9959"][COLOR=#22229c]this thread[/COLOR][/URL]. The info. specific to the servers that needs to be entered into your llr-clientconfig.txt file is:

#1
server = "nplb.ironbits.net"
port = 400[/quote]Much better--this time all the formatting has remained intact. :smile:

Max :smile:

Taking 587.4-588.0 for C443 server.

Yours truly on the CRUS project beat NPLB to a prime for Riesel base 16. (lol) Therefore I'm now showing 739*2^591681-1 as a known prime in the 1st post of this thread.

It's strange how close the 2 projects were to finding that same prime.

Brucifer is back?

I urgently need more work to C443, Lennart is on fire!

[quote=em99010pepe;152098]I urgently need more work to C443, Lennart is on fire![/quote]
Okay, I'll email you 595K-600K shortly...

Edit: Done. :smile:

Thank you. It's in.

That's a lot of work to add, I don't know how long Lennart will stay on C443. Perhaps it's better to reduce that range to 597-600, what do you think?

EDIT: I only added 598-600.

[quote=em99010pepe;152104]That's a lot of work to add, I don't know how long Lennart will stay on C443. Perhaps it's better to reduce that range to 597-600, what do you think?

EDIT: I only added 598-600.[/quote]
Okay, yeah, you're right. I'll reduce the range to just 598K-600K on the reservation table. :smile:

Excellent! Thanks for the boost Lennart. Can you give us an idea of how long you will crunch for us for the time being? That will help us balance the load of work in the servers. We appreciate it.

Oh, and it's nice to see you around again Bruce. Welcome back! :smile:


Gary

[quote=gd_barnes;152120]Excellent! Thanks for the boost Lennart. Can you give us an idea of how long you will crunch for us for the time being? That will help us balance the load of work in the servers. We appreciate it.

Oh, and it's nice to see you around again Bruce. Welcome back! :smile:


Gary[/quote]

I am not sure yet But you dont have to add more now.

I don't think i can crunch more then to 588k. :wink:

btw Did you jump to 587400 ?

/Lennart

577.0-578.0 and 587.4-588.0 are done for C443. Max, you can check the files, the last three I suppose.

Carlos

[quote=em99010pepe;152354]577.0-578.0 and 587.4-588.0 are done for C443. Max, you can check the files, the last three I suppose.

Carlos[/quote]
Okay, cool. I'll probably be out of the house for a large portion of today, but I may have enough time to get them processed somewhere in there. If not, I'll definitely be able to do them on Monday. :smile:

576.0 - 576.4 complete 2 primes previously reported

results emailed

577K-578K and 587.4K-588K completed by LLRnet C443, lresults emailed to Gary. :smile:

575.2-576.0 done

[url=http://em99010pepe.googlepages.com/lresults_NPLB-5752-5760.zip]lresults_NPLB-5752-5760[/url]

547.3-.5 complete. Estimate for 547.5-.7 finishing the range (and hopefully Drive 1) is 12/18.

Max, please add the rest of the ranges to IB400.

Carlos

[quote=em99010pepe;152525]Max, please add the rest of the ranges to IB400.

Carlos[/quote]
Well, we'll probably want to put at least some of them on G4000 when it comes back up--but, yes, you're right, most of these will be eventually loaded into IB400. By my estimate IB400 will dry its range at least by Saturday. When G4000 come back online I'll add 3K to it and 7K to IB400; that will clean up the rest of the ranges and should balance the two pretty well considering that Gary said he's going to switch his machines to G4000 when it comes back online.

[QUOTE]I'll add 3K to it and 7K to IB400; that will clean up the rest of the ranges and should balance the two pretty well considering that Gary said he's going to switch his machines to G4000 when it comes back online.
[/QUOTE]

Max/Gary I have no problerm switching back to G4000 if Gary wants to keep his "farm" on IB400 where most of the remaining work will be. At 4K / day + what Max was doing, it should be pretty easy to figure out what the spread between the machines should be. Let me know where you want me.

[quote=MyDogBuster;152534]Max/Gary I have no problerm switching back to G4000 if Gary wants to keep his "farm" on IB400 where most of the remaining work will be. At 4K / day + what Max was doing, it should be pretty easy to figure out what the spread between the machines should be. Let me know where you want me.[/quote]
First of all, I presume you meant .4K/day, instead of 4K? Even Lennart can't crank out 4K/day. :wink:

As for which server your machines would be most useful on: Gary, how do you think we should do this? I'm fine with whatever. :smile:

why not just keep everyone on IB400 it can cope with the load and it makes it easier to administrate

Oh, who knows. We'll figure it out a little later.

My plan was to switch to port 4000 but if Ian wants to, then perhaps I'll stay on port 400. That probably makes more sense. That way, I won't inadvertantly have pairs sent to me that Ian is ready to send results back on.

Henry, we can't all be on port 400 the rest of the way. Port 4000 still has quite a few pairs left to be processed.

OK, let's do this: Ian, switch all of your machines back to port 4000 after you get the word that we have everything working. (I'm hoping late Tues. night or early Weds. morning.) Stay on it until you dry it out. If we add all the remaining ranges to ports 400 and 443 and dry them before you dry port 4000, then we'll switch over to port 4000. If port 4000 dries first (more likely I think with the large amount of range left still not loaded in port 400/443), then you can switch back over to port 400/443.

To clarify, we won't add any more work to port 4000 for the 1st drive. It will all go into ports 400 and 443.

One further thing that Max, David, and I are in discussion about in PM's. I'm recommending that we add k=400-600 for n>600K to port 400 even before we have finished this drive. That way, we can just keep right on processing with no interruption and people can leave their cores there.

The good thing about k=400-600 for n>600K is that it is sieved far deeper and it's a much smaller k-range, so we'll process the n-ranges much more quickly for quite a while until we have another fftlen change.


Gary

[QUOTE]Ian, switch all of your machines back to port 4000 after you get the word that we have everything working. (I'm hoping late Tues. night or early Weds. morning.) Stay on it until you dry it out.
[/QUOTE]

Sounds like a plan.

[quote=gd_barnes;152597]Oh, who knows. We'll figure it out a little later.

My plan was to switch to port 4000 but if Ian wants to, then perhaps I'll stay on port 400. That probably makes more sense. That way, I won't inadvertantly have pairs sent to me that Ian is ready to send results back on.

Henry, we can't all be on port 400 the rest of the way. Port 4000 still has quite a few pairs left to be processed.

OK, let's do this: Ian, switch all of your machines back to port 4000 after you get the word that we have everything working. (I'm hoping late Tues. night or early Weds. morning.) Stay on it until you dry it out. If we add all the remaining ranges to ports 400 and 443 and dry them before you dry port 4000, then we'll switch over to port 4000. If port 4000 dries first (more likely I think with the large amount of range left still not loaded in port 400/443), then you can switch back over to port 400/443.

To clarify, we won't add any more work to port 4000 for the 1st drive. It will all go into ports 400 and 443.

One further thing that Max, David, and I are in discussion about in PM's. I'm recommending that we add k=400-600 for n>600K to port 400 even before we have finished this drive. That way, we can just keep right on processing with no interruption and people can leave their cores there.

The good thing about k=400-600 for n>600K is that it is sieved far deeper and it's a much smaller k-range, so we'll process the n-ranges much more quickly for quite a while until we have another fftlen change.


Gary[/quote]
Okay, that sounds good. In that light, I'll send an 8K range to IB400 right now; that will then leave 2K remaining in the 1st Drive in case C443 needs a bit more or possibly if Lennart wants to grab another range. Once we get closer to drying out IB400 after that, I'll add the last 2K and some k=400-600 n>600K work right after that. :smile:

BTW, IB400 finished the last of 560K-567K last night; I'll get that processed later today.

Edit: Oh, I almost forgot: Reserving 588K-596K for LLRnet IB400. That may have been somewhat obvious from my above message, but I figured I'd better make it official. :smile:

sorry i forgot about drying the other servers
in future i think 3 servers for one drive is a bit unnecessary though unless we have some [COLOR=Red]proxies[/COLOR]

A little boost:
reserving 596.0-596.2!

takin' one of the last available chunks!

[quote=nuggetprime;152625]A little boost:
reserving 596.0-596.2!

takin' one of the last available chunks![/quote]
File sent via PM.