I would exit BOINC and restart it in that situation rather than aborting them.

Is that because there is the possibility for them to complete and you get the information about the run and the cruncher gets the credit?

I would exit BOINC and restart it in that situation rather than aborting them.

Is that because there is the possibility for them to complete and you get the information about the run and the cruncher gets the credit?

Yes exactly, although flagging it up as an issue is useful as it obviously shouldn't happen and something needs fixing (whether that's in Rosetta or BOINC or elsewhere).

---

Many thanks. I did that yesterday (exited BOINC and restarted it) and it worked. The jobs were concluded, uploaded and received credit.

Immediately after I restarted BOINC, the elapsed time of both jobs decreased from 5 hours to about 56 minutes. Two of them also decreased progress from 100% to about 86-88%. And they received credit as if one hour had been elapsed. But they were concluded.

Many thanks again.
Valter.

hello,
I don't know if this issue is relevant or worthless, so i'm posting it: tonight I got 13 WU with app release 3.67 and 1 of these workunits completed successfully but failed validation with this message "workunit error - check skipped". WU is: https://ralph.bakerlab.org/workunit.php?wuid=3054528.

Now Rosetta Mini Beta 3.65
I'm little confused about all those versions :-)

Now Rosetta Mini Beta 3.65
I'm little confused about all those versions :-)

Me too! just kidding.

The versioning has been a bit inconsistent because I've just been updating the linux versions mainly. I did the recent update just have the beta and non-beta versions matched up.

---

And again, nothing but validate errors on the new batch 3.65 T0559_indexed_frags_test_...

WUs of any other brand validate just fine. There's a bug in your validator IMHO.

And again, nothing but validate errors on the new batch 3.65 T0559_indexed_frags_test_...

Windows, linux or mac?
My 2 win has no problem

There's a bug in your validator IMHO.

There are a lot of requests to upgrade their OLD servers...

And again, nothing but validate errors on the new batch 3.65 T0559_indexed_frags_test_...

WUs of any other brand validate just fine. There's a bug in your validator IMHO.

Please ignore the validation errors. I suspect it's just because the jobs are running faster than allowed on your computer for this specific test case. I'll switch to a better test case with longer run times per model.

---

Thank you very much. So my computer is too fast for these WUs :)

I'm looking forward to the new longer WUs. Keep on the good work!

No new test??

What's new with 3.68?
Bugfix? New protocols?

3.68 uses the latest Rosetta source. It includes new protocols, for example, a new cyclic peptide modeling method, and also a newly optimized energy function that improves scientific benchmarks.

---

Ok, new graphic is pretty but seems to be no "coherent".
1) All blue, included "accepted energy" box. Not an optimal solution, imho.
2) Blue only simulations boxes (searching, accepted, low energy) and return to black for others boxes.

3.68 uses the latest Rosetta source. It includes new protocols, for example, a new cyclic peptide modeling method, and also a newly optimized energy function that improves scientific benchmarks.

I would like to build a binary and test environment somewhat similar to yours and do some performance analysis. I can guess and experiment to find an environment that works or you can guide my efforts to complement the work you guys are doing and would like done.

I am currently using the November source bundle (rosetta_src_2015.39.58186_bundle.tgz) on a RHEL7.2 clone with the standard gcc/g++ 4.8.4.

I have been able to build the "bin" default, debug and release versions and with the "extras=static". The only problem so far is the static scripts generate an error in the TEST scripts caused by a conservative "-Werror" option.

I can upgrade/downgrade software versions easily if you prefer.

If there is no need for Software Performance Engineer, then I also have some time for other tasks too. Testing, validation, bug isolation ... ?

If you have completed the bin build then you can run the various tests, integration, profile, etc in Rosetta/main/tests. I'm not familiar with the source bundle that you have, is it the academic release? Feel free to contact me via email dekim at u.washington.edu

---

Got this error but the work unit was valid

<stderr_txt>
or/Parser should have replaced DummyMover.)

ERROR: false
ERROR:: Exit from: ......srcappspublicboincminirosetta.cc line: 96
DummyMover::apply() should never have been called! (JobDistributor/Parser should have replaced DummyMover.)

This line was repeated dozens of times

See Result 3473010

Conan

---

Got this error but the work unit was valid
<stderr_txt>
or/Parser should have replaced DummyMover.)

ERROR: false
ERROR:: Exit from: ......srcappspublicboincminirosetta.cc line: 96
DummyMover::apply() should never have been called! (JobDistributor/Parser should have replaced DummyMover.)

This line was repeated dozens of times

Same error, but my wus are "validation error" :-(

I'm looking into this odd error. Can anyone who is experiencing these errors do me a favor and reset their project (mainly to just clear the project data and slot directories). This error can happen if the application is using an older database version but this shouldn't happen since the new database is packaged with the new application. thanks!

---

I'm looking into this odd error. Can anyone who is experiencing these errors do me a favor and reset their project (mainly to just clear the project data and slot directories)

To be clear, i detach and re-attach the project....you've reached the daily quota of 6 wus :-(
I have to wait 12 hours to try new wus