<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">Dear Florian,<div><br></div><div>Normally I would recommend letting AutoSol deal with the anisotropy of your data, as it already has the capability of anisotropy correction. It is usually best to keep your "data" uncorrected, so that the "data" are not changing as you develop new interpretations of them. You can control the application of anisotropy corrections in AutoSol as you noticed with correct_aniso=True. AutoSol will apply an anisotropy correction during structure solution and map generation, and will keep your uncorrected data for refinement (an anisotropy term is automatically applied as a parameter in refinement as well).</div><div><br></div><div>There is a possible advantage to using the UCLA anisotropy server in that it throws away data that is weak, and it is possible that in some cases that weak data could interfere with structure solution.</div><div><br></div><div>If you do use anisotropy-corrected data for AutoSol I would recommend:</div><div><br></div><div>1. Specify a "refinement file" explicitly, and supply a file that is not anisotropy-corrected (i.e., your original data).</div><div>2. Specify "correct_aniso=False" for AutoSol (it would probably do that anyway as your corrected-data would have no anisotropy left).</div><div><br></div><div>AutoSol would not normally use FP or SIGFP from the data file, only F+SIGF+ F-SIGF-; however if you are supplying a "refinement file" then this file would need F and SIGFP (and you would would want to use uncorrected data there)</div><div><br></div><div>The NCS overlap is not an absolute scale, so greater than one is ok. The NCS correlation goes from -1 to 1, and 0.5 is ok, but not that great.</div><div><br></div><div>You can supply AutoBuild with a sharpened map with map_file=Mymap_coeffs.mtz and it will use this map in the first cycle of building (you might only run one cycle in this case). At 4.1 A, I would only use the helices_strands_only option in AutoBuild however, as model building at this resolution, particularly with a relatively difficult map, will not work well.</div><div><br></div><div><div>I hope that helps!</div></div><div><br></div><div>All the best,</div><div>Tom T</div><div><br></div><div><div><div>On Sep 16, 2010, at 8:23 AM, Florian Schmitzberger wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div>Dear All,<br><br>I would have a number of Phenix related questions:<br><br>Firstly, I used the anisotropy server ( to anisotropically truncate my mtz file with anomalous signal (SAD data). My question is if the labels (for F+/F- and SIGF+/SIGF- are correctly recognized by Phenix (Autosol).<br><br>The columns labels are: F_ref for FP; QSIGF_ref for SIGFP; GF(+)pk for F(+); LSIGF(+)pk for SIGF(+), GF(-)pk for F(-); LSIGF(-)pk for SIGF(-).<br><br>It seems QSIGF and GF(+)pk/LSIGF(+)pk etc. are , but I am uncertain if it recognizes F_ref, because for the LABIN INPUT LABELS it says "NONE" for"F".<br><br>Phenix does not seem to detect the anistropy ("Not using aniso-corrected data files as the range of aniso b is only 19.52 and 'correct_aniso' is not set); so I suppose I should use the correct_aniso=True keyword.<br><br>Secondly, what are good values for the evaluation of the NCS mask and NCS averaging Resolve is using in Phenix; NCS overlap values (e.g. in my case 1.1) and NCS_CORR (in my case 0.52) in the "resolve.scores" file. Does an NCS overlap value of greater than 1 make sense?<br><br>I am working with a (anisotropic) dataset with 4.1/4.5 A resolution, 78 % solvent content, 2-fold NCS; Perhaps a naive question: It is not possible to use B-factor sharpened maps for autobuilding with Phenix Autobuild is it?<br><br>Thank you for any comments!<br><br>Regards,<br><br>Florian<br>-----------------------------------------------------------<br>Florian Schmitzberger<br>Biological Chemistry and Molecular Pharmacology<br>Harvard Medical School<br>250 Longwood Avenue, SGM 130<br>Boston, MA 02115, US<br>Tel: 001 617 432 5602<br><br><br><br><br><br><br><br><br><br><br>_______________________________________________<br>phenixbb mailing list<br><a href="mailto:phenixbb@phenix-online.org">phenixbb@phenix-online.org</a><br>http://phenix-online.org/mailman/listinfo/phenixbb<br></div></blockquote></div><br><div>
<span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0; "><div><div><div><div><div><br>Thomas C. Terwilliger<br>Mail Stop M888<br>Los Alamos National Laboratory<br>Los Alamos, NM 87545<br><br>Tel: 505-667-0072 email: <a href="mailto:terwilliger@LANL.gov">terwilliger@LANL.gov</a><br>Fax: 505-665-3024 SOLVE web site: <a href="http://solve.lanl.gov">http://solve.lanl.gov</a><br>PHENIX web site: http:www.phenix-online.org<br>ISFI Integrated Center for Structure and Function Innovation web site: <a href="http://techcenter.mbi.ucla.edu">http://techcenter.mbi.ucla.edu</a><br>TB Structural Genomics Consortium web site: <a href="http://www.doe-mbi.ucla.edu/TB">http://www.doe-mbi.ucla.edu/TB</a></div><div>CBSS Center for Bio-Security Science web site: <a href="http://www.lanl.gov/cbss">http://www.lanl.gov/cbss</a><br><br></div></div></div></div><br></div></span><br class="Apple-interchange-newline">
</div>
<br></div></body></html>