Please post issues/bugs relating to minirosetta version 1.34 here. Version 1.34 is an attempt to fix several issues from the 1.33 release.

---

<core_client_version>5.10.45</core_client_version>
<![CDATA[
<stderr_txt>
**********************************************************************
Rosetta is going too long. Watchdog is ending the run!
CPU time: 11060.8 seconds. Greater than 3X preferred time: 3600 seconds
**********************************************************************
called boinc_finish

ERROR: unknown atom_name: ASN
ERROR:: Exit from: src/core/chemical/ResidueType.hh line: 928
called boinc_finish

</stderr_txt>
]]>

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



<core_client_version>5.10.45</core_client_version>
<![CDATA[
<stderr_txt>
**********************************************************************
Rosetta is going too long. Watchdog is ending the run!
CPU time: 14322.2 seconds. Greater than 3X preferred time: 3600 seconds
**********************************************************************
called boinc_finish

</stderr_txt>
]]>

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

Both computers are running linux btw. :)

I too have a WU that is at 98% after 8 hours 20 min with 9 min still to go.
Not stuck but as my preferences are set to 6 hours this one is going too long.

---

I too have a WU that is at 98% after 8 hours 20 min with 9 min still to go.
Not stuck but as my preferences are set to 6 hours this one is going too long.

It finally finished after 9.7 hours on a 6 hours preference.
See WU

---

Based on these test, we've identified an issue with on of our protocols taking an unacceptable amount of time to produce a single model, especially for larger proteins. In the next release of the minirosetta application, we're going to put an upper limit on the number of cycles that this protocol can execute so that your workunit time limits aren't exceeded in the future.

Thanks for crunching! I'm going to try and write up something tomorrow about the new scientific improvements we're testing with this latest version of minirosetta.

---

Based on these tests, we've identified an issue with on of our protocols taking an unacceptable amount of time to produce a single model, especially for larger proteins. In the next release of the minirosetta application, we're going to put an upper limit on the number of cycles that this protocol can execute so that your workunit time limits aren't exceeded in the future.

Thanks for crunching! I'm going to try and write up something tomorrow about the new scientific improvements we're testing with this latest version of minirosetta.

---

This WU ended after 1 second:

<core_client_version>6.2.18</core_client_version>
<![CDATA[
<message>
Funzione non corretta. (0x1) - exit code 1 (0x1)
</message>
<stderr_txt>

ERROR: unrecognized aa HOH
ERROR:: Exit from: ....srccoreiopdbfile_data.cc line: 468
called boinc_finish

</stderr_txt>
]]>

I'm going to try and write up something tomorrow about the new scientific improvements we're testing with this latest version of minirosetta.

Thanks, we are always happy to now about scientific improvements. :)

Similarly like mentioned in the Bug Reports for Minirosetta version 1.33 thread, my task fa_dis7-t313_-2008-9-4_4786_8_1 prematurely exited, after 5 sec runtime (Linux host, stock BCC 6.2.4):

<core_client_version>6.2.4</core_client_version>
process exited with code 1 (0x1, -255)

ERROR: Cannot open file /work/tex/projects/cm/benchmark/targets/t313_/native/T0313.pdb
ERROR:: Exit from: src/core/io/pdb/pose_io.cc line: 161
called boinc_finish

James Thompson mentioned that 1.34 should fix this error, apparently it did not (or it was not exactly the same error).

My wingman processed this WU with minirosetta 1.33 and failed with "Maximum CPU time exceeded", the result was reported just yesterday. As this WU is already older, actually from before this note "...I sent out a batch with options for minirosetta version 1.32 rather than version 1.33. The offending workunits have been removed from the queue...", I wonder whether the WU was left on the system by accident and survived the deletion.

Peter

This didn't cause a failure, but it was unusual:

