less than 100% complete?

[Burning Phoenix]

I not to long ago started using seti. Well after producing a few i had quit for a few months due to problems at home and moving out. I then burnt a p4 1.7 chip and replaced with a 1.8. Well i started doing seti again about 2 weeks ago with this new chip overclocked to 1980 mhz with stock heatsink/fan and voltage. The weird thing is i recently checked my seti.log and it shows something like 3 out of 50 Wu's had 100% and all the rest were in the 99.26% - 99.97 range completed. I am getting the credits for them so what is happening to these wu's?

[Jon]

I think it has more to do with a SETISpy problem...could be wrong.

Out of all 7 of my PCs and 10 processors, I may get 100% 1 in every 5 WUs.

[bodezafa]

I think this is normal mine does the same thing. I wouldend worry abouy it.

[davehau]

Hi there!

I would agree with the rest of the folk... don't worry about it.

My understanding is that SETI Spy checks the state.sah file every so often to get its stats. So I'd guess that if SETI Spy has just checked, and the work unit is 99.87% complete, that may be the last SETI Spy sees of that work unit, as your seti client may finish the work unit and send it off before SETI Spy happens to check again.

I've noticed I have a lot more of these "almost completes" in my SETI Spy log files on my faster machine than on any of my slower ones, which would make sense, I guess.

Dave

[Sir-Epix]

Originally posted by davehau
Hi there!

I would agree with the rest of the folk... don't worry about it.

My understanding is that SETI Spy checks the state.sah file every so often to get its stats. So I'd guess that if SETI Spy has just checked, and the work unit is 99.87% complete, that may be the last SETI Spy sees of that work unit, as your seti client may finish the work unit and send it off before SETI Spy happens to check again.

I've noticed I have a lot more of these "almost completes" in my SETI Spy log files on my faster machine than on any of my slower ones, which would make sense, I guess.

Dave

You are absolutely right. This is why not all of the work units are 100 percent complete.

[Morpheus]

the SETI client writes to the harddrive once a minute (or is 3.03 90 seconds now?, I know Berekely was going to change that)... At any rate, SETIspy logs results as they a written to the harddrive...

When the client finishes, the results are written to the results.sah file, which SETIspy does not monitor or log...

So, just like as has been written above.. the client finished before the next write to the harddrive...

If you want more accurate logging & client records (99%-ish), try calibrating your SETIspy...

Good luck!!!