There are a number of things I can think of that might possibly be useful when this is done. I will list a few that spring to mind that might help those new to the project.

1. This project is not ideal for those who want to just sign up, then let things happen. Checking the forums regularly can be useful
2.There are often periods of time without any work interspersed with lots of work in a famine and glut pattern.
3. Unlike some projects throughput of work is unlikely to increase by using virtual cores.
4. Even on the very fastest processors, many tasks take several days to complete.

I will add to this list when things come to mind but please feel free to contribute or to second ideas that you think are the most important. It would be good to get ideas from the point of view of "ordinary" crunchers as well as those involved through moderation and or those with very advanced knowledge of computing, programming etc.

The website should probably have something discouraging people who regularly turn off their machines from crunching this project as well. - I have just picked up a resend this morning, one machine, it didn't make the transition from global to regional model, I had that happen to one of mine in testing that is running fine on another machine. It is what it is. The other failure however is from a machine with lots of suspend requests and is completing less than 5% of the tasks it, often taking several days between trickle up messages/zip uploads. It would be helpful if potential crunchers for the project were aware of the nature of the project and that repeated machine reboots are likely with some model types to result in task failures.

This is for the boinc side of things to handle. Such machines I believe get deprecated. There is also a mechanism in the scheduler to favour resends to machines most likely to return successful tasks.

---

---
CPDN Visiting Scientist