Rosetta 5.34 has a few new features to allow us to test more accurate energy functions and more interesting variations in the protein's bond geometry. Let us know if you see any problems -- especially if they are reproducible!

---

Hi all i just got this with the new app.

https://boinc.bakerlab.org/rosetta/result.php?resultid=43809672

Access Violation (0xc0000005) at address 0x007DADE2 read attempt to address 0x337F02F4

Hope it helps someone.

---

My system is constantly freezing up with the new versions. It started more frequently from version 5.32 I don't mind giving unused processing time to Rosetta but it must not make my system unstable / unrelaible. Can somebody help me with this. If there is not a sollution i am considering the removal of the rosetta programm.

greetings Edwin

---

My system is constantly freezing up with the new versions. It started more frequently from version 5.32 I don't mind giving unused processing time to Rosetta but it must not make my system unstable / unrelaible. Can somebody help me with this. If there is not a sollution i am considering the removal of the rosetta programm.

greetings Edwin

Edwin, You've given us nothing to work with. What errors are you seeing? What error codes are you seeing? You're computers are hidden so we can't even look at the work you've done.

This thread is for reporting issues. Please create a thread of your own and give us some details.

thanks

tony

Hello there. Well my system does not show up any errors with the new version, but it has become very slow. Even after 3.5 hrs of crunching, the progress column shows only about 1.5%. Is this normal for this newer version? The earlier version actually completed WUs in that same time period.

---

Hello there. Well my system does not show up any errors with the new version, but it has become very slow. Even after 3.5 hrs of crunching, the progress column shows only about 1.5%. Is this normal for this newer version? The earlier version actually completed WUs in that same time period.

Same symptoms here for the following WU: 38667731

Stuck at 1.595 percent at about ~3h of crunching, with time to complete rising 1-2 secs for every 1-2 secs crunched

WinXP Pro with all relevant updates
P4 3GHz HT
512 MB RAM
Apps left in memory
App switch time 120 min

---

Stuck at 1.595 percent at about ~3h of crunching, with time to complete rising 1-2 secs for every 1-2 secs crunched

That symptom in and of itself is not a problem (See QA item here). The % completed is always jumpy. Check the graphic and see what is shown for the model number and step number you are on. Are the steps advancing?

The likely outcome here is that once your first model completes, it will reflect 100% complete and report the completed task. The fact that it takes more then your runtime preference doesn't change the need to complete at least one model. One model takes much longer for some tasks then for others.

---

Add this signature to your EMail:
Running Microsoft's "System Idle Process" will never help cure cancer, AIDS nor Alzheimer's. But running Rosetta@home just might!
https://boinc.bakerlab.org/rosetta/

All done! Complete in 3h 1min.

---

Edwin I'd suggest you exit BOINC (File -> Exit), and run your computer for a day without BOINC. See if it still locks up. Most likely it will. At that point, you can dig in to what's left running that is causing the conflicts on your machine.

If you'd like to learn what "hidden" computers means, or show us the system details of the machine you are running, here is a QA item on the subject.

---

Add this signature to your EMail:
Running Microsoft's "System Idle Process" will never help cure cancer, AIDS nor Alzheimer's. But running Rosetta@home just might!
https://boinc.bakerlab.org/rosetta/

All done! Complete in 3h 1min.

Great! Abhijeet, I believe the two of your were on the same WU type. And his machine is more then twice the speed of yours, and your may take 7 or 8 hours of runtime to complete. It will show the 1.xx% the whole time, and then finish out, so don't let it worry you unless it's still running for more then say 10hrs. Also, Rosetta has a "watch dog" watching to make sure that the task doesn't get stuck, so it will kill it for you if things aren't progressing normally.

---

Add this signature to your EMail:
Running Microsoft's "System Idle Process" will never help cure cancer, AIDS nor Alzheimer's. But running Rosetta@home just might!
https://boinc.bakerlab.org/rosetta/

Completed first two WU's OK running Mandrake Linux. Giving XP a rest for a week to see if any errors happen in linux. It could be a problem with my XP (Something Corrupted).

---

After 5.32 started causing one of my PCs to 100% error out, I tried re-installing BOINC and Rosetta. However, this continued, even through 5.34. I noticed a valid WU slip through when I was using my computer, which led me to disable the screen saver. Ever since then it's been back to normal. Anyone having a 100% error out rate should change their screen saver to something else to try their luck.

---

My problems didn't start until 5.32. Suddenly, my system goes from almost error free crunching to a variety of errors from read access violations to watch dog shutdowns to solid freezes.

I tried Linux (dual boot) for a while. the first three crunched perfectly. The next thing I know I get a WU halted at 100%, my cpu fan slows to idle and the WU will not upload. I've heard of this happening before.

It is quite unlikely that a hardware failure such as a memory address would go bad just as we upgrade to 5.32 and equally as unlikely that a bad memory addr would cause such a variety of errors. Why would this not happen under linux? I had memory 70% full just to see.

I hope 5.34 goes better.

---

I don't know if this is a Rosetta or Boinc problem but i changed

my run time from 8hrs to 10hrs and have updated 3 times since.

And Boinc has downloaded 2 W.U.'s and runtimes have not changed and are

still showing 8hrs when the first one started and it is going down as it

should the but other is still showing 8hr WHY.

Any ideas, Thanks.

---

Peter
BOINC uses the runtime of the last task to estimate the runtime of the next... in the case of Rosetta it's not always a valid assumption. So, it will show an estimated runtime of your old runtime preference until it has crunched a couple of tasks and reported them back. Then it will catch on. Once you've updated to the project, your next task (even if already in progress) should then run until your longer runtime preference.

---

Add this signature to your EMail:
Running Microsoft's "System Idle Process" will never help cure cancer, AIDS nor Alzheimer's. But running Rosetta@home just might!
https://boinc.bakerlab.org/rosetta/

My run times are now MUCH longer (~10 hours vs. ~2 hours) and progress saves are VERY infrequent (i.e., holds at 1.0000% almost to the end) so that on a switch to other projects sometimes work is lost and resets to basically start over.

Unless this is corrected soon, I will stop processing rosetta@home work units until it changes.

---

My run times are now MUCH longer (~10 hours vs. ~2 hours) and progress saves are VERY infrequent (i.e., holds at 1.0000% almost to the end) so that on a switch to other projects sometimes work is lost and resets to basically start over.

Unless this is corrected soon, I will stop processing rosetta@home work units until it changes.

See this thread. Was it an FRA 2rio? if so, it's every bit as useful as any other work you do.

My crunch time under 5.34 remains at 8 hours. My last comleted WU ran for almost nine hours. I usually average 75 granted credits. Now I only get 48 credits. So now I'm rather confused.

D-3000 2.8Gz P4 1GB 333MHz DDR-2 Ram

---

---

Like Keith, my granted credits are also much lower than they used to be. Any ideas?

---