The minirosetta_beta application has been updated to version 3.23. In the truest sense of the word, these binaries are alpha. If you experience increased error rates, please let us know.

In the truest sense of the word, these binaries are alpha.

3.22 seems to be very stable.
With 3.23 do you rewrite all the binaries?? :-)

Had this error on a 6 hour preference, it was completed by another volunteer with a much shorter runtime preference

See 2607010

ERROR: Fatal SOGFunc_Impl error.
ERROR:: Exit from: ......srccorescoringconstraintsSOGFunc_Impl.cc line: 181
BOINC:: Error reading and gzipping output datafile: default.out

Conan

---

3.22 seems to be very stable.
With 3.23 do you rewrite all the binaries?? :-)

The reason for the update is new & improved protocols. We're testing out new ways of doing things (particularly in the area of structure prediction), and 3.23 simply can't do these new protocols. It's cutting edge science (we hope), so we need to update the application to handle it.

The "alpha in the truest sense of the word" bit is due to the fact that, for technical reasons, we've had to change how we build the minirosetta application binaries. While we don't anticipate that there will be significant issues due to the change, we're aware that there could be unforeseen issues.

Had this error on a 6 hour preference, it was completed by another volunteer with a much shorter runtime preference

See 2607010

ERROR: Fatal SOGFunc_Impl error.
ERROR:: Exit from: ......srccorescoringconstraintsSOGFunc_Impl.cc line: 181
BOINC:: Error reading and gzipping output datafile: default.out

Conan

Around a couple of tenths of mine have errored with this same message, all the wingmen but one also failed so far.

It is a system with windows 7 64 bits, boinc manager 6.10.58

The reason for the update is new & improved protocols. We're testing out new ways of doing things (particularly in the area of structure prediction), and 3.23 simply can't do these new protocols. It's cutting edge science (we hope), so we need to update the application to handle it.

The "alpha in the truest sense of the word" bit is due to the fact that, for technical reasons, we've had to change how we build the minirosetta application binaries. While we don't anticipate that there will be significant issues due to the change, we're aware that there could be unforeseen issues.

First all, Rocco, thanks for the answer.
The new client seems to be good!
Now i have other questions :-)
1) If it is "cutting edge", why 3.23? I think it's a 3.50 or 4.0 release...
2) "we had to change how we build"...have you change the compiler? Is this a "prelude" for gpu client? :-P

Keep it up!

1) If it is "cutting edge", why 3.23? I think it's a 3.50 or 4.0 release...

From a software perspective, the change wasn't all that great. The general framework of the minirosetta client is still the same, it's just we added a bit of new functionality on top of that. Most updates to Rosetta@home are like that - they're not so much to increase stability or fix bugs (although we do do that), but rather to implement new scientific functionality.

In some respects, version numbering is meaningless. As long as different versions have different numbers, there really isn't a uniform standard on how to do software versioning. For the boinc minirosetta application, we're currently using a major version of 3 (as it's based on the Rosetta3 code) and a minor version which increments by one on each new release. As boinc updates the code automatically, a more sophisticated versioning scheme really isn't necessary. Run Rosetta@home, and you'll get the latest-and-greatest, whether that's called 3.23, 4.0 or XF2012

2) "we had to change how we build"...have you change the compiler? Is this a "prelude" for gpu client? :-P

Sorry, a little more prosaic. We had hardware issues on the system we normally use to build the client, so we had to set up a new build system.

Run Rosetta@home, and you'll get the latest-and-greatest, whether that's called 3.23, 4.0 or XF2012

XF2012 is a great name!!! :-)

All tasks end within 30 seconds as Computation error. It says output file "blah blah" absent. Now reached daily task limit.

Gggrrrrrr!!!!! Not happy.

Win 7 Ult 64-bit. Various BOINC versions, various computers eg 7.0.23, 6.10.60

---