I'm having trouble D/L the 5.24 application the link just hangs. A

A complete removal of all files and reinstall of Boinc and the project on each machine appears to fix this problem.

---

This WU does not checkpoint between models. One model needs between 15 to 30 minutes on Athlon 64@2.44 GHz and might well need more than an hour on a slower machine with no checkpoints inbetween. :-(

---

Version 5.24 is up:

1. The symbol store that we put in 5.22 was not properly activated, so we're giving it another shot.

2. We can now use prior predictions for which parts of the chain are buried or exposed to guide the Rosetta search.

3. We can efficiently assemble predefined domains of the protein chain into a whole structure.

This post says version 5.25 is up but it doesn't say where or how to get it. Where can I find that information. Thank you.

5.24 ;) - its an updated rosetta exe so it gets downloaded automatically (note that the BOINC software isn't updated automatically, which is currently at version 5.4.9 - just the rosetta project software)
HTH

---

I have been finding lately that when I check on my computer running version 5.24 I see the following message:

6/24/2006 1:31:16 PM|rosetta@home|Message from server: Your computer has only 266780672 bytes of memory; workunit requires 233219328 more bytes
6/24/2006 1:31:16 PM|rosetta@home|Message from server: No work sent
6/24/2006 1:31:16 PM|rosetta@home|Message from server: (there was work but your computer doesn't have enough memory)
6/24/2006 1:31:16 PM|rosetta@home|No work from project

To reset/restart work I must go to the Projects Tab of BOINC and push the Update button. Most times I will then get another job, sometimes I need to request an Update several times. Is there some kind of setting that I should be adjusting? This kind of behavior shortchanges the project since it requires me to babysit the effort...

Thanks!

---

I have been finding lately that when I check on my computer running version 5.24 I see the following message:

6/24/2006 1:31:16 PM|rosetta@home|Message from server: Your computer has only 266780672 bytes of memory; workunit requires 233219328 more bytes
6/24/2006 1:31:16 PM|rosetta@home|Message from server: No work sent
6/24/2006 1:31:16 PM|rosetta@home|Message from server: (there was work but your computer doesn't have enough memory)
6/24/2006 1:31:16 PM|rosetta@home|No work from project

To reset/restart work I must go to the Projects Tab of BOINC and push the Update button. Most times I will then get another job, sometimes I need to request an Update several times. Is there some kind of setting that I should be adjusting? This kind of behavior shortchanges the project since it requires me to babysit the effort...

Thanks!

I beleive I had a similiar question that was answered by mmciastro. By "pressing" the update button, you are performing a manual update. Welcome to the project! His answer is below.

Results are reported any time the project is contacted for an update. Updates occur at the first of:

1) A result report is due within 24 hours.
2) It has been at least the connect interval since the result completed.
3) (5.4) It is less than the connect interval till the report deadline.
4) Work is needed.
5) A manual update.

---

I have been finding lately that when I check on my computer running version 5.24 I see the following message:

