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.

Certainly. Do you know where I can upload the files?

---

Certainly. Do you know where I can upload the files?

I found these files at the url below

http://climateapps2.oucs.ox.ac.uk/cpdnboinc/download/sulphur_4.21_i686-pc-linux-gnu
http://climateapps2.oucs.ox.ac.uk/cpdnboinc/download/sulphur_4.21_i686-pc-linux-gnu.so
http://climateapps2.oucs.ox.ac.uk/cpdnboinc/download/sulphur_data_4.21_i686-pc-linux-gnu.zip
http://climateapps2.oucs.ox.ac.uk/cpdnboinc/download/sulphur_um_4.21_i686-pc-linux-gnu.zip
http://climateapps2.oucs.ox.ac.uk/cpdnboinc/download/sulphur_se_4.21_i686-pc-linux-gnu.zip

but we\'ll need the file_signature information for those mentioned in the xml file.

I found these files at the url below

http://climateapps2.oucs.ox.ac.uk/cpdnboinc/download/sulphur_4.21_i686-pc-linux-gnu
http://climateapps2.oucs.ox.ac.uk/cpdnboinc/download/sulphur_4.21_i686-pc-linux-gnu.so
http://climateapps2.oucs.ox.ac.uk/cpdnboinc/download/sulphur_data_4.21_i686-pc-linux-gnu.zip
http://climateapps2.oucs.ox.ac.uk/cpdnboinc/download/sulphur_um_4.21_i686-pc-linux-gnu.zip

but we\'ll need the file_signature information for those mentioned in the xml file.

You also need sulphur_se_4.21_i686-pc-linux-gnu.zip

The signature is:

(file_info)
(name)sulphur_4.21_i686-pc-linux-gnu(/name)
(nbytes)4259364.000000(/nbytes)
(max_nbytes)0.000000(/max_nbytes)
(status)1(/status)
(executable/)
(signature_required/)
(file_signature)
765a986e0c67b95cab0da0605be738abdeaa9791abeb36b20e596ff344044513
ed1a2cfa86bec894646149fda4b5da473b56d8d6b60acbb435fa46aa43787e2b
cf7e7d3e0cf0e8e00338257752e9f1e67363d3597d6b26414122d0cb89a7a6ce
0d3c6fb8b82ce3144a5f3762872eace49007cecbd04f7439d4891a7dca32a07b
.
(/file_signature)
(url)http://climateapps2.oucs.ox.ac.uk/cpdnboinc/download/sulphur_4.21_i686-pc-linux-gnu(/url)
(/file_info)
(file_info)
(name)sulphur_4.21_i686-pc-linux-gnu.so(/name)
(nbytes)8281400.000000(/nbytes)
(max_nbytes)0.000000(/max_nbytes)
(status)1(/status)
(executable/)
(signature_required/)
(file_signature)
91f02c74278d1d3da254aaf0d33d3141ace1ea503ace9f52e3e8ea9436985048
c8d05408802b1c232303929358442549cb817f3b49cb59b8fc24ae7479d1ae31
d50102c97c4048faeb0424fad737790d95268885a627204c18a6537be8f6de83
eb4f2daa311af2512a1d94a2a332d9932a4af6a319d26358109ccec9f996f805
.
(/file_signature)
(url)http://climateapps2.oucs.ox.ac.uk/cpdnboinc/download/sulphur_4.21_i686-pc-linux-gnu.so(/url)
(/file_info)
(file_info)
(name)sulphur_data_4.21_i686-pc-linux-gnu.zip(/name)
(nbytes)24047629.000000(/nbytes)
(max_nbytes)0.000000(/max_nbytes)
(status)1(/status)
(signature_required/)
(file_signature)
91e4e438a17842b73758007a92c4ffea63b9ade84211fd34038689b7b672eee8
d80e2a6c146465ce74c6aad4edab79c539a9dfddecbbc9ed93385bcfe8c533cd
3d2ff4f996e980262cfb5cd523b7acdec0352d19b46545407a3a67de6edf2c6e
8b63a505d5e2a9b89a2e6f6167a49cac0d0b04ce93772e25802807b0dc997dc1
.
(/file_signature)
(url)http://climateapps2.oucs.ox.ac.uk/cpdnboinc/download/sulphur_data_4.21_i686-pc-linux-gnu.zip(/url)
(/file_info)
(file_info)
(name)sulphur_um_4.21_i686-pc-linux-gnu.zip(/name)
(nbytes)4563697.000000(/nbytes)
(max_nbytes)0.000000(/max_nbytes)
(status)1(/status)
(signature_required/)
(file_signature)
44040e3d2012e67ece56d07b9ec38910d5e903eeb0093bbda9a7cc7047c00a8d
7f8ec82724b0fc1f2cc3f66f274c5bfe90f10397b18972e71af3111ff025037f
50b5dbad2ea09bd16505c580aace29a846bcb110b547bbd173cb6c8aefad5a4a
e6dd8c33064330452ecaaa42aad23c7daceb2234b5221637454391829091338f
.
(/file_signature)
(url)http://climateapps2.oucs.ox.ac.uk/cpdnboinc/download/sulphur_um_4.21_i686-pc-linux-gnu.zip(/url)
(/file_info)
(file_info)
(name)sulphur_se_4.21_i686-pc-linux-gnu.zip(/name)
(nbytes)5639582.000000(/nbytes)
(max_nbytes)0.000000(/max_nbytes)
(status)1(/status)
(signature_required/)
(file_signature)
09a841d58f5030fbd709c9027d05789a4ea1b2d9e2b3f5d9f5bb51c99128a918
a1c4e005635588ad44301705c947678ee3022053eb9661bd07d759ea9a9fe979
ef154e7b1041ec7bb51f96ed1482a35f8c5591eb9b78da92401b7c14600d40a4
e615c73c55843b82d3c17a3a3a4e2f5b09e61333aeaff1e79a3a4c3bf75d43e0
.
(/file_signature)
(url)http://climateapps2.oucs.ox.ac.uk/cpdnboinc/download/sulphur_se_4.21_i686-pc-linux-gnu.zip(/url)
(/file_info)

