1) It might have been complained enough, but please do not add gigantic work unit such as ClimatePrediction in secret next time. Even WCG still respect their user by warning for 'special' project.
2) I don't know why, but Charity Engine Statistic 1.01 is now on (Idle), High Priority 0.00 CPU and is about to be expired en masse one hour from now, even if some of them is already 90%, 80%, 70%. I tried suspending the rest but it just not budging. And why is this statistic thingy is downloading like 20 job at one go and working on all of them in one go. Why not finish it one by one by one?
If this keep happening one after another I might just quit Charity Engine and focus on WCG full time.
Hi Fox, Knight is correct - that sounds like a bug. It's not meant to be doing any more than one Stat task at a time. Something not working right there.
As for climateprediction (or any other WU), there's nothing 'secret' about it as such - CE work units are always chosen by CE, not the users. That's the only way it can work.
If users could pick and choose projects (like normal BOINC), then the platform would not be reliable enough to sell to science and industry - and would therefore have no income for prize draws or charity donations. Can't have one without the other!
@Mark Mca, I understand. But 500 hours? I divide my CPU 50/50 between WCG and CE. 500 hours means 20 days of continous on - which I don't with my PC. Even if divided by 8 hours per day (which is impossible on working day - people is at the office) that's 62 real life day already. And my boinc cannot work on other jobs. This is tantamount to taking my CPU hostage. Instead of playing nice by being less than 12 hours workload, someone is taking it hostage by the moment having cpu access, forced the CPU to only work for it for 62 real life days before passing it back. This is not cool.
You get points all along the way, as the task is going. So even if you can't complete the task you get just as many points as if you had completed smaller tasks that added to however much you got done. So while it may seem silly to have a 500 hour task it is probably mostly for convieniance of Climate prediction, and you are not really effected by the long task times.
I concur with Fable Fox: I've got 40 "statistics 1.02 (idle)" jobs running simultaneously at the moment (along with 3 climateprediction.net and 1 Einstein jobs)!
We are limiting the number of jobs being fed into the system on the server side. However, turns out that the BOINC version in use is not able to support the jobs limits (only versions 6.12 and later are able to), so we have suspended stats application until we can find a suitable solution.
1) It might have been complained enough, but please do not add gigantic work unit such as ClimatePrediction in secret next time. Even WCG still respect their user by warning for 'special' project.
2) I don't know why, but Charity Engine Statistic 1.01 is now on (Idle), High Priority 0.00 CPU and is about to be expired en masse one hour from now, even if some of them is already 90%, 80%, 70%. I tried suspending the rest but it just not budging. And why is this statistic thingy is downloading like 20 job at one go and working on all of them in one go. Why not finish it one by one by one?
If this keep happening one after another I might just quit Charity Engine and focus on WCG full time.
For your 1) see this
2) if i understand you correct you got more than 1 task of the statistic application right? If this is correct then i think it's a bug :)
I just get one statistics task at once.
There is 16 Statististic job currently. And the percentage is 90,70,70,60,60,50,50,50,50,10,0,0,0.
This is why I don't really get it. Why not just complete one at a time? Strange...
Hi Fox, Knight is correct - that sounds like a bug. It's not meant to be doing any more than one Stat task at a time. Something not working right there.
As for climateprediction (or any other WU), there's nothing 'secret' about it as such - CE work units are always chosen by CE, not the users. That's the only way it can work.
If users could pick and choose projects (like normal BOINC), then the platform would not be reliable enough to sell to science and industry - and would therefore have no income for prize draws or charity donations. Can't have one without the other!
@Mark Mca, I understand. But 500 hours? I divide my CPU 50/50 between WCG and CE. 500 hours means 20 days of continous on - which I don't with my PC. Even if divided by 8 hours per day (which is impossible on working day - people is at the office) that's 62 real life day already. And my boinc cannot work on other jobs. This is tantamount to taking my CPU hostage. Instead of playing nice by being less than 12 hours workload, someone is taking it hostage by the moment having cpu access, forced the CPU to only work for it for 62 real life days before passing it back. This is not cool.
And this is my statistic screenshot
You get points all along the way, as the task is going. So even if you can't complete the task you get just as many points as if you had completed smaller tasks that added to however much you got done. So while it may seem silly to have a 500 hour task it is probably mostly for convieniance of Climate prediction, and you are not really effected by the long task times.
I concur with Fable Fox: I've got 40 "statistics 1.02 (idle)" jobs running simultaneously at the moment (along with 3 climateprediction.net and 1 Einstein jobs)!
I think you all use the charity engine client yes? Maybe another charity engine bug? Because i have no problems using Boinc 7.0.28 / 7.0.54.
I'm still on BOINC 6.10.56.
Maybe I'll upgrade to 6.10.58 when I have the time. I'll upgrade to what WCG supports.
okay so nothing more we (the community) can help i'm afraid :/ A dev has to see over this...
We are limiting the number of jobs being fed into the system on the server side. However, turns out that the BOINC version in use is not able to support the jobs limits (only versions 6.12 and later are able to), so we have suspended stats application until we can find a suitable solution.