<core_client_version>6.2.18</core_client_version>
<![CDATA[
<stderr_txt>
needs psipred_ss2 to run filters
needs psipred_ss2 to run filters
needs psipred_ss2 to run filters
needs psipred_ss2 to run filters
needs psipred_ss2 to run filters
needs psipred_ss2 to run filters
======================================================
DONE :: 1 starting structures 3254.23 cpu seconds
This process generated 3 decoys from 3 attempts
======================================================

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

</stderr_txt>
]]>

==Mike

---

Don't believe everything you think.

hombench_mtyka_ralph_test1_foldcst_simple_t303___4839_2_0 prematurely exited, after 200 sec runtime (Windows XP host, own modified BCC 6.3.8):

Incorrect function. (0x1) - exit code 1 (0x1)
WARNING: Override of option -out:file:silent sets a different value

ERROR: unknown atom_name: PRO H
ERROR:: Exit from: c:cygwinhomeboincboinc_buildminirosettaminirosetta_1.34minisrccore/chemical/ResidueType.hh line: 928
called boinc_finish

Peter

I got the same warning, but it finished normally:

<core_client_version>6.2.18</core_client_version>
<![CDATA[
<stderr_txt>
WARNING: Override of option -out:file:silent sets a different value
WARNING: Override of option -out:file:silent sets a different value
======================================================
DONE :: 1 starting structures 3817.05 cpu seconds
This process generated 6 decoys from 6 attempts
======================================================

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

</stderr_txt>
]]>

==Mike

---

Don't believe everything you think.

I recieved a similar error message, on this WU

CPU time 20248.67
stderr out

<core_client_version>5.10.21</core_client_version>
<![CDATA[
<stderr_txt>
WARNING: Override of option -out:file:silent sets a different value
WARNING: Override of option -out:file:silent sets a different value
# cpu_run_time_pref: 21600
======================================================
DONE :: 1 starting structures 20248.2 cpu seconds
This process generated 6 decoys from 6 attempts
======================================================

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

</stderr_txt>
<message>
<file_xfer_error>
<file_name>hombench_mtyka_looprelax_test_full_2_looprelax_t326__IGNORE_THE_REST_1S1MA_7_4951_1_0_0</file_name>
<error_code>-161</error_code>
</file_xfer_error>

---

Hello all,

I had a long running WU:
hombench_mtyka_looprelax_test_full_2_looprelax_t326__IGNORE_THE_REST_1HFJA_15_4951_1_0

After 5 hours of Processor Time I switched my computer off. Switching it on let the WU start at about 1 hour.

Runtime: 26778.01 seconds (7.4 hours), preferred runtime: 7200 seconds (2 hours).

Message:Rosetta is going too long. Watchdog is ending the run!
CPU time: 26776 seconds. Greater than 3X preferred time: 7200 seconds

Surprisingly the outcome is Success and 80 credits were granted.

Have a nice day,
Path7.

hombench_mtyka_looprelax_test_full_2_looprelax_t326__IGNORE_THE_REST_1Q7RA_4_4951_1_0 using minirosetta version 134
has been running 16hrs, and still only on model 2. I have a 24hr runtime preference, but this is way too long for 2 models.

---

compute error with this one

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

'Client error' failure on WU 1098636

<core_client_version>6.2.18</core_client_version>
<![CDATA[
<message>
Incorrect function. (0x1) - exit code 1 (0x1)
</message>
<stderr_txt>
Loops::add_loop error -- bad loop definition
begin/cut/end: 134/133/0
ERROR:: Exit from: ....srcprotocolsloopsLoopClass.cc line: 169
called boinc_finish

</stderr_txt>
]]>

---

And again on WU 1098676

---

compute failures for
1099605 (also failed on 2nd computer)
1099603
1099596
973721
1098390
1098367 (passed on 2nd computer)
1098343

A few more 'Computation Errors'

1098726
1098736
1098770
1098778
1098779
1098780
1098781
1098797
1098798

---

This one died with an Access Violation:

1098475

core_client_version>6.2.18</core_client_version>
<![CDATA[
<message>
- exit code -1073741819 (0xc0000005)
</message>
<stderr_txt>
# cpu_run_time_pref: 86400
# cpu_run_time_pref: 86400