6/24/2006 1:31:16 PM|rosetta@home|Message from server: Your computer has only 266780672 bytes of memory; workunit requires 233219328 more bytes
6/24/2006 1:31:16 PM|rosetta@home|Message from server: No work sent
6/24/2006 1:31:16 PM|rosetta@home|Message from server: (there was work but your computer doesn't have enough memory)
6/24/2006 1:31:16 PM|rosetta@home|No work from project

Please see my earlier comments in this thread about encountering a really big WU. Some CASP7 WUs require lots of memory, so knowing that your PC can't cope, BOINC-server at Rosetta@home won't send it to your BOINC-client/PC. And gives you this message instead.

The Rosetta team (see answers to my question by David Kim and Bin) said they have mixed small and large jobs in the queue, so if you try again ("manual update") you'll probably get a WU that can be handled by your PC.

Ideally ofcourse the BOINC-server should be smarter and noticing your PC can't handle the ultra-big WU, send you one of the regular, smaller jobs. But this feature is not yet available in BOINC server code unfortunately.

---

Best UFO Resources
Wikipedia R@h
How-To: Join Distributed Computing projects that benefit humanity

Ideally ofcourse the BOINC-server should be smarter and noticing your PC can't handle the ultra-big WU, send you one of the regular, smaller jobs. But this feature is not yet available in BOINC server code unfortunately.

Actually it is. There is only enough space in the feeder queue for 1,000 workunits. When the scheduler connects up to the feeder queue to get work it cycles through all 1,000 slots looking for available work. When all 1,000 queue slots are filled up with large jobs that is what the server returns.

Splitting the queue up equally is supported with different applications. If this is really a big problem we could set things up in such a way that the project believes it has more than one application and 50% of the queue is saved for each application.

---

----- Rom
My Blog

I have been finding lately that when I check on my computer running version 5.24 I see the following message:

6/24/2006 1:31:16 PM|rosetta@home|Message from server: Your computer has only 266780672 bytes of memory; workunit requires 233219328 more bytes
6/24/2006 1:31:16 PM|rosetta@home|Message from server: No work sent
6/24/2006 1:31:16 PM|rosetta@home|Message from server: (there was work but your computer doesn't have enough memory)
6/24/2006 1:31:16 PM|rosetta@home|No work from project

Please see my earlier comments in this thread about encountering a really big WU. Some CASP7 WUs require lots of memory, so knowing that your PC can't cope, BOINC-server at Rosetta@home won't send it to your BOINC-client/PC. And gives you this message instead.

The Rosetta team (see answers to my question by David Kim and Bin) said they have mixed small and large jobs in the queue, so if you try again ("manual update") you'll probably get a WU that can be handled by your PC.

Ideally ofcourse the BOINC-server should be smarter and noticing your PC can't handle the ultra-big WU, send you one of the regular, smaller jobs. But this feature is not yet available in BOINC server code unfortunately.

I have one observation to make on this. In the past few days a couple of my machines have received this message about not enough memory. But wait. There's more. A workunit is downloaded anyhow (don't know if it is a high memory one that causes the message to appear or another one in the queue that does not have the high memory requirement.) Then, it also puts a 24 hour delay in before my client will contact the server again. Since I have a queue length of <1 day, if I don't catch it and manually update, I'll run out of work.

May I suggest that the message about not enough memory not be sent unless all work in the server's queue has too high a memory requirement. Also, please don't set a 24 hour backoff if in fact a workunit is downloaded. Maybe 1 hour, but not 24.

Thanks for your consideration.

Charlie

---

-Charlie

Just for information: I see no reduction in the amount of memory used.

---

Just for information: I see no reduction in the amount of memory used.

Actually there are two types of WUs sent out. Small and big ones. The small ones got smaller so that they can be calculated on a machine with only 256 MB RAM. The big ones are still big (or bigger) but are sent out only to hosts with 512 MB RAM and more. Your machine has 1 GB RAM and therfore will reeive big WUs from time to time (those consume up to 300 MB RAM). I already suggested clarifying this in the "Project announcement thread", however obviously the team is to busy to make that announcement.

---

I got an "incorrect funtion error" https://boinc.bakerlab.org/rosetta/result.php?resultid=25399824 First time i get this.

Hi all. Not sure if this is an issue or not. I too noticed that when Rosetta was crunching the processor would go to 100% usage, even when I set Bonic back to "Run based on preferences" for which mine is set to not do work while the computer is in use. I couldn't get Rosetta to stop using all of the processor even after the application was preempted. The only way to do this was to go to Task Manager and stop the rosetta_5.24_wi process.

My next course of action was to try and see if I changed the "Leave applications in memory while preempted?" back to no (I was on yes), but now my work units are coming up with Computational Errors (I thought this was fixed a few releases back).

I use my computer for work as well, so I need to have the work suspended while I use the computer.

Let me know what other information I can send to help out.

Thanks!

---

@Brian Bowles:
That's normal. With the normal settings, BOINC (Rosetta) uses the free CPU cycles. When you are typing a letter in Word, or surfing the internet, it uses less than 5% of your CPU power. The project (Rosetta) uses the free CPU cycles.
This is the way the DC program works.

The application runs at the lowest priority. This means that when another application asks more CPU power (example: you start up graphical software), this application gets this immidiatly. So for example your normal work asks at that moment 75% of your CPU, Rosetta only gets the rest (25%).
A few moments later, your normal work asks 15%, boinc gets 85%.
So Rosetta has the lowest priority: it only gets what isn't being used by other applications.

---

Member of Dutch Power Cows

I'm still seeing the "ghost Accepted Energy" and my protein is not properly centered for this WU:
t309__CASP7_ABRELAX_SAVE_ALL_OUT_BARCODE_nohistag_hom001__683_55900_0

I've only seen it for this specific WU. Apart from that Rosetta is running perfect.

---

@Brian Bowles:
That's normal. With the normal settings, BOINC (Rosetta) uses the free CPU cycles. When you are typing a letter in Word, or surfing the internet, it uses less than 5% of your CPU power. The project (Rosetta) uses the free CPU cycles.
This is the way the DC program works.

The application runs at the lowest priority. This means that when another application asks more CPU power (example: you start up graphical software), this application gets this immidiatly. So for example your normal work asks at that moment 75% of your CPU, Rosetta only gets the rest (25%).
A few moments later, your normal work asks 15%, boinc gets 85%.
So Rosetta has the lowest priority: it only gets what isn't being used by other applications.

Hmm, that's not correct. If the BOINC Manager is set to "Run based on Preferences" and the general preferences have "Do work while computer is in use?" set to "No", then when typing in Word or doing any activity with the mouse/keyboard, all BOINC applications should be preempted and therefore using 0% CPU. After stopping the activity, the general preference "Do work only after computer is idle for" controls when BOINC will 'un-preempt' the applications.

I can confirm this is the correct behavior. If I have Task Manager open, I can see several BOINC project applications on the Process tab, but using 0% CPU. (I have "Leave applications in memory while preempted?" set to "Yes").

(Normally, I force BOINC Manager to "Run Always", but wanted to confirm the behavior.)

---

Hi Brian,

As cureseekers has pointed out letting Rosetta even when you are working on your computer should not decrease performance - at least I can't notice any difference. However if you want to preempt BOINC when you use your computer you should keep in mind, that changing the preferences on the webpages does not change anything on your computer. After every change you need to "Update" the project and verify that the general preference were synced with your local host. Then Rosetta should not use cycles if you set your preference to "No work when computer is in use".

You should "Leave application in memory" on yes. Not only because of the errors (which should be fixed) but because checkpointing occurs still quite infrequently. You may loose over an hour of work if you remove the apps while preempted.

If you really can't get Rosetta to pause try to suspend the Project inside BOINC. If even this does not work I don't know.

P.S.: Your computer is hidden, so it is hard to help you out without knowing the specs and OS.

---

Welcome, Brian Bowles. System Idle Process of zero is a cruncher's goal. A project that runs nicely in the background the way Rosetta does is a dream.

Here's a shot of a gadget available with Windows Vista's sidebar and I keep it on my desktop. I don't want to waste any CPU cycles. :-)



If you have issues with running, post them in a new topic and someone will help you get them sorted.

---

deleted

---

NOT A PROBLEM. but aborted a WU download to temporarily stop BOINC work on this computer. I regret any extra work I've caused! Back soon, I hope.

Great project!

>>> Work Unit # 22005972. <<<
BOINC Manager Message content:
6/26/2006 4:33:13 PM|rosetta@home|Unrecoverable error for result

FRA_t316_CASP7_hom001_7_IGNORE_THE_REST_dect316_7_63_1.pdb_810_82_0

WU download error: couldn't get input files:<file_xfer_error> <file_name>boinc_hom001_aat316_03_05.200_v1_3.gz</file_name> <error_code>-114</error_code> <error_message>user requested transfer abort</error_message></file_xfer_error>)

---

On this computer 2 WU results t312__CASP7_ABINITIO_SAVE_ALL_OUT_BARCODE_hom007__776_27_0 and FRA_t320_CASP7_hom001_4_t320_3_1zunA_IGNORE_THE_REST_912_766_4_0 stopped well short of the 8 hours I have set in my preferences. It appears to be a checkpointing problem since the WUs both aborted because of lack of progress. I thought the remove from memory problem was fixed, but I guess not. Have changed my prefs. back to leave in memory.

---

!!Stupidity should be PAINFUL!!