There is checkpointing for that type of work unit. It just happens less frequently. It may be that your R@h workunit displayed 0% complete after a restart but there is a bug in the % complete display so I would ignore it and go by the cpu run time. This minor bug is fixed in this ralph version.

---

There is checkpointing for that type of work unit. It just happens less frequently. It may be that your R@h workunit displayed 0% complete after a restart but there is a bug in the % complete display so I would ignore it and go by the cpu run time. This minor bug is fixed in this ralph version.

Yes, I figured there might be a problem with the progress reporting--but even though the WU was on the 12th model or so before, it had now jumped back to the first one, so I knew a checkpoint must have fallen through.

Actually, there is another bug in the current R@h app that doesn't report the model number correctly under certain circumstances. This is fixed in the current ralph app being tested.

---

We're now testing version 5.61. This version has a few science code updates and uses the latest version of the boinc api.

---

Version 5.62 has a fix in the stack size adjuster for macs.

---

Yes, I figured there might be a problem with the progress reporting--but even though the WU was on the 12th model or so before, it had now jumped back to the first one, so I knew a checkpoint must have fallen through.

Work should be preserved after each model. They don't refer to that save as a checkpoint, it is actually the point that the application saves it's work. So you shouldn't lose previously completed models under any circumstance. I've never seen that happen before. The checkpoints are mid-model saves.

---

Client error Compute error
https://ralph.bakerlab.org/result.php?resultid=496726
<core_client_version>5.8.11</core_client_version>
<![CDATA[
<message>
Incorrect function. (0x1) - exit code 1 (0x1)
</message>
<stderr_txt>
# cpu_run_time_pref: 7200
ERROR:: Unable to obtain total_residue & sequence.
start pdb file must be provided.
ERROR:: Exit from: .input_pdb.cc line: 2944

</stderr_txt>
]]>

and

Client error Compute error
https://ralph.bakerlab.org/result.php?resultid=496717
<core_client_version>5.8.15</core_client_version>
<![CDATA[
<message>
Incorrect function. (0x1) - exit code 1 (0x1)
</message>
<stderr_txt>
# cpu_run_time_pref: 7200
ERROR:: Unable to obtain total_residue & sequence.
start pdb file must be provided.
ERROR:: Exit from: .input_pdb.cc line: 2944

</stderr_txt>
]]>

---

I'm still seeing the translucent backbone and dotted sidechains in the graphic as originally reported here. This is under Windows, with version 5.62, a search pairings task

[edit]same with this SYMM_FOLD_AND_DOCK_RELAX_BARCODE task. Also 5.62.

---

Translucent backbone and dotted sidechains on 1bm8__DIVERSE_ABRELAX__NEWRELAXFLAGS_BCFROMFRAGS_20_frags83__1981

Same on Rosetta 5.62 task SEARCH_PAIRINGS_-1hz6A-round2_filters_SAVE_ALL_OUT_1694_1263

---