I fear that changing the scheduler so that it spreads problematic units across different platforms requires a fair bit of coding on David's part. Not something easily set in motion.

They really should get it fixed. Science/workunits are wasted. ET could be hiding in one of them.

There may be an easier solution. Most of the hosts involved here consistently report errors on GPU tasks. I think the number of tasks sent to these hosts should be limited to 1 (or only a couple) per day (so people have a chance to fix the problem and get tasks again). Right now they get a (single) task, it fails immediately and 5 minutes later they report the task that has the error and get a new task. This means that a single host can still send hundreds of invalid/error tasks every day. Would it be difficult to check if a host (once it has processed a number of tasks) has at least a certain percentage of valid results (during the last say 50 reported tasks) and limit the number of new tasks to a single task (or a couple of tasks) per day ?
Most of the information required is already available (I can find it in my host details).

Tom

Why not do both? To save science and bandwidth.

Well the good news is that the tapes that were used and got riddled with these errors will not be thrown away. Once the problem gets fixed, at some point in the future, we will run through those tapes once again and get good science out of them.

This isn't the first time something like this has happened, and that's what we ended up doing about it in the past.

---

Linux laptop:
record uptime: 1511d 20h 19m (ended due to the power brick giving-up)

Well the good news is that the tapes that were used and got riddled with these errors will not be thrown away. Once the problem gets fixed, at some point in the future, we will run through those tapes once again and get good science out of them.

This isn't the first time something like this has happened, and that's what we ended up doing about it in the past.

As I mentioned before this sort of things has come up before.
It can only be attributable to human error.

---

SETI@home classic workunits: 93,865 CPU time: 863,447 hours
Join the [url=http://tinyurl.com/8y46zvu]BP6/VP6 User Group[

The ati bug was realy fixed? ask because i just see and i receive one of the problematic WU yesterday.

http://setiathome.berkeley.edu/workunit.php?wuid=1271358183

---

The ati bug was realy fixed? ask because i just see and i receive one of the problematic WU yesterday.

http://setiathome.berkeley.edu/workunit.php?wuid=1271358183

Yes, it was fixed.

There is a lot of shrubbery waiting in the wings, of course.

---

"Freedom is just Chaos, with better lighting." Alan Dean Foster