Geophi, yes I know and I\'m looking forward to the coupled model, fast and stable as it seems.
Anyway one box here was shut down since LHC has no units, a second one restarted a Spinup model, the third is chewing on an old slab model, a fourth went to GIMPS, and this one does sulphur and the coupled beta.

isn\'t it possible to run manually the old hadsm project on these pcs?

Scarf
Which old Project?
If you mean slab models, they finished last year.

I\'ve e-mailed Tolu about it and he knows there\'s a problem. When it will be fixed...given the upcoming coupled launch...??

I have a 4.22 one that is still working, but all the 4.23 ones fail after a little while (as is well known, now).

But should we have boincmgr boycott all new climateprediction work units for a while? Is there any benefit for computing part way through phase 1 and bombing? I know I get credit for doing that, but if it does no good, I would rather use the processor time for something else.

---

If you can finish phase 1 and upload it, then it will be very useful, as it contains extra data that the researchers need for starting the TCM here.

If you can finish phase 1 and upload it, then it will be very useful, as it contains extra data that the researchers need for starting the TCM here.

Nope: most recent failure got up only to phase 1 timestep 108020 in work unit sulphur_hbbt_100807833_0 a.k.a. Result # 1792194

---

You could always set CPDN to get no new work and connect to the BBC coupled model project (http://bbc.cpdn.org) instead.

---

"The ultimate test of a moral society is the kind of world that it leaves to its children." - Dietrich Bonhoeffer

You could always set CPDN to get no new work and connect to the BBC coupled model project (http://bbc.cpdn.org) instead.

OK. I hope someone posts here when climateprediction starts sending out work units that I can process on Linux when the time comes.

---

You could always set CPDN to get no new work and connect to the BBC coupled model project (http://bbc.cpdn.org) instead.

Incidentally, as far as I can see the BBC one, which starts at 1920, is in fact the beginning of the new whizzy exciting next-gen experiment 2 which various people have been working their systems so hard doing the spin-up for- it\'s not a cut down super-stable cpdn as I have seen suggested in 1 or 2 threads (not this one), it\'s the future, man! (Please, if I\'m wrong about this someone let me know).

As I have 1 windows box on normal cpdn and one linux one now on bbc.cpdn, they\'re technically on 2 different projects which offends my tidy mind, but at least they\'re both working now!

Chris

---

cjrt
You got it. Welcome to the future.
Coming soon to this site as well. (As soon as the dust settles.)

If you\'re a multi-project person, the way to run the BBC project is to use a normal 5.2.13 version of BOINC and just attach to the BBC project, the same as any other.

This new model type starts at the end of 1920, just before New Years.

Scarf
Which old Project?
If you mean slab models, they finished last year.

yes I mean the slab models, hadsm was the client name for that as far as I know.
I guess i have to wait for a new sulphur client or the start of the new model for regular cpdn.

cjrt
If you\'re a multi-project person, the way to run the BBC project is to use a normal 5.2.13 version of BOINC and just attach to the BBC project, the same as any other.

Yes, that\'s what I did, but I\'ve still ended up with one (windows) system running cpdn and one (linux) system attached to the bbc.cpdn.org website- they appear to me to be running as totally separate projects, though both under boinc. Did I do it wrong?

Chris

---

They are indeed, totally separate projects, with totally separate listings for credits on stats sites.

I have decided to process the sulphur workunits using 4.21 until the coupled model becomes available or a new/old version of the linux application is released as 4.24+. I do not know if I will be able to upload the result, but I can always revert to 4.23 for doing that.

Lets see what happens...

---

I have decided to process the sulphur workunits using 4.21 until the coupled model becomes available or a new/old version of the linux application is released as 4.24+. I do not know if I will be able to upload the result, but I can always revert to 4.23 for doing that.

I wish there was an easy way to revert to 4.21.

I just dropped the 4.21 executables in the climateprediction.net directory, and edited the client_state.xml file to add the (file_info) and (app_version) bits. Then I changed the version of the application in each of the (workunits). When I restarted the client, it complained about a couple of shared memory symbols (I believe is because of the graphics, which I do not use) but it continue running using 4.21 all right.

So far, the clients I modified have trickled, but I have not reach the point yet where I have to upload a file.

Edit: Changed parenthesis () for angle brackets as these do not show.

---

To follow up with this issue, I remember the team re-released hadsm3 (slab) 4.04 as 4.13 when 4.10, 4.11 and 4.12 were found unstable, much to my disappointment because I never had problems with them and 4.1x were much faster on Athlon 64 processors.

Do you know if re-relasing sulphur 4.21 as 4.24 involves a lot of work? Does it require to regenerate the workunits which are queued to be processed? The answer is probably yes :-(

---

They are indeed, totally separate projects, with totally separate listings for credits on stats sites.

Thanks for the info Les, good thing I\'m not it it for huge credit scores then:-) (Never going to happen with an Athlon XP 3200 & an XP 2600 anyway!)

Chris

---

I have decided to process the sulphur workunits using 4.21 until the coupled model becomes available or a new/old version of the linux application is released as 4.24+. I do not know if I will be able to upload the result, but I can always revert to 4.23 for doing that.

Lets see what happens...

It seems to work. I just uploaded the intermediate xx...xxxx_1.zip file at the end of phase 1.

---

I have decided to process the sulphur workunits using 4.21 until the coupled model becomes available or a new/old version of the linux application is released as 4.24+. I do not know if I will be able to upload the result, but I can always revert to 4.23 for doing that.

Lets see what happens...

It seems to work. I just uploaded the intermediate xx...xxxx_1.zip file at the end of phase 1.

In order for others who are very persistent to be able to do this, they would need access to the 4.21 executables, zip files, and the associated changes in the snippets of code in the xml files. I know Honza wrote something on upgrading here so I imagine one can attempt to follow that (with appropriate changes) to downgrade, but the files are needed (downloadable) and the file signatures.