I don't know what your settings are but I'm getting nearly 100% valid tasks here on my both Windows and Linux pc;s.

Me too. Send more betas.

Some Robetta tasks - non-Beta - sneaking through atm.
Hardly any tbh, but not quite nothing

---

I don't know what your settings are but I'm getting nearly 100% valid tasks here on my both Windows and Linux pc;s.

Me too. Send more betas.

Some Robetta tasks - non-Beta - sneaking through atm.
Hardly any tbh, but not quite nothing

Sneaking a few new8v Beta tasks now but similarly hard to come by

---

I think that the 6.xx branch of code makes the same things as the 4.xx plus other things.
But it's in beta since the beginning of April.
Why not abandon the 4.xx branch (that has over 3 years old code)?

Still

---

Current batch of Beta tasks have the same naming convention as Rosetta 4.20, and use a similar amount of RAM.
Roughly 1.2GB of RAM required per Task.


Also running for around 8 hours, not the previous Task runtime of around 3hrs.

---

Grant
Darwin NT

Current batch of Beta tasks have the same naming convention as Rosetta 4.20, and use a similar amount of RAM.

And seems there are problems with the graphic...

---

Some errors 1552811222, 1552784491, etc

ERROR: Error in protocols::cyclic_peptide_predict::SimpleCycpepPredictpplication::set_up_n_to_c_cyclization_mover() function: residue 1 does not have a LOWER_CONNECT.
ERROR:: Exit from: src/protocols/cyclic_peptide_predict/SimpleCycpepPredictApplication.cc line: 2442
BOINC:: Error reading and gzipping output datafile: default.out
08:36:42 (5544): called boinc_finish(1)

---

Yep, another group of faulty Tasks in with the current batch.

---

Grant
Darwin NT

Yep, another group of faulty Tasks in with the current batch.

Today a lot of wus with this error:

residue 1 does not have a LOWER_CONNECT

---

New batch, same problem.

---

Grant
Darwin NT

New batch, same problem.

A little debug from admins is welcome.

---

ERROR: Error in protocols::cyclic_peptide_predict::SimpleCycpepPredictpplication::set_up_n_to_c_cyclization_mover() function: residue 1 does not have a LOWER_CONNECT.
ERROR:: Exit from: src/protocols/cyclic_peptide_predict/SimpleCycpepPredictApplication.cc line: 2442
BOINC:: Error reading and gzipping output datafile: default.out
08:36:42 (5544): called boinc_finish(1)

Still the same error.
After 2 months. Seems there is no debug of errors...

---

A bug report (in the unlikely event that one of the developers still read forum and decides to fix some of the bugs).

On one of my computers (this one: https://boinc.bakerlab.org/rosetta/results.php?hostid=1211592) ALL, without exception, tasks for the Rosetta Beta 6.xx application end with an error at the 1st minute of operation.
The error is always the same:

Unhandled Exception Detected...

- Unhandled Exception Record -
Reason: Access Violation (0xc0000005) at address ........... (address vary)

This is a fairly old, but still decent and stable computer running on an AMD Phenom II X6 processor (6 physical cores) and 16 GB of RAM

Tasks for Rosetta 4.x are performed on it without any problems (except for faulty tasks that cause errors on all computers like famous "CHI angle" or "residue LOWERCONNECT" errors) as well as many(thousands - literally) tasks for several other DC projects: Einstein@Home, World Community Grid, SiDock@Home.

This has been going on for several months by now (starting from Rosetta beta version 6.03, I think, because I've seen some valid WUs with early versions from the 6.x branch on this computer), killing many hundreds of WUs.
During this time, there were several computer reboots and I reset the project twice (this includes re-downloading of all executable files and data files).
Without changes.

I do not think that the problem is in the software configuration, because on other computers I have not just a similar, but almost identical setup (originally obtained by cloning the system disk from this one).
The main difference is that other computers have newer processors installed - also from AMD but from newer generations - Ryzen 7 2700 and Ryzen 5 5600X on which the Rosetta 6.xx application works without problems with same SW setup.

So one of the versions of the error causes is that the application is trying to use one of the new instruction sets (AVX maybe? or other never CPU features which old Phenom series lacking ) without proper verification of their availability causing errors on older CPUs.

It would be nice if someone from the owners of the old processors (like a Phenom or Core 2 DUO/QUAD) check this.