Hi Steinar

There are a lot of \'blue worlds\' lately. They may be related to the values being used in the recent batches of models.
I wouldn\'t start reinstalling things; it\'s much more likely to be the models.

************

A note for those people who aren\'t aware: the object of the climate models is NOT to run them to the due completion date. It\'s to run them as far as they\'ll go.
The researchers need to know which combinations of values produce a long time stable model and which don\'t, as much as they also want to know the end \'climate\' result.

The object of the project is to improvement climate forecasting, so it\'s just as important to know what works, as it is to know what doesn\'t.

There is a no definitive answer yet to this problem.
A \'blue world\' is what you get initially when starting a model, as the graphics data is not yet available for the display.
Whether this has anything to do with it, I don\'t know.

There is an info thread here, with a link near the bottom to a discussion thread.
This is for the slab models, but the symptoms are often similar for the Coupled Ocean models.

As to re-running from a backup, there\'s only one way to find out. :(
However, the problem may have started from before the time that the backup was made.

Running two models with hyperthreading increases throughput by about 15% on a single processor P4. On dual Xeons with hyperthreading, there doesn\'t appear to be any advantage due to front side bus/memory access/contention problems.

A slower machine can still do useful climate modelling work :

* Try running the \'slab\' model rather than the \'coupled\' model. The slab model has much smaller requirements for CPU time and memory. You can control which you run (via Your Account / Project Preferences / Set HadSM3 to \'ticked\', and HadCM3 to \'unticked\').

Alternatively, you could run the http://www.apsathome.org/ project, which is doing localised atmospheric physics work which will be used to improve climate models in the future. The work units only take a few hours even on older PCs.

Error 1 is mostly associated with shutting down too quickly for the modelling program to close all of it\'s files.
This may be because Windows is closed without first Exiting BOINC, or becuause the power is simply turned off with the program running.
And Vista is worse, because fast turn off is one of it\'s touted features.

The only guaranteed way to save the model is:
(Menu) Suspend BOINC,
Wait until it SAYS \"Suspended\", then
(Menu) Exit from BOINC.

Anything less is \"Russian Roulette\".

Steinar\'s model completed and uploaded perfectly:

http://climateapps2.oucs.ox.ac.uk/cpdnboinc/result.php?resultid=5776940

You could run two models simultaneously on that computer. Or a climate model on one core and a different project on the other. Ther\'s enough memory for 2 models.

Hi Steinar

Yes, the server problem is solved, at least temporarily. So we can enable network activity and allow our files to upload. That should include final 2080 files. But if I were you I\'d make a backup first before uploading the finished model, just in case. Make the backup now, before you let the model finish and before you allow network activity.

There\'s an easy method through my sig link. The README about avoiding model crashes, item #1 by Les.

Congratulations on getting to the end!

Steinar, when you\'ve had plenty of time to see this, if you don\'t mind I\'ll move your post and my reply to a thread about current models, not about Classic. Hope that\'s OK.