Rosetta@Home has been updated to version 3.24. If you encounter any problems, please let us know. Thank you for your continued support.

Among other things, this release includes support for symmetry in the hybrid protocol for comparative modeling.

I have some problemes with upload of results
I think this is in relation with the distribution of the new app (high network traffic ?!)

A network monitoring at the rah_status.php like at primegrid´s server_status.php should be helpfully...

Same problem here.Work unit\'s won\'t upload.

---

Upload is very slow but it is working for me (\"Retry Now\").

---

Seems to be uploading okay now!

---

Thanks for your patience. We bog down a bit when new versions of the application are distributed. If you continue to experience slow uploads, please let us know.

I noticed that the 3.24 app did not have the execute bit set after download (in openSUSE 11.4, Boinc 7.0.18), which caused all WUs to fail. I have fixed this manually, but that should not be necessary of course...

Rosetta@Home has been updated to version 3.24. If you encounter any problems, please let us know. Thank you for your continued support.

Among other things, this release includes support for symmetry in the hybrid protocol for comparative modeling.

plus remind new people the update is automatic and there is nothing they have to download ..........

Please post details about correcting the execute bit. I built a new machine over the weekend for R@H and the WU\'s all failed. As a consequence BOINC/R@H will only give me 8 new work units per day, and those are completed in three hours... a lot of processing time is being wasted. Also wasted were many hours testing the computer trying to figure out why it couldn\'t get a WU done correctly.

pvh: I noticed that the 3.24 app did not have the execute bit set after download (in openSUSE 11.4, Boinc 7.0.18), which caused all WUs to fail.

There was nothing different done on our end, with respect to the executable bit, from any of the previous versions, so it\'s likely it\'s a Boinc 7 issue.

Note that the Boinc 7.0 series is currently still a development version, and people have reported a number of issues with Boinc 7 and R@h. As it\'s development code, we\'re really not supporting Boinc 7 at this point.

In Memory of Kimsey M Fowler Sr: I built a new machine over the weekend for R@H and the WU\'s all failed.

If you\'re referring to this machine, it looks like the issue is not a faulty execute bit, but rather the successful completion/Exit status 0/Client Error/missing application version issue that others have experienced. (See http://boinc.bakerlab.org/forum_thread.php?id=5914#72425) We\'re looking into it, but the best lead so far is that it\'s related to GPU settings. If it won\'t impact computing for other projects, try turning off GPU usage for that machine. (Rosetta@home itself does not use GPUs, although other boinc projects you\'re running might.)

If you\'re referring to this machine, it looks like the issue is not a faulty execute bit, but rather the successful completion/Exit status 0/Client Error/missing application version issue that others have experienced. (See http://boinc.bakerlab.org/forum_thread.php?id=5914#72425) We\'re looking into it, but the best lead so far is that it\'s related to GPU settings. If it won\'t impact computing for other projects, try turning off GPU usage for that machine. (Rosetta@home itself does not use GPUs, although other boinc projects you\'re running might.)

Thanks for taking time to respond. Yes, that is the correct machine. I set the GPU Activity button to \"Suspend GPU\", and the last few days WU\'s appear to be completing normally. I wonder if, like myself, others having experienced a similar problem are running F@H on one or more GPU\'s and R@H on the CPU? I\'m doing this on a second nearly identical machine (computer ID 1498519) without any problems, so I\'m thinking that \"Suspend GPU\" is the ticket.

I am still dealing with the problem of being limited to eight new WU\'s per day. From poking around various forums it looks like BOINC may take several days to recognize that I can perform additional work units in the allotted time. I\'m experimenting with a suggestion to accelerate that process by setting my preferences differently to indicate a connection to the internet every six days and request two days of work at the time even though the machine is always connected.

I set the GPU Activity button to \"Suspend GPU\", and the last few days WU\'s appear to be completing normally.

Interesting ... But I\'m wondering why you think they\'re completing normally, as according to the task list for that computer (http://boinc.bakerlab.org/rosetta/results.php?hostid=1525425) everything for the past couple of days (at least of from 16 Mar 15:00 UTC on back) seems to be still suffering from Client Errors.

I set the GPU Activity button to \"Suspend GPU\", and the last few days WU\'s appear to be completing normally.

Interesting ... But I\'m wondering why you think they\'re completing normally, as according to the task list for that computer (http://boinc.bakerlab.org/rosetta/results.php?hostid=1525425) everything for the past couple of days (at least of from 16 Mar 15:00 UTC on back) seems to be still suffering from Client Errors.

Yep, I see that now. There were no reports of errors when the jobs completed and I saw credit was awarded. \'I assumed\'.... shameful.

I\'m going to uninstall and reinstall BOINC for a fresh attempt.

After updating to version 3.24
- Tasks are considered from two to seven hours (set to 3:00)
- Granted credit was less than 6 times
- Compute errors
http://boinc.bakerlab.org/rosetta/results.php?userid=402480
Restarting the project has not helped...

Recently, \"Granted credit\" for Mac OS X clients is relatively low compared to one for Windows client.

Client #1 Mac OS X(10.7.3)
- Measured floating point speed 2840.51 million ops/sec
- Measured integer speed 4754.19 million ops/sec
- CPU Time (sec) 21,972.88
- Claimed Credit 96.57
- Granted Credit 14.61
- http://boinc.bakerlab.org/rosetta/workunit.php?wuid=448711523

Client #2 Windows 7
- Measured floating point speed 2271.54 million ops/sec
- Measured integer speed 6904.26 million ops/sec
- CPU Time (sec) 21,434.99
- Claimed Credit 113.82
- Granted Credit 92.04
- http://boinc.bakerlab.org/rosetta/workunit.php?wuid=448711904

Your first example returned 7 decoys, that\'s a bit over 2 credits per decoy. The second example returned 44 decoys that comes to about the same number of credits per decoy. So the credit-granting is the same (2.09 credit/decoy). To reliably compare performance between the apps the other variables have to be the same. Same CPU, same memory configuration. It could be the 2 hosts are not similar enough to compare them too each other.

---

transient, I have the same thing happens in OS X 10.7.3
http://boinc.bakerlab.org/rosetta/results.php?userid=402480
see what it was two days ago - all calculated results fell about six times

I am also experiencing the same results with MacOS X 10.6.8. All results have dropped to 20-25% of what they were for jobs completed prior to March 16.

transient, I have the same thing happens in OS X 10.7.3
http://boinc.bakerlab.org/rosetta/results.php?userid=402480
see what it was two days ago - all calculated results fell about six times

Comparing the same type of task on the same type of cpu, one a mac (yours) and one a windows 7 computer. I found these the mac: http://boinc.bakerlab.org/rosetta/show_host_detail.php?hostid=1372047, windows: http://boinc.bakerlab.org/rosetta/show_host_detail.php?hostid=1336570, I looked up these tasks:

MAC:
======================================================
DONE :: 1 starting structures 10241 cpu seconds
This process generated 6 decoys from 6 attempts
======================================================
BOINC :: WS_max 4.51269e+08

BOINC :: Watchdog shutting down...
BOINC :: BOINC support services shutting down cleanly ...
called boinc_finish

</stderr_txt>
]]>

Validate state Valid
Claimed credit 61.2023891428566
Granted credit 12.5052457755095

Windows:
======================================================
DONE :: 1 starting structures 10707.2 cpu seconds
This process generated 28 decoys from 28 attempts
======================================================
BOINC :: WS_max 3.97976e+008

BOINC :: Watchdog shutting down...
BOINC :: BOINC support services shutting down cleanly ...
called boinc_finish

</stderr_txt>
]]>

Validate state Valid
Claimed credit 66.716736771631
Granted credit 58.6144700013407


Looking at these 2 tasks, provided it is valid to compare them, performance on the mac is less.

---

It looks like the performance of the Rosetta@home application dropped on Macs (we believe all Macs) with 3.24. We\'re aware of the issue and looking into ways of remedying it.

Note that the low performance is the direct cause of the variable runtimes. The R@h client will try to always produce at least decoy. If execution slows down enough that a job takes 7 hours to produce the first decoy, that workunit will run for 7 hours, even if your runtime setting is 3 hours. But once that first decoy is produced, the client will only start on subsequent decoys if the estimated runtime falls under the run-time limit. So if the first decoy takes 2 hours to complete and your runtime is set for 3 hours, the client will stop early, rather than run for 4 hours.