Posts by DaveSun

1) Message boards : Number crunching : Minirosetta v1.47 bug thread. (Message 58170)
Posted 25 Dec 2008 by DaveSun
Post:
I found this WU stalled after 15 hrs. I suspended the task and then reenabled it later. After it started again it stalled at the same point. I looked at the box and it had a popup saying that it had a C++ runtime error that had asked to be shutdown in an unusual way.

STDERR OUT

<core_client_version>5.10.45</core_client_version>
<![CDATA[
<message>
The system cannot find the path specified. (0x3) - exit code 3 (0x3)
</message>
<stderr_txt>
# cpu_run_time_pref: 86400

</stderr_txt>
]]>



Had This WU this morning with the same error. It ran for 7 hours before stalling. Both are vanilla type. I still have one more of these in progress, it is currently at 21 hours and so far looks good.
2) Message boards : Number crunching : Minirosetta v1.47 bug thread. (Message 58157)
Posted 24 Dec 2008 by DaveSun
Post:
I found this WU stalled after 15 hrs. I suspended the task and then reenabled it later. After it started again it stalled at the same point. I looked at the box and it had a popup saying that it had a C++ runtime error that had asked to be shutdown in an unusual way.

STDERR OUT

<core_client_version>5.10.45</core_client_version>
<![CDATA[
<message>
The system cannot find the path specified. (0x3) - exit code 3 (0x3)
</message>
<stderr_txt>
# cpu_run_time_pref: 86400

</stderr_txt>
]]>

3) Message boards : Number crunching : Minirosetta v1.45 bug thread (Message 57834)
Posted 12 Dec 2008 by DaveSun
Post:
Got a validation error on score12_rlbd_1gvp_IGNORE_THE_REST_DECOY_5473_170 any indication as to what may have caused this?
The task ran for the full time so no indication on my end of a problem.


I took another look at your results, and noticed that it returned 596 decoys. I don't think I've seen a workunit before that returned a 3 digit number of decoys, so perhaps there needs to be a check of whether both minirosetta 1.45 and the workunit validation software can handle that many decoys for one workunit and still do it properly.


I've been running at this setting for several months with out any major troubles and have had several that returned triple digit decoys. I setup to run 1 day after running for less than 10 hours for a long time and having units run what seemed like forever. This way I've not had any taks run over my preference and it works well for my setup. I just don't remember a task that did not validate that had run to completion here before this one.


Then perhaps the limit handled successfuly is higher than 99 decoys per workunit, but not as high as 596.


While that is possible you'd think that if there was a limit it'd be coded into the app and tasks would end once the limit was reached.
4) Message boards : Number crunching : Minirosetta v1.45 bug thread (Message 57821)
Posted 12 Dec 2008 by DaveSun
Post:
Got a validation error on score12_rlbd_1gvp_IGNORE_THE_REST_DECOY_5473_170 any indication as to what may have caused this?
The task ran for the full time so no indication on my end of a problem.


I took another look at your results, and noticed that it returned 596 decoys. I don't think I've seen a workunit before that returned a 3 digit number of decoys, so perhaps there needs to be a check of whether both minirosetta 1.45 and the workunit validation software can handle that many decoys for one workunit and still do it properly.


I've been running at this setting for several months with out any major troubles and have had several that returned triple digit decoys. I setup to run 1 day after running for less than 10 hours for a long time and having units run what seemed like forever. This way I've not had any taks run over my preference and it works well for my setup. I just don't remember a task that did not validate that had run to completion here before this one.
5) Message boards : Number crunching : Minirosetta v1.45 bug thread (Message 57815)
Posted 12 Dec 2008 by DaveSun
Post:
Got a validation error on score12_rlbd_1gvp_IGNORE_THE_REST_DECOY_5473_170 any indication as to what may have caused this?
The task ran for the full time so no indication on my end of a problem.






©2022 University of Washington
https://www.bakerlab.org