Please post bugs/issues regarding version 5.98 here.

6/26/2008 3:31:54 PM|rosetta@home|Starting t434_1_NMRREF_1_t434_1_T0434_2QPWA_2JV0_hybridIGNORE_THE_REST_truncated_4104_1_1
6/26/2008 3:31:54 PM|rosetta@home|Starting task t434_1_NMRREF_1_t434_1_T0434_2QPWA_2JV0_hybridIGNORE_THE_REST_truncated_4104_1_1 using rosetta_beta version 598
6/26/2008 4:16:56 PM|rosetta@home|Computation for task t434_1_NMRREF_1_t434_1_T0434_2QPWA_2JV0_hybridIGNORE_THE_REST_truncated_4104_1_1 finished
6/26/2008 4:16:56 PM|rosetta@home|Output file t434_1_NMRREF_1_t434_1_T0434_2QPWA_2JV0_hybridIGNORE_THE_REST_truncated_4104_1_1_0 for task t434_1_NMRREF_1_t434_1_T0434_2QPWA_2JV0_hybridIGNORE_THE_REST_truncated_4104_1_1 absent

---

https://boinc.bakerlab.org/rosetta/workunit.php?wuid=158620863

https://boinc.bakerlab.org/rosetta/workunit.php?wuid=158616469

https://boinc.bakerlab.org/rosetta/workunit.php?wuid=158605953

All with compute errors in the first minute.

---

Compute error,
https://boinc.bakerlab.org/rosetta/result.php?resultid=173774049

This one fell over on both hosts, same error.

https://boinc.bakerlab.org/rosetta/workunit.php?wuid=158612212

Output file FRA_t449_CASP8_MANUAL_1_IGNORE_THE_RESTt449_1_ttxxxxT0449_1CHIM_0001_0001_0001_4126_3627_1_0 for task absent

