Task http://climateapps2.oerc.ox.ac.uk/cpdnboinc/result.php?resultid=15475090 is shown as having timed out no response yet it is still running on the computer. Should I abort or let it try and report? Is this because it passed it's deadline today?

Yes, timed out means it's passed its deadline. It isn't crunching terribly fast, but it must have done about 65%? I think it would be a shame to waste all this crunching and I'm even more convinced when I look at the whole workunit:

http://climateapps2.oerc.ox.ac.uk/cpdnboinc/workunit.php?wuid=8407972

Two models crashed, two aborted. It looks as if your model will be the only finisher here. If you abort it the model will have to be started from scratch on another computer. So please do continue. You'll still receive your credits even though it's overdue.

This is irrelevant to Dave's model, but the top model listed in this WU crashed with a panoply of errors including DYLD. The same thing is happening to all this computer's Hadcm models. Has anyone encountered this before? The error seems specific to Darwin:

http://climateapps2.oerc.ox.ac.uk/cpdnboinc/result.php?resultid=15458108

DYLD Google search

---

Cpdn news

Thanks Mo,

Somehow I didn't save settings for this computer - dual core atom netbook It won't get any more of these models now I have set the computer to be at my work location. I had changed preferences for work and thought the computer was set as work but it wasn't. Quite happy to continue crunching, just wanted to check that it wasn't a waste of time.

Edit:

And next time I have a query about whether to abort a model I will check the others in the workunit.

... This is irrelevant to Dave's model, but the top model listed in this WU crashed with a panoply of errors including DYLD. The same thing is happening to all this computer's Hadcm models. Has anyone encountered this before? The error seems specific to Darwin:

http://climateapps2.oerc.ox.ac.uk/cpdnboinc/result.php?resultid=15458108 ...

I remember investigating this when it first started appearing on my Mac. The consensus appears to be that it is benign and possibly an Apple problem. That user gets so many because the machine is constantly restarted.