Hello, shipmates,

Experienced a minor technical problem – seemed one project work units running on my present BOINC 6.6.36 version prevented the thingamajig from downloading jobs from another. The start and happy end of the story, for your kind information:

http://setiathome.berkeley.edu/forum_thread.php?id=54764&nowrap=true#920946
http://setiathome.berkeley.edu/forum_thread.php?id=54764&nowrap=true#921044

I am glad to be able to tell, that at the moment my BOINC is happily munching both projects toils again.

Regards

PK

It's possible that your last CPDN Model(s) ran in priority mode to meet the "deadline", keeping other Projects from getting time. BOINC keeps track and will "pay back" what is owed to other projects before allowing CPDN to run again.

Note that CPDN ignores deadlines but boinc does not.

---

"We have met the enemy and he is us." -- Pogo
Greetings from coastal Washington state, the scenic US Pacific Northwest.

It's possible that your last CPDN Model(s) ran in priority mode to meet the "deadline", keeping other Projects from getting time.

Yes, could be of course, but my both present CPDN work units have their "report deadline" in early July 2010 only. I have now one of those running, the other one suspended, and a SETI job is being computed by the other processor. So basicly this is as I want it to be, only that a bit more monitoring is required than usually. I may have to make sure personally, that new work units are able to be downloaded from time to time.

A different thing is, that after latest updates my BOINC application seems to overestimate running times remarkably. It thinks e.g. a new CPDN HADAM3P 6.06 toil would take about 1800 hours, when about 500 is nearer to the final outcome.

Regards

PK

It's a minor, but irritating, bug in BOINC v6.6.36 and thereabouts. v6.6.31 and before don't have it: v6.6.38 and (not yet compiled) v6.6.39 have a fix, but other problems come with it.

It's a minor, but irritating, bug in BOINC v6.6.36 and thereabouts. v6.6.31 and before don't have it: v6.6.38 and (not yet compiled) v6.6.39 have a fix, but other problems come with it.

You think that CPDN overestimates, I recently downloaded an AstroPulse from seti@home. This is the first one of those that I have ever run. I was shocked to see a time to completion of 522 hours! I wasn’t looking for another long project, just a short break from ClimatePrediction models. I needn’t have worried. The AstroPulse finished in only 62 hours.

---

Play around with the percentages allocated to both the projects. Start with 50/50 then adjust.
Regards
Masud.

It's possible that your last CPDN Model(s) ran in priority mode to meet the "deadline", keeping other Projects from getting time.

Yes, could be of course, but my both present CPDN work units have their "report deadline" in early July 2010 only. I have now one of those running, the other one suspended, and a SETI job is being computed by the other processor. So basicly this is as I want it to be, only that a bit more monitoring is required than usually. I may have to make sure personally, that new work units are able to be downloaded from time to time.

A different thing is, that after latest updates my BOINC application seems to overestimate running times remarkably. It thinks e.g. a new CPDN HADAM3P 6.06 toil would take about 1800 hours, when about 500 is nearer to the final outcome.

Regards

PK

Hi Pasi Karonen

You said: 'I have now one of those running, the other one suspended, and a SETI job is being computed by the other processor.' If a task is suspended you cannot download new work from that project. This is a rule for all recent versions of Boinc. Before trying to download new work from CPDN be sure that you have no CPDN models suspended.

---

Cpdn news

Hello, shipmates!

Before trying to download new work from CPDN be sure that you have no CPDN models suspended.

Yes, sure. But the thing is, as follows.
* One HADAM3P running, almost 30 % progress, says about 850 hours to completion; I believe will be much less eventually.
* Another HADAM3P suspended at 6,8 %. I shall allow this to run again after the first one is completed. Also, the Climate Prediction project is presently told not to get new tasks for me; it will be let to do so again when this second job is finished.
* At the same time SETI work units are now again able to be downloaded, ran and reported with no problem; this was not the case with this BOINC version 6.6.36, if I allowed two HADAM3Ps to run simultaneously.

So, a bit more monitoring is required than usually, but no big deal. Hopefully later BOINC versions indeed will have a fix to the bug on the bottom of this, as Richard Haselgrove said earlier in this thread.

Regards

PK

Members who want more work ready to crunch in advance may be able to fetch it by increasing their additional work buffer.

Boinc Manager > Advanced > Preferences > Network usage tab > manually edit the additional work buffer, maximum 10.00 days > click OK.

But computers which also do tasks with short deadlines from other projects should keep the work buffer low to avoid fetching too much work and missing deadlines.

---

Cpdn news