All hadam3p WU's that I have received during the past week or so have shown an estimated run time betweem 500 hrs and 1200 hrs with a 'due date' approximately 3 mo hence. The WU's run for several days with little or no decrease in remaining estimated run time, resulting in the WU running at high priority and blicking any other project from running on single core machines. Some have eventually settled down after a few days and start showing a systematic decrease in remaining run time, but others continued to run at high priority for many days until I finally aborted them. I have therefore suspended the project on my single core machines and only allow it to run on my three multicore machines (under two different user IDs) which can still run other projects while the climate model is running at high priority). Just thought someone might like to know...

As I understand it, the Boinc time estimation algorithm works better the more models the PC has run to completion. So the more models you let run, the better will be the initial estimate.

During the course of a model run, Boinc seems to stick with its original estimate much longer than we humans do. In my experience it doesn't get really accurate till about 90% completed, or even later. There's nothing we can do about this.

So it's a case of just letting Boinc do its thing, if you still want to contribute. In the long run, things will work out. (That is, after finishing the CPDN model, the PC will spend its time with other projects, to work off its "time deficit".)

Oh and yes, the CPDN models do take weeks (or months!) to run. That's normal.

Cheers.

Oh and yes, the CPDN models do take weeks (or months!) to run. That's normal.

And while it's running at high priority on a single core machine, nothing else gets done until one of the other WU's gets near its 'due date'. The problem would be resolved if the due date (of the HADAM3P WU's) was made much longer. Previous ClimatePrediction WU's typically had a due date about one year in the future -- in which case the run time estimate was always << less than the time until the due date.

EDIT: I just noticed that the offending WU's are HADCM3N's rather than HADAM3P's -- guess this is the wrong thread... :-[

---

The problem with long "due dates", is that people treated this as "The project's not in a hurry to get any results".

Except that each of the research groups do want results fairly quickly, as the next lot of work is dependent on what's currently running.

And with the tight deadline for completion of the RAPIT project, (it may even be past it, due to problems getting out the bugs at the start of the year), there's just no time to "be nice" to single core/multi project crunchers.

Welcome to the New Look cpdn.

---

Backups: Here

And with the tight deadline for completion of the RAPIT project, (it may even be past it, due to problems getting out the bugs at the start of the year), there's just no time to "be nice" to single core/multi project crunchers.


If that is the project's attitude, then I'll just donate my puny little computers' time elsewhere... :-(

---

And with the tight deadline for completion of the RAPIT project, (it may even be past it, due to problems getting out the bugs at the start of the year), there's just no time to "be nice" to single core/multi project crunchers.


If that is the project's attitude, then I'll just donate my puny little computers' time elsewhere... :-(

It isn't the project's attitude. CPDN models are usually a pretty relaxed affair, with results continuing to be accepted beyond any reasonable deadline. However, as Les says, the RAPIT sub-project is different - they do have a more constrained timeline. If that's a problem then it is always possible to deselect the HADCM3N models from your project preferences and select another model type.

I take the use of CPDN by other research groups as a credit to the project team and also to the prodigious efforts of the volunteers. It shouldn't be a surprise if different teams have different objectives - and we volunteers may need to adjust our contributions accordingly.

If that's a problem then it is always possible to deselect the HADCM3N models from your project preferences and select another model type.

Good point -- I'll deselect HADCM3N. But not much else seems to be available lately...

---

Good point -- I'll deselect HADCM3N. But not much else seems to be available lately.

Hadam3p are still being produced in limited batches. They seem to be released at irregular intervals. The problem is that they go fast. Its is not like in the past when slab models were available in seemingly endless numbers. If you keep connected 24/7 you should get 1 or 2 in a few days. Just make sure that your work buffer is set for 10 days.

---