And you also have to add the (app_version):

(app_version)
(app_name)sulphur_cycle(/app_name)
(version_num)421(/version_num)
(file_ref)
(file_name)sulphur_4.21_i686-pc-linux-gnu(/file_name)
(main_program/)
(/file_ref)
(file_ref)
(file_name)sulphur_4.21_i686-pc-linux-gnu.so(/file_name)
(open_name)sulphur_4.21_i686-pc-linux-gnu.so(/open_name)
(/file_ref)
(file_ref)
(file_name)sulphur_data_4.21_i686-pc-linux-gnu.zip(/file_name)
(open_name)sulphur_data_4.21_i686-pc-linux-gnu.zip(/open_name)
(/file_ref)
(file_ref)
(file_name)sulphur_um_4.21_i686-pc-linux-gnu.zip(/file_name)
(open_name)sulphur_um_4.21_i686-pc-linux-gnu.zip(/open_name)
(/file_ref)
(file_ref)
(file_name)sulphur_se_4.21_i686-pc-linux-gnu.zip(/file_name)
(open_name)sulphur_se_4.21_i686-pc-linux-gnu.zip(/open_name)
(/file_ref)
(/app_version)


Written in anger: BBCode tags suck!

Anyway, I have an HTML page with the downgrade instructions and the XML changes to the client_state.xml file listed above.

---

OK. Try:

Instructions to downgrade from sulphur 4.23 to 4.21 on Linux

---

I\'ll give it a try later today. Thanks for the effort and I\'ll let you know how it goes.

LS Diseño

Thanks. Worked great. There were some complications because I had both 4.22 and 4.23 entries in my client_state file, but I figured it out. Running much faster than the 4.22 executables that were crunching before.

LS Diseño

Thanks. Worked great. There were some complications because I had both 4.22 and 4.23 entries in my client_state file, but I figured it out. Running much faster than the 4.22 executables that were crunching before.

Glad it worked for you! I also have a host with 4.22, and I left it at that as it was crunching through phase 3 already.

---

I have tried the method you descibed, but each time CPDN downloads new workunit it switches back to 4.23 ?? What am I missing ??

Please help.

LS Diseño

Thanks. Worked great. There were some complications because I had both 4.22 and 4.23 entries in my client_state file, but I figured it out. Running much faster than the 4.22 executables that were crunching before.

Glad it worked for you! I also have a host with 4.22, and I left it at that as it was crunching through phase 3 already.

---

I have tried the method you descibed, but each time CPDN downloads new workunit it switches back to 4.23 ?? What am I missing ??

What error messages do you get in the Messages tab when this occurs?

I was overwriting the 4.23 sections rather than adding in new 4.21 sections in client_state.xml. I have got it running, thanks for reply.

But now the gui is not updating cpu time and progress. The client app is running and showing no errors, but I have noticed that when boinc cycles to another app and suspends cpdn, it rewinds to beginning of last saved (archived boinc copy)timestep when staring cpdn again, as if not doing data dumps and checkpoints??

