How many WU's can you cache with SETI driver?

NeoPTLD

Platinum Member
Nov 23, 2001
2,544
2
81
As the school gets out for the summer, this computer might not have network access utnil I return to school and I want to cache enough WUs for the summer.

How long does DL'ed cache stay valid for and how many could SETI Driver handle?

I tried 1,000 and it seems to download fine, but I had to exit SETI driver when about 300 WUs were DLed to restart the machine for something else.

When I tried to start SETI driver again, it takes 100% CPU and I think it's freezing up because the controls won't open up until I cleared out most of WUs.
 
Aug 27, 2002
10,043
2
0
2 of my crunchers have 500 WU's cached.(they are on dial up, and I never know when they will be able to leave the modems on for them to empty the cache.
 

amdxborg

Diamond Member
Aug 27, 2002
6,790
23
81
If you keep having trouble with SETI Driver, rather use SETI Queue to cache wu and SETI Driver can get wu from SETI Queue. ;)
 

Coquito

Diamond Member
Nov 30, 2003
8,559
1
0
The wu's are always valid(as long as the project is around), but any results cached for close to a month will probably just be adding to your total & nothing more. The results will have already been submitted by several other users by that time.
 

kamper

Diamond Member
Mar 18, 2003
5,513
0
0
Neo, I have done something very similar. When you have a few hundred folders it takes seti a while to get its bearings when it starts up and you also lose a bit of time in between wu's. The easiest way to fix this might be to just download the units and then move them to another folder. For instance, download 1000, stop the seti driver, copy numbers 101-1000 into a different folder and then crunch away. When the first hundred are done, move them into another folder and then swap the next hundred in. The driver is pretty good at dectecting funny numbered folders and will rename 101-200 to 1-100 automatically. Just make sure that you keep all the results seperated as they will have the same folder names.

Of course, an even easier solution would just be to run setiQ locally.