I don't know what the problem is but my computer just uploaded a WU and it timed out at 58 seconds!! I really don't care about the credits, but something is wrong. The computer had the work unit for 2 days. The WU was 12506308. I don't know about the other CPU but I think it lost time too.

---

> I don't know what the problem is but my computer just uploaded a WU and it
> timed out at 58 seconds!! I really don't care about the credits, but
> something is wrong. The computer had the work unit for 2 days. The WU was
> 12506308. I don't know about the other CPU but I think it lost time too.
>
Actually, you can think of this as a CPU time increase. If it actually only crunched or 1 minute like it appears it did for the other host who has returned it, then you've been freed up to crunch another one. There are WU that contain to much noise (RFI, radio frequency interference) to be of any use, these return to many signals. Boinc/seti sees that and ends the WU prematurely, reports it, and this lets your host work on a new WU. In seti Classic it would have been a LONG WU and you'd have to have crunched it all.

hope this helps

tony

I wish that was the case, but my computer had crunched over 90% of its WU. It looks like the other computer had probably done a large percentage too. Who knows. I just didn't what them to get bad info. Probably doesn't make any differnce.

---

> I wish that was the case, but my computer had crunched over 90% of its WU. It
> looks like the other computer had probably done a large percentage too. Who
> knows. I just didn't what them to get bad info. Probably doesn't make any
> differnce.
>
I don't think Berkeley has time to babysit these freak WUs. It'll probably still be valuable if the whole timeframe of Wu's give similar results. It just won't net you much credit. Luckily, these are few and far between.

tony