Roelof spent a lot of time that I didn't have benchmarking WUs to write WU
progress calabration code.  SETI Driver doesn't have this code.  What you
see in SETI Driver is taken directly from the state.sah file, whereas
SETISpy has this code.  It's well known that v3 of the CLI doesn't report
progress linearly.  Instead, the first 5-10% is reported too fast, the
middle 10-95% is a little slow (not much), and the final part of the WU
processing is also faster.  SETI Driver doesn't make these distinctions.

Both programs are correct given the non-linear progress reporting by the
client.

Mike Ober.

"Orin" <orinbalenovic.NOSPAM@hotmail.com> wrote in message
news:MPG.19d4bdbb8c7b4da6989685@news.carnet.hr...

I' using SetiSpy and SETI Driver combination for monitoring/cashing.
They were set up to work together as described in SetiSpy faq, but they
show different percentage done; SS shows 3,72% and SD 6.50%. SetiSpy
version is 3.3.3 and SETI Driver is 1.6.4. What can be done to fix it?

thanks



-- 
Orin