• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Need your SETI help.. :)

Fardringle

Fardringle

Diamond Member
I've seen this answered before on the forums, but I can't remember exactly how to do it, and can't seem to find the old thread.. 😱


Anyway, I have a half-dozen WU's that have been partially processed by computers I am no longer able to use, so I would like to transfer them to my main system at home to finish them up. However, I want to make sure that the computer only works on these WU's until they are done, rather than getting new WU's from my SetiQ. What would be the easiest way to do this?

I suppose I could just have the system work on all of them at the same time, but that would sure kill the average WU time!! :Q

I seem to remember someone setting up some kind of 'chain' or something to have several client directories (each one with a different WU in it) and use a batch file or other procedure to trigger the next one in line to start when the previous one finishes. Is this possible, and if so, how do I set it up? If not, what would be better?

Thanks for the help!
 
I'd recommend using SetiDriver. I once wrote a system that ran WUs in multiple directories. Then I found that SetiDriver uses about the same system, and modified my program to be compatible. I would have switched if SetiDriver worked with a ramdisk....

Anyway, I believe you need to put the .sah files for each WU in subdirectories of the SETI directory, named 1, 2, 3, 4... Then run SetiDriver from the SETI directory, and it should recognize all the WUs.
 
How would I get SetiDriver to recognize that the WU's had already been partially processed since I would just like to finish up these that have already been partially done? Or would it be able to do that automatically?
 
No help here but I'd cut the losses and save yourself the effort/time. Just start them from scratch. You're not going to lose a massive amount of WU's anyway. Cut your losses and save the effort. Just get the clients configured the way you want for the long haul so they're running on restarts and queued. Don't let the partials cloud your goal. You lose a few now and then. Clients lock up, users shut down their boxes, it happens. The goal is long term. 😉

Good luck!

Rob
 
It should work automatically. Just install SetiDriver in your SETI directory, put the WUs in those subdirectories, and you should be all set.

Of course if you want to "cut your losses" 😉 (or it doesn't work 😱), you can always give me the WUs. 🙂
 
Just make sure that you finish them with the same version of the seti client that you started them with or they will restart anyway.🙂

 
Hey Fardringle,

What exactly did you save when you closed out the old machines? When I take stuff off of a system I copy the whole directory to include the executables. Then I can put the whole thing on another system and restart where it left off. Depending on disk space you can omit the .exe's and take the rest.
 
I copied the complete directories...some of them are around 80% complete, so I'd rather not start over, but I don't have time today (lots to do 🙁) to check on the computer every hour or two to give it a new WU, so I was wondering the easiest way to do this.

I actually ended up having three of them run last night, and only lost an average 'efficiency' of about 20% on each of them, so I may try running two processes at the same time normally, just to see what happens.. 🙂

By the way, thanks again for the help and suggestions!
 
Why would you want new WU's for these clients? ,don't you want them to finish the Wu & then stop?
Like JWM said ,just run it from the copied directory.
BTW the state.sah file is the 1 which keeps track of the % done of a WU
 
I don't quite understand your obsession with your average WU times. The more WUs you finish the less each individual work unit will effect your average. So even if you have a dozen or so long times, they will eventually have a very minute effect on your WU average.

Anyway. If you have copied the whole directory and just want to finish the WU up, why don't you just have it stop after unit is done? All you have to do is start the client from dos prompt or the Run from the start menu, and add -stop_after_process. This sounds like what your wanting. It will finish up the WU then stop so you can erase the directory.


How long have these WUs been incomplete? If it has been more than 3 weeks there is the possibility that they have already rereleased them.

Good luck.
 
Fardringle:
Similar to what artemedes said, you can create a text file named stop_after_send.txt and put it in the directory with with the partially finished WU and it will send the results when finished and not reload with a new WU. The file can contain anything, or can be "0" bytes in size as it is the name that the program looks for. Then when the results are sent you can delete the whole directory.
 
Yeah, I know about the 'stop' function, I was just wondering if there was a way to make each of these individual copied client directories run in sequence (one finishes and the next one automatically starts...) Apparently, SetiDriver is capable of doing this, but it also looks like my K6-3+ likes running two clients at the same time!!

Average time for one client running is ~10.5 hours and average time with two clients running is ~17 hours, so I'm actually gaining time by running two...I know that this technically shouldn't happen-anybody have any ideas why this is? (Or maybe my 24 hour 'test' just included some especially short WU's?) I'll have to keep it running like this for a couple more days and see what happens! 🙂


My system is:
EPOX MVP3G5 motherboard
K6-3+ 450@600
128MB CAS2 PC100 RAM
Win98SE
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top