I have a number of projects through gridrepublic. Ive given each different weights for their resourse share. CPDN has the most weight (500%), and a few of the others (like rosetta) are at 50%...however, every time I look, lately, CPDN is only \"waiting to run\" and not \"ready to start\" or \"running\", where-as the other projects (with very low percentages of resource time) are consitently \"running\"...also there always seems to be 2 projects \"running\". I would have expected only one to be running at any given time. Is there any way to regulate this as well?

---

Probably your cpdn models ran for a long time while BOINC worked out how long it would take to finish, and now the other projects are being paid back the processing time that they\'re owed.
DON\'T FIDDLE! It will all work out in the long term.

You\'re running 2 because you have a 2 core processor, and you\'ve allowed BOINC to use both. There\'s an option in General prefs on the server to change the number of processors.

And your models all keep crashing, so you have a problem somewhere.
(Laptop overheating, perhaps?)
The READMEs here may help.

---

Backups: Here

ok (Ill assume nothings wrong concerning the percentage of processing time being allotted)...It had been a little while since I had checked the results for CPDN (or any other program through boinc as well). I see that all other programs through boinc (gridrepublic) seem to have the result of \"success\", CPDN is getting the result of \"Client Error\". I believe that I finished the computations for this model, sent it, and when it was recieved it contaiend an error. Am I understanding the error (client error) correctly?? How should I go about determoning precicely what is going wrong with the CPDN modells and my machine (aka overtemp)??

Look through the README files linked through my signature just below.

---

Backups: Here

Greg, here are the models you\'ve had:

http://climateapps2.oucs.ox.ac.uk/cpdnboinc/results.php?hostid=689423

You\'re currently running one, but none of the others completed. One had a 107 error code, which is often a graphics error on the computer (not necessarily a hardware problem - it could be something you did, like playing games with the model running, or the graphics driver needing an online update). Most of the others you aborted yourself before they\'d finished, or before they\'d started. I suggest that in the Projects tab you set cpdn to No new work to avoid getting unwanted models.

You could download the free trial version of Everest to check the CPU temp.

In the project READMEs, in the one about avoiding model crashes, I\'d recommend item #5 by Mike plus item #1 by Les about how to back up the models. Because if a model does crash, the only way to get it back and continue crunching it is by restoring a backup of the contents of the boinc folder.

The cpdn models are tougher to run than WUs from other projects, if only because they\'re so long. There\'s far more time for glitches.

---

Cpdn news