Have the larger ones started coming out? This beast ran for 18 hours and only had one decoy: https://boinc.bakerlab.org/rosetta/result.php?resultid=1156094562

Same here for me, 1 decoy in 14hs

---

I consider it mandatory that in order to distribute such tasks there needs to be a new, separate RAM threshold setting in the project's preference section that requires manual activiation before such tasks are going to be send to the corresponding machines.

It's 2 days that i'm asking to create a possibility to choose...

---

Have the larger ones started coming out? This beast ran for 18 hours and only had one decoy: https://boinc.bakerlab.org/rosetta/result.php?resultid=1156094562

Same here for me, 1 decoy in 14hs

I believe both of those were ended by the watchdog after going 10 hours (36000 seconds) over your selected run times:

BOINC:: CPU time: 65043.4s, 36000s + 28800s[2020- 4-21 8:57: 3:] :: BOINC
Output exists: default.out.gz Size: WARNING! cannot get file size for default.out.gz: could not open file.
-1

BOINC:: CPU time: 50670.5s, 36000s + 14400s[2020- 4-21 10:22:32:] :: BOINC
WARNING! cannot get file size for default.out.gz: could not open file.
Output exists: default.out.gz Size: -1

-Charlie

---

-Charlie

Here I have two tasks that run just shy of the watchdog timeout of 18 hours, without the BOINC:: CPU time message:
https://boinc.bakerlab.org/rosetta/result.php?resultid=1156071420
https://boinc.bakerlab.org/rosetta/result.php?resultid=1156071425

I think that is too close for comfort. When systems are a little bit slower, all that work might still be wasted because of a too short timeout if it fails to generate some useful output...