On most of my machines I've been getting ~8% Ebolanator W/U's. I have no particular objection to outside work,but I feel the points should be approximate to those granted by R@H for a given amount of CPU time. This is not the case. Most of my machines have seen a significant drop. The worst one is down ~17%. Considering the small proportion of Ebolanator to other tasks,point yield would seem to be about zero. The next problem with Ebolinator is that it seems to have no time limit. I aborted one last week that had run 50+ hrs. I don't want to change preferences against outside work,if we can just get a clear statement as to how this works.

---

On most of my machines I've been getting ~8% Ebolanator W/U's. I have no particular objection to outside work,but I feel the points should be approximate to those granted by R@H for a given amount of CPU time. This is not the case. Most of my machines have seen a significant drop. The worst one is down ~17%. Considering the small proportion of Ebolanator to other tasks,point yield would seem to be about zero. The next problem with Ebolinator is that it seems to have no time limit. I aborted one last week that had run 50+ hrs. I don't want to change preferences against outside work,if we can just get a clear statement as to how this works.

Hi John

Why do you think it's 'outside' work? The Ebola work is a Bakerlab project as far as I'm aware. Also, the credit granted on my machine appears to be in line with the other tasks. I've just had a look at your machines and it's a possibility that the FX architecture doesn't do as well at some tasks as others. Fortunately, it generally seems to excel at Rosetta.

Danny

---