<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class="">Hi Billy, I should clarify that I typically use real_space_refine on the command line - I have not checked it in the GUI. <div class=""><br class=""></div><div class="">On the command line, it provides a list of the available arrays, but no way to input a selected array (and the output of phenix.real_space_refine --help doesn’t provide any promising looking options).<div class=""><br class=""></div><div class="">Cheers</div><div class="">Oli<br class=""><div class=""><div><blockquote type="cite" class=""><div class="">On Oct 5, 2016, at 5:12 PM, Billy Poon <<a href="mailto:bkpoon@lbl.gov" class="">bkpoon@lbl.gov</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class="">Hi Oliver,<div class=""><br class=""></div><div class="">When you provide a MTZ file with map coefficients to the phenix.real_space_refine GUI, the widget labeled "Map coefficients label" should refresh and provide a list of available arrays. It should behave the same way as the "Data labels" and "Phase labels" widgets in the phenix.refine GUI. If the "Map coefficients label" widget is not displaying the arrays in your MTZ file, can you provide your file so that I can take a closer look? Thanks!</div></div><div class="gmail_extra"><br clear="all" class=""><div class=""><div class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr" class=""><div class=""><div dir="ltr" class=""><div class=""><div dir="ltr" class=""><div class=""><div dir="ltr" class=""><div class=""><div dir="ltr" class=""><div dir="ltr" class=""><div dir="ltr" class=""><div class=""><div class="">--</div><div class=""><span style="font-size:12.8000001907349px" class="">Billy K. Poon</span><br class=""></div></div><div class="">Research Scientist, Molecular Biophysics and Integrated Bioimaging</div><div class="">Lawrence Berkeley National Laboratory</div><div class="">1 Cyclotron Road, M/S 33R0345</div><div class="">Berkeley, CA 94720</div><div class="">Tel: (510) 486-5709</div><div class="">Fax: (510) 486-5909</div><div class="">Web: <a href="https://phenix-online.org/" target="_blank" class="">https://phenix-online.org</a></div></div></div></div></div></div></div></div></div></div></div></div></div></div>
<br class=""><div class="gmail_quote">On Wed, Oct 5, 2016 at 2:02 PM, Oliver Clarke <span dir="ltr" class=""><<a href="mailto:olibclarke@gmail.com" target="_blank" class="">olibclarke@gmail.com</a>></span> wrote:<br class=""><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi,<br class="">
<br class="">
I find phenix.real_space refine very effective for initial refinement of a model against a density modified map after molecular replacement (with morphing and reference restraints etc enabled).<br class="">
<br class="">
However, when I do this it seems like if there is more than one array of map coefficients in the file there is no way to select which columns to use, unlike for phenix.refine - would it be possible to add such an option? Currently I just use cad in ccp4 to make a file with the desired columns, but it would be a smoother process if the desired column labels could be specified directly at run time.<br class="">
<br class="">
Cheers<br class="">
Oli<br class="">
______________________________<wbr class="">_________________<br class="">
phenixbb mailing list<br class="">
<a href="mailto:phenixbb@phenix-online.org" class="">phenixbb@phenix-online.org</a><br class="">
<a href="http://phenix-online.org/mailman/listinfo/phenixbb" rel="noreferrer" target="_blank" class="">http://phenix-online.org/<wbr class="">mailman/listinfo/phenixbb</a><br class="">
Unsubscribe: <a href="mailto:phenixbb-leave@phenix-online.org" class="">phenixbb-leave@phenix-online.<wbr class="">org</a><br class="">
</blockquote></div><br class=""></div>
</div></blockquote></div><br class=""></div></div></div></body></html>