<div dir="ltr"><div><div><div><div>Hi Pavel<br><br></div>Just to let you know, I ran phenix.refine with and without weight optimization and I summarize the results below (R, clashscore, Ramachandran and rotamer outliers)<br><br></div>without - 27.9/32.1, 21.9, 4.71, 11.08<br></div>with - 32.8/35.1, 8.6, 3.89, 6.44<br></div><div>without (torsion-angle NCS) - 27.9/31.0, 26.5, 4.1, 10.82<br></div><div><br></div>So, it seems weight optimization is trying to lower the clashes and outliers at the expense of R factor.<br></div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, May 20, 2015 at 11:39 AM, Pavel Afonine <span dir="ltr"><<a href="mailto:pafonine@lbl.gov" target="_blank">pafonine@lbl.gov</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi Mohamed,<span class=""><br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
I am refining a low resolution structure (3.8 A). After I fix most of the outliers (red bars) in Coot, phenix.refine is causing my structure to be worse than the start with 13 % Ramachandran outlier and 13 % rotamer outlier.<br>
</blockquote>
<br></span>
could you please send me data and model (before refinement) files then I will have a look. Refinement at low resolution is generally tricky and often requires using beyond the default settings such as secondary structure, rotamer and Ramachandran plot restraints, NCS (at 3.8A Cartesian NCS or even NCS constraints might be a better option).<br>
<br>
If you send me files I will try plausible options to see what can be done.<span class="HOEnZb"><font color="#888888"><br>
<br>
Pavel<br>
</font></span></blockquote></div><br></div>