RALPH@home

Posts by Trotador

  UW Seal
 
[ Home ] [ Join ] [ About ] [ Participants ] [ Community ] [ Statistics ]
  [ login/out ]

1) Message boards : RALPH@home bug list : Rosetta mini beta and/or android 3.61-3.83 (Message 6074)
Posted 604 days ago by Trotador
All WUs continue erroring in Linux. W7 seems Ok, rest of windows is a mix of failure/success
2) Message boards : RALPH@home bug list : Rosetta mini beta and/or android 3.61-3.83 (Message 6061)
Posted 609 days ago by Trotador
All units erroring in all my Linux hosts:

Some of the wus failing after finishing crunching OK with the error (these wus were donwloaded yesterday):

</stderr_txt>
<message>
upload failure: <file_xfer_error>
<file_name>des5ralph_design5_hydrophobic32_test1_buriedtrp_S_0095_SAVE_ALL_OUT_20313_229_0_0</file_name>
<error_code>-161 (not found)</error_code>
</file_xfer_error>

</message>
]]>

Other failing after several hours or after restarting BOINC and reporting 0 seconds of time computed with the error (these ones dowloaded today):

ERROR: ERROR: Option matching -cyclic_peptide:user_set_alph_dihedral_perturbation not found in command line top-level context

I'm seing that most of the windows hosts seem to finish Ok the wu and report success, but it is not a conclusive fact.

Stopping crunching until knowing more.


3) Message boards : RALPH@home bug list : Rosetta mini beta and/or android 3.61-3.83 (Message 6060)
Posted 609 days ago by Trotador
In one of my hosts, all "des5ralph_design5" units failing after finishing crunching OK with

</stderr_txt>
<message>
upload failure: <file_xfer_error>
<file_name>des5ralph_design5_hydrophobic32_test1_buriedtrp_S_0095_SAVE_ALL_OUT_20313_229_0_0</file_name>
<error_code>-161 (not found)</error_code>
</file_xfer_error>

</message>
]]>

This host have have processing time above default, all units have been crunched during 9-12 hours and generated lot of decoys but end with this error.

Wingmen crunhing just an hour and generating few decoys are uploading OK.
4) Message boards : RALPH@home bug list : Rosetta mini beta and/or android 3.61-3.83 (Message 6051)
Posted 643 days ago by Trotador
The current Ralph WUs use huge amounts of RAM, I've seen up to 4 Gb per unit, is it on purpose? any new kind of simulation?

thanks for the info




Yes, I'm running a test of a new type of job that runs small perturbations of the protein backbone and then does a round of design. The design protocol can use a lot of memory. I realize that this will be problematic and will see if we can distribute these jobs to high memory machines. We may just not be able to run these on R@h.



I've crunched a lot of these backrub units, they are tough due to the large memory requirements. It is necessary to limit the quantity of units being simultaneously crunched and a lot of baby sitting, but it is also fun :).

Most of them don't use to go over 4 Gb but I got half a dozen reaching almost 7GB in the same host. It has 32 Gb but also 72 threads :), in short it stalled because lack of memory, So I finally had to abort them and a few more because they were nearly over the deadline.



5) Message boards : RALPH@home bug list : Win10 3.71 Unhandled Exception: Reason: Out Of Memory (backrub) (Message 6047)
Posted 649 days ago by Trotador
Quote from thread http://ralph.bakerlab.org/forum_thread.php?id=567

Trotador
The current Ralph WUs use huge amounts of RAM, I've seen up to 4 Gb per unit, is it on purpose? any new kind of simulation?

thanks for the info


Dekim

Yes, I'm running a test of a new type of job that runs small perturbations of the protein backbone and then does a round of design. The design protocol can use a lot of memory. I realize that this will be problematic and will see if we can distribute these jobs to high memory machines. We may just not be able to run these on R@h.
6) Message boards : RALPH@home bug list : Rosetta mini beta and/or android 3.61-3.83 (Message 6038)
Posted 652 days ago by Trotador
The current Ralph WUs use huge amounts of RAM, I've seen up to 4 Gb per unit, is it on purpose? any new kind of simulation?

thanks for the info




Yes, I'm running a test of a new type of job that runs small perturbations of the protein backbone and then does a round of design. The design protocol can use a lot of memory. I realize that this will be problematic and will see if we can distribute these jobs to high memory machines. We may just not be able to run these on R@h.


R@H means Rosseta, doesn`t it? It is good for the investigation you could look for ways of distributing these units. The only effective way I could think of is limiting the quantity of units downloaded, by the user as in CEP project in WCG or by the project. Distributing them only to hosts with lot of memory could just not be enough if the hosts have also a lot of available threads (like mine).

A good thing I'm seeing with these units is that Boinc/Ralph seems to take into account the amount of available system memory and limits the menory used, even limiting the quantity of units in execution below the quantity of available threads, and the systems does not stall and hang as used to happen in these cases. Is it correct ?

7) Message boards : RALPH@home bug list : Rosetta mini beta and/or android 3.61-3.83 (Message 6035)
Posted 652 days ago by Trotador
The current Ralph WUs use huge amounts of RAM, I've seen up to 4 Gb per unit, is it on purpose? any new kind of simulation?

thanks for the info

8) Message boards : RALPH@home bug list : Rosetta mini beta and/or android 3.61-3.83 (Message 5905)
Posted 770 days ago by Trotador
I just updated the 64bit linux app. Please let me know how it goes as there might still be compatibility issues with the glut, GL, GLU libraries etc...


3.65 is working, great!
9) Message boards : RALPH@home bug list : Rosetta mini beta and/or android 3.61-3.83 (Message 5897)
Posted 770 days ago by Trotador
In Linux libglut.so.3 errors all over the place, perhaps looking in wrong directory?


me too :(
10) Message boards : RALPH@home bug list : minirosetta beta 3.50-3.52 apps (Message 5824)
Posted 989 days ago by Trotador
Validate error for all tasks returned today.

It looks like being on the server side, units crunch ok.

Suspended until solved.


Next 10 posts

Home | Join | About | Participants | Community | Statistics

Copyright © 2017 University of Washington

Last Modified: 20 Nov 2008 7:11:22 UTC
Back to top ^