On Wed, May 7, 2014 at 11:56 PM, Jan Gebauer <jan.gebauer@uni-koeln.de> wrote:

With only one process running the first of five model was finished in
roughly 3 hours. However, the second model already takes more than 10
hours, and the log file on the _ros_tempXXX file wasn't update for the
last 9 hours. I can't see any progress, however it still uses 100% of
one processor. Unix's top tells me that "reduce" is completely using
this resource and that it had run for the last 821 minutes... so I guess
rosetta_refine is somehow stuck?

This sounds like a bug in Reduce/phenix.refine - which I thought we had fixed already. Could you look in the run directory and see if there are stdout/stderr files corresponding to this job? I think I know of a workaround we can add for this but it will require modifying the Rosetta source code.

By the way: Is rosetta_refine meant to work on a "normal" Computer -
like mine. In principle I would have access to a cluster, but set-up
time there would be considerably long for me...

A cluster or large multiprocessor is strongly recommended - due to the stochastic nature of Rosetta's optimization process, you really need to sample multiple runs to get an optimal result in most cases. If you use one of the queuing systems we support (SGE, PBS, LSF, others that I can't remember) it should be able to automatically parallelize across cluster nodes, although I've only tried this with SGE.

-Nat