Anyone know what the status is of Cosmology? Last word was their sever crashed but they where working on it.
That was sometime ago. Nothing since. They still active or retired?

They have been officially down since March 12. I have written them 3 times now asking nicely for a status update, and I saw only a generic message when I tried to bring up their site. The latest I saw was that there was a replacement server on order and was supposed to arrive during their Spring Break. Following that timeline, they would be installing the server this week, but there has been no communication from inside the camp that I know of. I know a few people at RPI. I will see what I can find out.

Ken

I have a wu try to send for a while, better hold it or cancel it ?

I would hold it. BOINC takes care of those kind of issues on it's own.

Besides, if you hold it, as long as BOINC keeps it you are more likely to get credit for it. Otherwise you have to hope for the kindness of admins.

And, if their server has lost it in the crash, then BOINC will take care of that too.

Typically, the best advice for proper use of BOINC is don't mess with it. (Though I know I do.)

COSMO IS BACK UP!!!!!!!!!!!!!!!!!!!!!!

...not really...

Here well, everything's fine, seems to be a new BOINC version on the server, as the layout of the results table has changed:

the new app CAMB2.16 is more resource hungry than v.2.15 in various ways. One is it won't run on 384MB of RAM - I think 512MB may be enough (well that's what it asks for) - so I can't run cosmo on my old boat-anchor. I was going to shut it down for the summer anyway; might try MW if it'll run.

The problem is not the version 2.16, the problem is version 2.16 past the cosmo-restart. If you read in the cosmo-forum, you will find an additional download for win-v2.16. It seems to be, that the project-admin restored an older/unoptimized versions as v2.16.
The crunching times in windows are higher than before and higher in linux, too. I know the crunching times are not equal for win and linux on same host but they should go in the same direction.
If there is nothing changed in the middletime you should have the similar situation like spinhenge but with the difference in os. In cosmo the win-app needs ~25% more time than linux-app and visversa in spinhenge with ~25% more time for linux-app.

[edit]
Got an message from boinc:
Message from server: CAMB needs 476.84 MB RAM but only 379.65 MB is available for use.

I've got one using 652MB of RAM right now. They seriously need to work on their app.