View Full Version : 1 or 2% completed
I have a rather disturbing question...
I had a really good night of crunching one night, 6 WU done in less than 8 hours. That was my first flag. When I looked at the Spy log, I saw 3 units that were finished with less than 10% completed. To put it bluntly, WTF???
Usually, I see above 95% completed, and I'm wondering what could have caused this. :(
Kid
Usually is one of two things:
1) The WUs were bad...probably had alot of static or some other "noise" in the form of interference. Check to see how many spikes were encountered in those WUs. If there were alot, then SETI will automatically dump that WU. I've always gotten credit for these.
2) Your overclock is upsetting the calculation process and is interfering. I've had this problem as well and had to back off a bit.
Jon pretty much covered it all there. Most likely the work units had certain types of radio interference that the client sees as unaccetable, so after it processes a certain amount of that junk it dumps the unit and starts on a new one.
Hmmm, it would seem neither are the case... My OC'ing hasn't returned any errors in the burn in's I've done, and the WU's completed after all got above 99%. But anywho here's the log (from spy). I apologize for the formatting, but it's all there.
Date Time Work Unit Name Start Start Angle Tera- Process Percent Returned Best Returned Best Return
12/27/2001 5:16:17 AM 17my01ab.14901.19072.22154.253 20.866 23.840 0.534 0.076 0.034 1.91% 0 13.763 0 1.339 2 1.062 0 0.000
12/27/2001 10:34:29 AM 17my01ab.14901.19122.723566.84 20.896 23.700 0.526 0.171 0.084 4.27% 0 17.312 0 1.137 0 0.992 2 8.993
I could always be completely wrong.
I just hope it's not my computer. Can anyone suggest a good burn in proggy? I got one, but I'm questionable about it's quality.
Kid
I would still blame it on interference within the WU even though you don't have any spikes. I've had 4 in a row returned like that...all were fine after it and before it. Just had a problem with those 4.
If you use a caching program they could even have possibly been slightly corrupted during downloading or corrupt to start from Berkeley themsleves. It's really hard to say.
Kepp crunching and if all returns to normal then I would think no more about it. If WUs are still being dropped early then you may need to check your overclock. Other programs may run fine under it but that doesn't necessarily mean SETI will.
vBulletin® v3.8.7, Copyright ©2000-2012, vBulletin Solutions, Inc.