Pre-combined sieving remaining.

[Brucifer]

In shooting emails back and forth with Lars, I have learned that besides the 23T left before we are in the combined ranges, there is also 4.7T in first pass ranges. He said he'd like to get the first pass stuff out of the way if possible, so I went ahead and reserved those ranges. As my systems complete the presently loaded 2nd pass stuff, I will load the first pass ranges in to the nextrange.txt files on my systems and start getting the first pass knowcked out. Then I will go back and complete the 2nd pass ranges that I have reserved. I estimate around a week to get the first pass stuff completed.

Just didn't want y'all thinking that I was leaving the 2nd pass 23T remaining stuff. It's all stuff that needs to be finished to get PSP to the point of sieving the combined ranges with SOB.

And thank you to those that have reserved some more of the 23T stuff!!!! And if any of you new team members would be interested in spending a month helping us out, I'd be more than happy to help you get set up and running for the psp sieving effort.

Bruce

[NeoGen]

I remember seeing those ranges there but didn't know they were really needed for the SOB merging.
I did one once (98000-98700) just to close the hole, and didn't get on them anymore.

[Brucifer]

yeah, I didn't know about them either. But we'll get there, as the ranges left to go are getting smaller each week.

[ltd]

To make it clear the first pass ranges are not the most important for the merge with combined sieving but as they are the lowest firstpass sieve ranges they should contain more low n factors then any other range. So these two ranges have a good chance to remove k/n pairs that would else be prp tested in the next few weeks/months. Which brings us ahead in the short term.

For example the combined range 133T-134T done by shauge contained 161 factors lower then 20M and four of them 2.1-2.4Mil. (The llrnet server hands out work in the range 2.05-2.25M at the moment)

For the ranges Brucifer reserved i would expect around 200 low factors per 1T and around 250 Factors>20M.

Conclusion these two ranges are the most important ranges the project has to offer at the moment.

To complete my priority list:
Second priority the 23T from second pass
Third Priority combined ranges.

And yes i do combined ranges most of the time.
I want to show to the SOB sievers that we want to help them and not only want to get their help. I am lucky at the moment that there are so many helping hands to give me the freedom to sieve ranges with lowest priority from my list.

Lars

[AMDave]

I made the switch from PRP to Seive last night.

It looks like I have a total of around 1350 kp/s chewing through my first range. About 20% of a 400 range is done in 24 hours, so I am pleased with the progress.

As I expect to keep topping up my nextrange.txt files for a while, moving range to range to range, I want to be able to send in intermediate results without allowing any of my clients to run out.

Is it safe just to "cut" the fact.txt and factrange.txt files from their directories while the client is still running on each machine, or does the Sobistrator provide another means for doing this like the Rieselator does?

Brucifer, I notice you have been sending in frequent updates, do you cut the files or cut the text from inside the files? Do you only send in the facrange.txt files at the end of a reservation or is the content directly linked to the content of the fact.txt file?

It would be REALLY cool if someone fixed up the Sobistrator to submit PSP Seive residues just like the Reiselator.

[Brucifer]

Say I take out a 1,000 block for sieving.

I seperate them into blocks of fifty. For instance the range is 50000 - 51000, the first block will be 50000 - 50050, the second is 50050 - 50100 and so on. I first start one system off with the first block, then once it is running, I stop it and load in the nextrange.txt so it reads:
pmin=50050000000000
pmax=50100000000000

save it, and then restart the sieving. I use linux, in console mode, and watch then. When that system completes the first range and has shifted into the second block, I stop it, and then copy the fact.txt to 50000-500050_fact.txt and also copy the factrange.txt to 50000-50050_factrange.txt. I edit the files to remove the factors that are out of range. Then I mv the 5* files to a seperate directory and after I get a bunch of them I tar them up and send them to Lars in the format of results.brucifer.20060303.tar.gzip and lars can then use his script to suck them right in. The 20060303 is year month day.

I then re-edit the nextrange.txt file to enter in the next range and start the client again.

Windows people can use sobistrator to take care of the bulk of the babysitting. I don't use sobistrator. Anyway I generally send them in every day or two. When I finish sending in everthing in that reserved range, then I add the endtry to the sive reservation forum and say it is complete.

You do not have to wait until everything is completed to send them in. And it isn't a good idea to do that anyway as that way if the HD or something goes kaput you don't lose a bunch of timetaking sieving results. I also retain a copy of the email message that I send to lars with the results just incase something happens and his system craps out or loses some results too, or also in case I made a mistake and forgot something.

I also save a copy of the range numbered result files on the computer they were crunched on, just in case I screw up and number something wrong somewhere along the line. I do not edit any fact* files while the client is running if that was one of your questions.

[AMDave]

Thanks Brucifer.
That makes sense.

I break up my block of 1000 into 1000 :D I keep track of progress of each machine in a workbook and so I can load-balance the work depending on each machines speed (they are all different). I seem to get away with topping up the nextrange.txt file without stopping the clients.

Thank you for explaining how to deal with the in-progress fact.txt files.
Incidentally, I wrote ftp scripts to copy the directories back to my main PC where I back them all up, and I cron'd the job to run each hour. I use the same script when I plug in the laptop when I get home from work. So I have an hourly backup copy of each machine's folder and progress.

I can easily pick up all the fact files from there.

I thought about writing the reverse so that I could modify the files locally and send them back to each machine, but I don't like the idea that I may cause the machine to do a range twice, so I stick with the hands-on method too.

[Brucifer]

ya.... some things are just better left to the hands on approach. Also due to the time it takes to re-crunch a range, I just don't like to add complicating methods to it.

I'm getting close to having half of the first pass stuff finished though. Will be glad to get back in the 60000 - 80000 range stuff again though.

[Brucifer]

I just turned in some more results. don't know if it is enough to get us past Rechenkraft or not, but it will be pretty close anyway. Hopefully this week we will edge by them.

[AMDave]

I think I have my ranges rolling over nicely.
I just dropped in my second batch.
Lars has processed them.
I'll have another batch mid-week.

Waiting for the stats to rollover tonight.

Did you see the last update?
Only ~15 Tera left !!!
We're knocking it down fast now.

Awfully good, Chaps. Tally Ho!