Hi Morten,<br><br><br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div>So what is the correct way of handling TLS and NCS? </div></blockquote><div><br><br>nothing special. Just ask phenix.refine to use TLS (define TLS groups or ask phenix.refine to find them automatically - this is very quick, may take a minute or less), and also ask phenix.refine to use NCS restraints.<br>
<br>For NCS restraints you have two options: use Cartesian or torsion NCS. For Cartesian NCS you can let phenix.refine find groups automatically (the algorithm is not very smart though) or provide your atom selections for NCS groups yourself. <br>
For torsion NCS you don't have to do anything; and this is the recommended option.<br><br>A very simplistic example using command line (sure, all this is available in the GUI !):<br><br>phenix.refine model.pdb data.mtz strategy=individual_sites+individual_adp+tls main.ncs=true ncs.type=torsion tls.find_automatically=true<br>
<br></div><blockquote class="gmail_quote" style="margin:0pt 0pt 0pt 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<br></blockquote>On the phenix website it says under <u>current limitations of phenix.refine</u> "Atoms with anisotropic ADP in NCS groups". I take this to mean that phenix.refine doesn't handle the combination of TLS and NCS well, is this correct? </div>
<br>Sorry for this not being clear enough. All it's trying to say is that if you refine individual ADPs, NCS restraints will not handle B-factors correctly because NCS matrices should be applied to ADP matrices before applying similarity restrains. This is not implemented.<br>
<br>However, this is never realistic situation: if you refine with individual anisotropic ADPs then you never need to use NCS, and the other way around is true too. If you use TLS, then NCS are applied to residual (local atomic ADPs) only, so it's not a problem as well.<br>
<br>Pavel<br><br>