- This topic has 2 replies, 2 voices, and was last updated 10 years, 2 months ago by Anonymous.
September 18, 2013 at 10:59 am #1721Anonymous
we’re trying to model a protein complex in helical symmetry with SymmDock in Rosetta 3.5.
There is one problem occuring always, which we coundn’t solve so far: In most of the resulting
models there are single residues displaced from the backbone of the protein. Often the whole structure
looks completely broken. Relating to this we made the observation that the master subunit is not affected
but the strength of the effect (number of displaced residues) increases with the number of jumps between the master
subunit and the affected subunits. Also the distance of a displaced residue to the protein backbone increases with
the number of jumps between the slave and the master subunit. The problem is that these disrupted structures are often
scored as “good” ones because the displaced residues don’t clash with others. In addition to this, effected residues seem
to be always located at the potential interfaces between subunits. We found that this problem occurs during the high resolution refinement step
in fa-mode. E.g. giving the flag “-prevent_repacking” was completely avoiding these disruptions, meaning probably those occuring during the packing or repacking stage?
And the effect is somehow related to the movement allowed by the dofs controlling the rise and the rotation around the helical axis.
We generated the symmetry definiton file based on a template helical structure (once based on a homolog complex,
once based on a self generated “loosely packed” helix).
Also we modeled a 7-subunit system of the complex or a 21-subunit complex (controlled by the -r flag for “make_symmdef_file.pl”), this problem was always occuring.
All dofs in the sdf were properly ramdomized, as far as we know. But we found that not allowing rotation around z (the helical axis)
is reducing this effect strongly even though not completely. But of course for sampling the search space in helical symmetry
this dof is very important and removing it can’t be the solution.
Feeding in AtomPair distance constraints and/or an edensity map works very well but was not altering our problem.
The question is now how can we overcome this problem – is there any easy solution for it?
Is it maybe a problem with the symdef file?
Thank you already in advance!
September 18, 2013 at 7:06 pm #9310Anonymous
Frank Dimaio actually just checked in a fix for a bug which he thinks is the cause of the problem (the ‘Tsymm_’ matrices in SymmInfo don’t get properly updated for lattice symmetries in symmdock and fold-and-dock). The fix should be in this week’s weekly release (should be week 38, 2013) when it comes out (or any later weekly release, if it comes to that).
The big thing to keep in mind with going from Rosetta3.5 to a weekly release is that we’ve moved to a new scorefunction (Talaris2013). We think it’s better, so it’s probably worth keeping for new production runs, but if you want to use the old scorefunction, simply add the flag “-restore_pre_talaris_2013_behavior” to the commandline.
If for some reason you don’t want to update to the latest weekly release, I can see about tracking down a patch for the bug you ran into, so you can fix just that bug and recompile.
September 19, 2013 at 9:27 am #9311Anonymous
Thank you very much for the update, I do really appreciate it!
I think I will wait for the new weekly release and update to it.
- You must be logged in to reply to this topic.