<core_client_version>5.10.30</core_client_version>
<![CDATA[
<message>
Incorrect function. (0x1) - exit code 1 (0x1)
</message>
<stderr_txt>
# cpu_run_time_pref: 21600
# random seed: 2404847
ERROR:: Exit from: .loop_relax.cc line: 1745

</stderr_txt>

pete.

---

Another compute error,
https://boinc.bakerlab.org/rosetta/result.php?resultid=173797309

---

Compute error...

---

This one fell over on both hosts, same error.

https://boinc.bakerlab.org/rosetta/workunit.php?wuid=158612212

Output file FRA_t449_CASP8_MANUAL_1_IGNORE_THE_RESTt449_1_ttxxxxT0449_1CHIM_0001_0001_0001_4126_3627_1_0 for task absent

<core_client_version>5.10.30</core_client_version>
<![CDATA[
<message>
Incorrect function. (0x1) - exit code 1 (0x1)
</message>
<stderr_txt>
# cpu_run_time_pref: 21600
# random seed: 2404847
ERROR:: Exit from: .loop_relax.cc line: 1745

</stderr_txt>

pete.

same here

Again errors as 5.96 :(

https://boinc.bakerlab.org/rosetta/result.php?resultid=173787198
https://boinc.bakerlab.org/rosetta/result.php?resultid=173807571
https://boinc.bakerlab.org/rosetta/result.php?resultid=173821223

---

174088567
174032945
174000755

First and last validate errors after the full job, (10,000+ seconds), the middle one after just a few seconds, (Exit from: .loop_relax.cc line: 1745).

---

Wave upon wave of demented avengers march cheerfully out of obscurity into the dream.

Please post bugs/issues regarding version 5.98 here.

rosetta@home Rosetta Beta 5.96 1405_CaspB_IUMPAB_Type2_RES81to19... 03:51:35 00.000% ...06/28/... Running high prio...

---

This WU did 1247 decoys, then was marked "invalid" for no apparent reason:

FRA_t449_CASP8_AUTO_1SNZ_1L7J_2CIQ_1_IGNORE_THE_RESTt449_1_ttttaaT0449_1L7JA_10_0001_0001_0002_4134_634

This little bugger has been running all weekend. 47hrs on a 24hr preference.
FRA_t449_CASP8_MANUAL_1_IGNORE_THE_RESTt449_1_ttxxxxT0449_1CHIM_0001_0001_0001_4142_1913 Yet it is still getting CPU time, and the step number is still incrementing. It says it is on model 151.

---

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/

Here is a very fast error running version 5.98 on Windows XP: 174404220. It looks like it failed on at least one other host in the same manner.

---

Bizzare problem with this WU; had an 'unhandled exception error' after about approx 50 mins CPU run time, with a lenthy Std_Out: 157316144

<core_client_version>5.10.45</core_client_version>
<![CDATA[
<message>
- exit code -1073741819 (0xc0000005)
</message>
<stderr_txt>
# cpu_run_time_pref: 10800
# random seed: 2747207


Unhandled Exception Detected...

- Unhandled Exception Record -
Reason: Access Violation (0xc0000005) at address 0x00B3C947 read attempt to address 0x000000A4

Engaging BOINC Windows Runtime Debugger...


Otherwise no other errors so far with 5.98 on both of my hosts (knocks on wood ;p)

https://boinc.bakerlab.org/rosetta/workunit.php?wuid=158648907

Two validate errors after full crunch.

Rosetta needs to think about how to apply credit when the problems are obviously of project/WU source.

Jim

---

Crunch with friends - TeAm Anandtech

https://boinc.bakerlab.org/rosetta/workunit.php?wuid=158648907

Two validate errors after full crunch.

Rosetta needs to think about how to apply credit when the problems are obviously of project/WU source.

Jim

Credit is applied to these as claimed - it doesn't show on the task's main page but does if you hit the Task ID link on the left.

HTH
Danny

---

WU FRA_t449_CASP8_MANUAL_1_IGNORE_THE_RESTt449_1_ttxxxxT0449_1CHIM_0001_0001_0001_4142_3294_1 using rosetta_beta version 598

Original estimated run time about 6 CPU Hrs

Still Runing at 10:10:00 CPU

Progress 98.386% and incrementing 0.001 about every 25 CPU secs

To Completion 00:09:55 (no change last 30 CPU minutes

At current % increase will take another 11+ CPU Hrs, or if Prog% is calculated from time done as % of Time done+To completion then will run forever.

BTW Currently Model 22 Step 47795

WU FRA_t449_CASP8_MANUAL_1_IGNORE_THE_RESTt449_1_ttxxxxT0449_1CHIM_0001_0001_0001_4142_3294_1 using rosetta_beta version 598

Original estimated run time about 6 CPU Hrs

Still Runing at 10:10:00 CPU

Progress 98.386% and incrementing 0.001 about every 25 CPU secs

To Completion 00:09:55 (no change last 30 CPU minutes

At current % increase will take another 11+ CPU Hrs, or if Prog% is calculated from time done as % of Time done+To completion then will run forever.

BTW Currently Model 22 Step 47795

the % complete and time to completion aren't linear - they're estimates, so don't worry about them if Rosetta's CPU time is increasing in task manager.

Danny

---

Danny is correct about the time estimates.

But the t449 I reported earlier never did finish. I let it run for 68 hours before aborting it (my runtime preference is 24hrs so I'm sure the watchdog would have discovered it after 4x that preference, but I didn't want to waste the time).

My aborted task didn't seem to send the normal data in to the server. 150 presumably good models lost. So, I would suggest (if you have the patience) to exit and restart BOINC 5 times. Each time leaving it run for long enough to get itself initialized and running the problem task. Rosetta will then detect no progress after 4 or 5 restarts and more cleanly cut it off and send it in.

I'm also wishing I had saved a copy of all the slots directories. Again, if you have the time, after your first exit of BOINC, I would save all the directories under your BOINC installation path with /slots on the end of the path, and EMail it to the rosettamod.

---

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/