Ralph has been updated to 5.28. In this version, we added all-atom sidechain display to the screensaver during Rosetta sidechain refinement stage. Also users now can rotate any of the four displayed model on the screen using a mouse. Several new flags have been added to Rosetta too.

ERROR:: Unable to determine sequence length from pdb file

https://ralph.bakerlab.org/result.php?resultid=274727

https://ralph.bakerlab.org/result.php?resultid=274830

https://ralph.bakerlab.org/result.php?resultid=274785

https://ralph.bakerlab.org/result.php?resultid=274908

Anders n

---

I recieved the same error

https://ralph.bakerlab.org/result.php?resultid=275739

Of the ones completed only this workunit failed for me.

Errors for these:

277562
277561

Unhandled Exception Detected

https://ralph.bakerlab.org/result.php?resultid=277671

Unhandled Exception Detected

https://ralph.bakerlab.org/result.php?resultid=277671

This one to.

https://ralph.bakerlab.org/result.php?resultid=276753

Anders n

---

I get in message tab:
2006-10-05 10:44:52|ralph@home|Unrecoverable error for result DOCK_1BQL_unbound_perturb_benchmark_1330_19_0 (Niepoprawna funkcja. (0x1) - exit code 1 (0x1))

and with next WU:

2006-10-05 10:50:53|ralph@home|Unrecoverable error for result DOCK_1JHL_unbound_perturb_benchmark_1330_19_0 (Niepoprawna funkcja. (0x1) - exit code 1 (0x1))

Niepoprawna funkcja = incorrect function

---

Next two WU's with the same:

2006-10-05 10:58:45|ralph@home|Unrecoverable error for result DOCK_1FQ1_unbound_perturb_benchmark_1330_19_0 (Niepoprawna funkcja. (0x1) - exit code 1 (0x1))

2006-10-05 11:04:21|ralph@home|Unrecoverable error for result DOCK_1MEL_unbound_perturb_benchmark_1330_20_0 (Niepoprawna funkcja. (0x1) - exit code 1 (0x1))

---

While displaying graphics for this WU, the first box seems stuck with status message "Try Rotamers", and the graphic in that first box is not refreshing. The Accepted box is jumping around, but no movement in first box.

...while I was typing the above, it went to "Packing" status (step 340,000) and now it seems to be progressing normally and refreshing the graphic.

---

Thanks. This will be very useful for us to track down those hidden bugs in the code.

Next two WU's with the same:

2006-10-05 10:58:45|ralph@home|Unrecoverable error for result DOCK_1FQ1_unbound_perturb_benchmark_1330_19_0 (Niepoprawna funkcja. (0x1) - exit code 1 (0x1))

2006-10-05 11:04:21|ralph@home|Unrecoverable error for result DOCK_1MEL_unbound_perturb_benchmark_1330_20_0 (Niepoprawna funkcja. (0x1) - exit code 1 (0x1))

