Well as long as it isn't going to stop other projects from running and thereby overshooting their time limits I'm willing...

I understand exactly how you feel. I did not experience this during the time I was active on the project.

---

Thanks.

---

Peter
Toronto, Canada

Well Neil Munday's stats counter has either picked the wrong Volpex or the wrong user because there is no way I could have all those points already as I haven't even added it to BOINC yet.

What a screw up. I can't even find a project URL on their website. The user ID they give me apparently belongs to someone called Fred who belongs to the Heidelberg team.

---

Peter
Toronto, Canada

I replied to your post at Neil's site.

I don't have time this evening to dig any deeper, but I can say that the project website is working, my stats are correct on Neils's stats and at Free-DC. Also, if you've only just joined, your stats won't have been exported yet to the XML user db dump, so just wait 24 hours and see what happens :)

Cheers,

Al.

OK, thanks.

They have fixed a number of bugs at this project and it works much better. Be warned that it is very, very different from any other BOINC project you have ever crunched. For example tasks never complete successfully, they always either error out or get cancelled/aborted by the server. Do not be alarmed, that is exactly the way this project is supposed to work. All error and cancelled/aborted (by the server) tasks do useful work and you will get credit for them. The reason why it works that way is explained in the forums.

Also, Volpex tasks arrive on your host with a very short deadline of about 5 minutes or less and a high "remaining time" estimate. Do not be alarmed and do not abort the the task. The reason for the short deadline and huge duration estimate is to force the task to start immediately and yes, it will run at high priority. This is necessary for the parallel execution paradigm Volpex is trying to develop. Yes, it does bump their tasks to the front of the line and it does cause other projects to wait but not for long because Volpex tasks are reasonably short in spite of the huge initial duration estimate. If you have set a sensible cache size then there will be no problem and over the long run your resource shares will be honored. For more info on the parallel execution paradigm and why the high priority tasks are necessary see the forums at Volpex.

The URL to put in the Add Project wizard is http://volpex.cs.uh.edu/VCP/