Climate Prediction has taken over control of time sharing from SETI, ROSETTA,& EINSTEIN.

I set each to "100" which should result in a 25% share each. However, that is not what's happening.
Climate Prediction has be running for 9 1/2 hours straight.

Did I do something wrong in set-up? Help?

---

The welfare of the people is the highest law - Cicero

If no one complains, the people must be satisfied.

Climate Prediction has taken over control of time sharing from SETI, ROSETTA,& EINSTEIN.
I set each to "100" which should result in a 25% share each. However, that is not what's happening.
Climate Prediction has be running for 9 1/2 hours straight.
Did I do something wrong in set-up? Help?

No you have a found a flaw in trying to run CP along with other Projects. It just does nto share well. It has to do with CP's deadlines and some units taking a year to process. After the CP unit is finished CP will not get any work and the other projects will get alot.

---

There are a couple of possibilities:

1) CPDN is in deadline trouble.
How much CPU time is remaining for it to process (as estimated by BOINC)?
What are the time_stats (from the client_state.xml time_stats section)?
How many hours to the deadline?

2) Some other tasks were in deadline trouble, and CPDN is getting some makeup time.
What are all of the short_term_debt values?
What are all of the long_term_debt valuse?
Please associate the above with the projects to which they apply.

---

BOINC WIKI

I had the same issue and it turns out that is has to do with the deadline set by CP and the % of time the CPU is crunching for BOINC.

In my case, when I managed to improve the % of time from 22% roughly (which had led to CP monopolizing my pc) to 30% or thereabouts, SETI resumed sending WUs.

---

I had the same issue and it turns out that is has to do with the deadline set by CP and the % of time the CPU is crunching for BOINC.

In my case, when I managed to improve the % of time from 22% roughly (which had led to CP monopolizing my pc) to 30% or thereabouts, SETI resumed sending WUs.

In that case, CPDN would eventually have let S@H get some work in. It might have been a while, but it would have happened.

---

BOINC WIKI

I have had the same issue with the climate prediction work units. I have only received two so far, the first of which failed to complete but the schedule given was for a period of 1 year approximately but my PC could not possibly complete the work sent within that time period. I forced my PC to get SETI@Home work units by stopping the CP work unit temporarily. These work units commonly had an earlier complete by date so ran first (the PC being overloaded). However as soon as the CP unit was allowed to re-start it took over again and wouldn't allow ant time for SETI@home once more. I believe that my attempts to enable some SETI@ home work to complete caused the failure.I have now received a second CP unit, with adeadline again of about 1 year, causing exactly the same issue. I have left it to run but it is now clear that it will take soemthing like 2.5 years to complete and, without taking the same steps as before, will prevent me getting any further SETI@Home work units. I am considering stopping the CP work altogether. Does any one have any suggestions to get around this issue before I go ahead with this solution?

---

I have had the same issue with the climate prediction work units. I have only received two so far, the first of which failed to complete but the schedule given was for a period of 1 year approximately but my PC could not possibly complete the work sent within that time period. I forced my PC to get SETI@Home work units by stopping the CP work unit temporarily. These work units commonly had an earlier complete by date so ran first (the PC being overloaded). However as soon as the CP unit was allowed to re-start it took over again and wouldn't allow ant time for SETI@home once more. I believe that my attempts to enable some SETI@ home work to complete caused the failure.I have now received a second CP unit, with adeadline again of about 1 year, causing exactly the same issue. I have left it to run but it is now clear that it will take soemthing like 2.5 years to complete and, without taking the same steps as before, will prevent me getting any further SETI@Home work units. I am considering stopping the CP work altogether. Does any one have any suggestions to get around this issue before I go ahead with this solution?

I see a Celeron 1.3G in your account. The CPDN recommendation is for at least a 1.6G system with 500Meg of RAM. The Celeron chip also has some other limitation that may be detrimental to its efficient processing of the work. I believe that your system may be somewhat underpowered to share CPDN with other projects and be able to finish by deadline. It would probably need to run it 24/7 to be successful.

Just the opinion of someone who had to drop CPDN on a comparable Duron system. On the other hand, crunching 24/7, I was able to add several other worthwhile projects instead. I still contribute to CPDN with my newer C2D.

---

Boinc V7.2.42
Win7 i5 3.33G 4GB, GTX470