Thanks for continuing posts of ralph errors.
This will probably be our last development release
on ralph before putting the app on Rosetta@home. We really need to know if anything is fundamentally wrong with this one!

---

Thanks for continuing posts of ralph errors.
This will probably be our last development release
on ralph before putting the app on Rosetta@home. We really need to know if anything is fundamentally wrong with this one!

Then put up a few more WUs! Why so few testing?

---

Haven't seen this error before, but here it is: WU 84203

<core_client_version>5.3.6</core_client_version>
<message>Incorrect function. (0x1) - exit code 1 (0x1)
</message>
<stderr_txt>
# random seed: 3884798
# cpu_run_time_pref: 10800
# cpu_run_time_pref: 10800
ERROR:: Exit at: .dock_structure.cc line:401

---

My one 5.04 wu, and one 5.03 wu for that matter, both finished successfully. However I'm wondering why they both finished in under 2 hours when my preference is set to 16 hours and earlier wu's did run for that time.

wu 95168, 5.04
wu 94408, 5.03

My one 5.04 wu, and one 5.03 wu for that matter, both finished successfully. However I'm wondering why they both finished in under 2 hours when my preference is set to 16 hours and earlier wu's did run for that time.

wu 95168, 5.04
wu 94408, 5.03

Did you "Update" with BOINC Manager after changing your preferences on the web site? If not, the preferences will not be changed until the client contacts the server. Pardon me if this response is too obvious, but you never know.... :)

---

My one 5.04 wu, and one 5.03 wu for that matter, both finished successfully. However I'm wondering why they both finished in under 2 hours when my preference is set to 16 hours and earlier wu's did run for that time.

wu 95168, 5.04
wu 94408, 5.03

Did you "Update" with BOINC Manager after changing your preferences on the web site? If not, the preferences will not be changed until the client contacts the server. Pardon me if this response is too obvious, but you never know.... :)

No problem, appreciate the thought (however I did update). I should have said in my original post that the result files show the preference set to 16 hours.

Thanks for continuing posts of ralph errors.
This will probably be our last development release
on ralph before putting the app on Rosetta@home. We really need to know if anything is fundamentally wrong with this one!

Some work for testing, please! I've only got about 2 WU's per host. One WU (resultid=95455) has crached...

---

I have same, first 2 WUs completed in 1hr 10min. But my updated preference to Ralph indicates I'd prefer 16hrs as well.

---

For those jobs, we had it set to make a maximum of 10 predictions -- "hit it and quit it". That was mainly so that we'd have some results back quickly. Thanks for asking for more work! I'm sending out more jobs now, asking for 50 predictions.

Things looks OK for ralph 5.04 so far. We're still getting the occasional file transfer error when the watchdog aborts, but that's not the end of the world. Looking into it.

I have same, first 2 WUs completed in 1hr 10min. But my updated preference to Ralph indicates I'd prefer 16hrs as well.

---

Quess I should have put this here:

I've not had hung WUs before, but watchdog stepped in and killed one after about 1hr 10min runtime, with a 16hr preference. My other WU (same PC) seemed to end normally, but again, after about 1hr 10min rather than the 16hr preference. 2 more crunching now, during the day, so I can watch them run.

Does the watchdog just compare two points in time? Is it possible the score was jumping all around for an hour, and just happened to be exactly the same at that instant in time an hour later? Or is it looking at the step I'm on too?

---

For those jobs, we had it set to make a maximum of 10 predictions -- "hit it and quit it". That was mainly so that we'd have some results back quickly. I'm sending out more jobs now, asking for 50 predictions.

I have my Preferences set to 8 hours, which I guess is OK if the workunit is set to report at a set time anyway. Or maybe you mean you have overwritten the time preferences, and if it takes longer than 8 hours to get 50 predictions, then that is what it will take? Might be prudent to make this clarification, so people don't get too stressed if their time preferences are ignored for now. :)

Thanks!

---

Got this error on This WU running the BOINC CC 5.4.2. The "Target CPU Run Time" was set on 2 hours. Changed it to 4 hours, will see how the next WU goes when I get it.

Result ID 95456
Name CHECK_600_DOG_7486h002_dec08_1.pdb_410_2_1
Workunit 83413
Created 25 Apr 2006 14:06:59 UTC
Sent 25 Apr 2006 14:07:19 UTC
Received 25 Apr 2006 21:07:58 UTC
Server state Over
Outcome Client error
Client state Computing
Exit status 0 (0x0)
Computer ID 65
Report deadline 9 May 2006 14:07:19 UTC
CPU time 4949.296875
stderr out <core_client_version>5.4.2</core_client_version>
<stderr_txt>
# random seed: 3885562
# cpu_run_time_pref: 7200
**********************************************************************
Rosetta score is stuck or going too long. Watchdog is killing the run!
Stuck at score -128.786 for 600 seconds
**********************************************************************

</stderr_txt>
<message><file_xfer_error>
<file_name>CHECK_600_DOG_7486h002_dec08_1.pdb_410_2_1_0</file_name>
<error_code>-161</error_code>
</file_xfer_error>

</message>


Validate state Invalid
Claimed credit 11.0121627676007
Granted credit 0
application version 5.04

---

For 1 days, this result is 100% done, but does not upload at all

I run several projects on ths pc, and keep work in ram.

When boinc switches for ralph@home ... boincview shows cpu eficciency 0.0000

After about an hour, boinc switches for next project ...
then cpu efficiency is restored to 0.9809

And this cycle, is repeating for 1 days .. (I believe for ever, if I do nothing)
https://ralph.bakerlab.org/result.php?resultid=94996

I am aborting this result now, manually

---

Click signature for global team stats

Exit status 0 (0x0) - Watchdog is killing the run!, no credits granted
https://ralph.bakerlab.org/result.php?resultid=95121
ps: I have the debugger installed on this pc

---

Click signature for global team stats

I believe that the credits should be granted in this case !
*No error in my part.

I believe that the credits should be granted in this case !
*No error in my part.

From a link off the RALPH Home page -

RALPH@home is the official alpha test project for Rosetta@home. New application versions, work units, and updates in general will be tested here before being used for production. The goal for RALPH@home is to improve Rosetta@home.

Please consider the following before deciding to join:

Since this project is a testing environment, applications and work units may be unstable at times.
Credits and other competitive statistics do not mean anything in this test project. Credits may be lost due to instabilities and may be reset at any time for testing.
There will not be a continual flow of work units. Work units will be issued only when necessary for testing.
We urge participants to not abort work units to help with testing.
Please set the resource share low for this project compared to other production projects in your RALPH@home preferences.

Emphisis added for clarity

Regards
Phil

I believe that the credits should be granted in this case !
*No error in my part.

You are right Carlos.

You should have gotten credit for the WU.

Somthing for the developers to look at before it reaches Rosetta.

Anders n

---

wu 85055 was killed by the watchdog; credits were granted.

cpu_run_time_pref: 57600
Watchdog is killing the run! Stuck at score 2.48287 for 3600 seconds

Not sure if this is the right place to report this, but I am seeing errors on the graphics. Strands are broken - I see as many as six ends. Graphic is moving partially outside the box on the search and accepted graphics. No problems yet running the code, though.

---

A new watchdog kill.

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

switching tasks involved?

Anders n

---