The current setup in the screensaver graphic is to flash protein sidechains only in "Try Rotamer" and "Packing" stage. "Try Rotamers" is supposed to be very fast each time, and we called them a lot in the code. So people are expected to see protein sidechains flashed on and off most of the time. I think the trajectory is still moving forward as reflected by the moving protein in the accepted box. So it looks like a graphic issue. I am wondering if the more demanding task (showing sidechains on and off quickly) for the graphic is the reason for more frequent "Unhandle Exception" errors we have seen in this updated application. I tried to google what the error code(0x0000005 means when it happens, some people suggest a hardware issue, but no firm answers. Anybody has an idea?

While displaying graphics for this WU, the first box seems stuck with status message "Try Rotamers", and the graphic in that first box is not refreshing. The Accepted box is jumping around, but no movement in first box.

...while I was typing the above, it went to "Packing" status (step 340,000) and now it seems to be progressing normally and refreshing the graphic.

We used to see them a lot before ?Rom? came in and worked thru the code.
I think that was about the time they set-up Ralph for testing. Maybe he can help? I know back then we had to keep Rosetta in-memory and not let it get swapped out to avoid problems also.

---

We used to see them a lot before ?Rom? came in and worked thru the code.
I think that was about the time they set-up Ralph for testing. Maybe he can help? I know back then we had to keep Rosetta in-memory and not let it get swapped out to avoid problems also.

I still have all my computers set to yes "leave in memory".

Anders n

---

I think a part of what we should be testing here is the description of what to expect from the new release and the new graphics. We've had problems before where intentional changes are made... not really described to people, tested on Ralph, rolled out to Rosetta and then people start posted in the "bugs with this release" thread, simply because they don't understand what is happening and that the change is intentional. They don't realize that the science is changing over time and that this is part of the point of the project. etc.

So... could you take a stab at describing the changes to the graphics? And the phases and behavior we should expect to observe? Dr. Baker mentioned in his journal that sidechains would be shown... but that raises more questions then it answers. Because this is all second nature to you, let me explain some questions I can see people will be having:

What are side chains?
Why do they blink on and off?
Why can't I see side chains in the other boxes? Mine must be broken.
Are we doing calculations differently now on the side chains? Or simply illustraiting the calculations we've been doing all along?

I feel these types of questions should be answered HERE on Ralph, so that we can comment on them and ask further questions... have the description revised and improved to address those questions and then use that to post the beginning of the "report problems with v x.yy in this thread", and to then summarize and post to the news on the homepage.

---

I tried to google what the error code(0x0000005 means when it happens, some people suggest a hardware issue, but no firm answers. Anybody has an idea?

I looked at some of the error results that were posted, and I saw for the error code 0xffffffffc0000005, which, if you look at the lower 32 bits is 0xc0000005, which is an access violation. You know, like using a bad pointer, or trying to read or write to memory you don't have.

Hope that helps.

---

Unrecoverable error for result

[list]
*1tit__BOINC_ABRELAX_SAVE_ALL_OUT_truess__1329_17_0 ( - exit code -1073741819 (0xc0000005))
*2vik__BOINC_ABRELAX_SAVE_ALL_OUT_truess__1329_18_0 ( - exit code -1073741819 (0xc0000005))
*2vik__BOINC_ABRELAX_SAVE_ALL_OUT_truess__1329_19_1 ( - exit code -1073741819 (0xc0000005))
[list]

resultid=279007
resultid=277677
resultid=277610
resultid=277591
resultid=277577

2Seems to be a Graphics problem. The graphics just freeze and will not release. The workunit appears to still be running (checked with Task Manager) but can't get rid of graphic screen, have to end process which causes a computation error. If I let it go I get this error
**********************************************************************
Rosetta score is stuck or going too long. Watchdog is ending the run!
Stuck at score 0.966268 for 3600 seconds
**********************************************************************
GZIP SILENT FILE: .xx1c9o.out

The stuck score changes for different failed workunits. Only happening on Windows machine as the Linux machine has no graphics.

So far the above error is on
https://ralph.bakerlab.org/result.php?resultid=279500
https://ralph.bakerlab.org/result.php?resultid=279505
https://ralph.bakerlab.org/result.php?resultid=247849

Also have had Unhandled Exception Record errors
Reason:Access Violation (0xc0000005) at address 0x00759D94 read attempt to address 0x00000011. Had this on https://ralph.bakerlab.org/result.php?resultid=247851
Reason:Access Violation (0xc0000005) at address 0x00759D7D read attempt to address 0x00000011. had this on
https://ralph.bakerlab.org/result.php?resultid=247850

Have had no successful WU's on this batch of Windows WU's.
Have extended the time for the screen saver to come on to 300 minutes from 20 to see if this stops the problem.

---

Thanks for the suggestion, feet1st. I will give it a try here.

What are side chains?
For general knowledge about protein and amino acid, please visit here. I notice that some key terms like "sidechains" are missing and we will update that soon. Here is something I wrote quickly and it definitely needs to be improved.
20 natural amino acids have part of their structures in common and they are connected via peptide-bond linkages to form the topology of a protein structure. The common part is called "backbone". Amino acids differ from each other by its unique chemical group which connects to the C-alpha atom of the backbone and that group is called "side chain".

Why do they blink on and off?
Sidechains are part of protein structures but we only choose to show them on screen during some certain stages when they are being changed by the program.

Why can't I see side chains in the other boxes? Mine must be broken.
So far we only enable the sidechain drawing for the "searching" box.

Are we doing calculations differently now on the side chains? Or simply illustraiting the calculations we've been doing all along?
Sidechain calculation has been part of Rosetta program for a long time, but we only start to have them illustrated on the screen recently.

I understand the above is still far from an adequate description. But I will try my best to provide more information on future updates and this will give people like you guys who volunteer to help testing a better chance to send us feedbacks. Many thanks again.

Well these new Ralph work units are impressive. After creating lots of problems such as freezing my computer when the graphics lock up, it now appears to have stuffed Boinc altogether. During the night Boinc closed down due to the graphics problem. I restarted Boinc which ran for a while then errored out and now Boinc won't run anymore due to Visual C++ runtime errors.
I am now trying to get Boinc running again by either replacing the MSVCP71.dll and MSVCP80.dll files in Boinc or I will just have to reload Boinc.
This is only affecting my Windows Xp machine with the latest updates.

---

I now have 2 problems. I can no longer get BOINC to run on my AMD 4800+ Windows XP machine. Problem started with the Ralph graphic freezes, now all I get is Visual C++ runtime errors when Boinc.exe attempts to run. I have re-installed Boinc and downloaded .net software for the VC libraries but still can't get Boinc to run anymore. Also rebooted a few times, no joy. Help please.

Problem 2, just had 20 WU's download to one of my Linux machines and all 20 Errored out in minutes of downloading with this error:-

ERROR:: Unable to determine sequence length from pdb file

https://ralph.bakerlab.org/workunit.php?wuid=247972, 247980, 247982, 247983, 247993, 247994, 247995, 247996, 247997, 247998, 247999, 248001, 248002, 248004, 248005, 248006, 248051, 248052, 248053, 248054

---