hlp appreciated

I have tried the method you descibed, but each time CPDN downloads new workunit it switches back to 4.23 ?? What am I missing ??

What error messages do you get in the Messages tab when this occurs?

---

sorry Geophi, my last post was incorrect, the checkpoints and timestaps are working correctly, just gui not updating. I use a windows 2K box for monitoring other boxes running boinc, and the CPU time, progress and to completion tabs are not updating ??

regrds

I was overwriting the 4.23 sections rather than adding in new 4.21 sections in client_state.xml. I have got it running, thanks for reply.

But now the gui is not updating cpu time and progress. The client app is running and showing no errors, but I have noticed that when boinc cycles to another app and suspends cpdn, it rewinds to beginning of last saved (archived boinc copy)timestep when staring cpdn again, as if not doing data dumps and checkpoints??

hlp appreciated

I have tried the method you descibed, but each time CPDN downloads new workunit it switches back to 4.23 ?? What am I missing ??

What error messages do you get in the Messages tab when this occurs?

---

to add to this...

it seems that 4.21 has problem running on redhat 8.0 gcc v3.22, as I get sulphur-4.21__um zombie on start of process and wu gets stuck starting up model. I have tried using sulphur-4.23_um and the wu runs (so far 15 hours). But this stops the gui updating (I think this is client_state.xml not being udpated periodically ?)

Is there a problem with the libraries with 4.21 and RH8.0 ?

I just wish I could get some wu done on linux with sulphur !!!! 8((

regards

Steve R

[quote]sorry Geophi, my last post was incorrect, the checkpoints and timestaps are working correctly, just gui not updating. I use a windows 2K box for monitoring other boxes running boinc, and the CPU time, progress and to completion tabs are not updating ??

regrds

[quote]

---

(I was away on travel and I did not read the posts above until now)

I believe the problem with the GUI not updating might be related to the warning messages 4.21 produces upon startup when trying to set pointers to the shared memory segment it allocates. At first, I thought the only side effect would be lack of graphics, but I think the GUI also uses this memory segment to interchange information with the boinc client. As I do not use the GUI much because I find is faster editing the client_state.xml file, I had not realized of this problem.

On the other hand, my experience is that the client seems to be crunching workunits fine on Red Hat Linux (so Fedora should be all right too), and MEPIS. I have no direct experience with other distributions of Linux besides Knoppix, which seems to be all right too. However, what I have noticed odd behaviours of other CPDN applications in the past. For example, the hadcm3 spinup application produces a lot of zombi processes when running on Fedora, something that does not happen on other Linux distributions.

Sorry I cannot be of more help.

---

Sorrow days are over, 2006-03-13 16:17:48 [climateprediction.net] Started download of hadcm3trans_5.08_i686-pc-linux-gnu
:)

Sorrow days are over, 2006-03-13 16:17:48 [climateprediction.net] Started download of hadcm3trans_5.08_i686-pc-linux-gnu
:)

What exactly does this mean? Is it ok to run climate on linux once again? Is there official word? Was there any official notice that the linux client was hosed other than having to rummage through the forums?

---

Sorrow days are over, 2006-03-13 16:17:48 [climateprediction.net] Started download of hadcm3trans_5.08_i686-pc-linux-gnu
:)

What exactly does this mean? Is it ok to run climate on linux once again? Is there official word? Was there any official notice that the linux client was hosed other than having to rummage through the forums?

I am not sure. I re-enabled climateprediction downloads, and it downloaded me three homework assignments. Two were hadsm3lb 5.08 (these may be good ones) and one sulfur_cycle 4.23 (that I think is a bad one).

---

It\'s the new HadCM3L Coupled Model Experiment and it popped up in the Applications tab on Monday.
Been running fine on my Fedora boxen for a couple of weeks as a beta and in the BBC project.

I\'m just wondering, is this

sulphur_ilto_000868092 - PH 1 TS 0103459 A - 26/11/1816 09:30 - H:M:S=0078:58:21 AVG= 2.75 DLT= 1.88
2006-04-22 23:23:00 [climateprediction.net] Unrecoverable error for result sulphur_ilto_000868092_0 (process got signal 11)

peculiar behavior also caused by the unstable version 4.23? I\'ve never had a full run due to a) memory problmems and b) trying to debug in wine whilst CPDN was running, but with this one I\'ve gotten farther than before. This one never rewound though, just out of the blue a signal 11, bam!

---