Rocco,

Since you are reading this thread, I have a question that I can not find an answer to. After shutting down an overclocking program I still have problems processing CASP9 tasks. The majority of them crash, but my wingmen can process the majority of my crashes without any problem.

What is going on? Also the tasks with RB03 were having troubles on my system.

Rocco,

Since you are reading this thread, I have a question that I can not find an answer to. After shutting down an overclocking program I still have problems processing CASP9 tasks. The majority of them crash, but my wingmen can process the majority of my crashes without any problem.

What is going on? Also the tasks with RB03 were having troubles on my system.

My understanding is that there is an edge case on some of the runs with the very new hybridize protocol (which are mainly being sent out as CASP9 and rb_ runs) which result in numerical instability and range errors in calculations for a substantial fraction of workunits for particular protein systems. The crashes were happening somewhat randomly, so it makes sense that the next person on the same workunit could complete it fine.

The issue should hopefully be fixed in the new version of Rosetta@home we are currently testing on Ralph@home.

Rocco,

Since you are reading this thread, I have a question that I can not find an answer to. After shutting down an overclocking program I still have problems processing CASP9 tasks. The majority of them crash, but my wingmen can process the majority of my crashes without any problem.

What is going on? Also the tasks with RB03 were having troubles on my system.

My understanding is that there is an edge case on some of the runs with the very new hybridize protocol (which are mainly being sent out as CASP9 and rb_ runs) which result in numerical instability and range errors in calculations for a substantial fraction of workunits for particular protein systems. The crashes were happening somewhat randomly, so it makes sense that the next person on the same workunit could complete it fine.

The issue should hopefully be fixed in the new version of Rosetta@home we are currently testing on Ralph@home.

ok, thanks.
You talking about version 3.26 that is out now?

You talking about version 3.26 that is out now?

Right. 3.26 should hopefully fix most of the CASP9/rb workunit-related issues.

Hi.

Got two more with errors first one ran for 47min & did the 99 the other ran for 9sec then erred.

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

sh3_d310_design_010_relax_SAVE_ALL_OUT_46196_233_0

cpu_run_time_pref: 14400
======================================================
DONE :: 99 starting structures 2840.33 cpu seconds
This process generated 99 decoys from 99 attempts
======================================================
BOINC :: WS_max 0

BOINC :: Watchdog shutting down...
BOINC :: BOINC support services shutting down cleanly ...
called boinc_finish

</stderr_txt>
]]>

Validate state Invalid
==========================================================

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

ab_11_29__optpps_T5311_optpps_03_09_35686_254232_0

Setting up checkpointing ...
Setting up graphics native ...
EFPCWLVEEFVVAEECSPCSNFRAKTTPECGPTGYVEKITCSSSKRNEFKSCRSALME
can not find a residue type that matches the residue PRO_p:pro_hydroxylated_case1at position 3

ERROR: core::util::switch_to_residue_type_set fails

ERROR:: Exit from: src/core/util/SwitchResidueTypeSet.cc line: 143
BOINC:: Error reading and gzipping output datafile: default.out
called boinc_finish

</stderr_txt>
]]>

---