<div dir="ltr">Hi Edward,<div><br></div><div class="gmail_extra"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">I had a related question- is it possible to have env. variables evaluated in an eff file?<br>
(Like in cns, {===>} parameter_infile_1="CNS_TOPPAR<wbr>:protein_rep.param";, CNS_TOPPAR is env var)<br></blockquote><div>I'm afraid no.</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
If not, do command line parameters override what is in the eff file? Like:<br></blockquote><div>Yes, whatever is in command-line arguments overrides values in .eff file.</div><div> </div><div>I think simple bash/tsch script would be the easiest way to solve the original Andrew's problem.</div><div><br></div><div>Best regards,</div><div>Oleg Sobolev.</div><div><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div class="h5"><br>
<br>
On 11/29/2016 05:21 PM, Andrew Morin wrote:<br>
</div></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div class="h5">
Hello,<br>
<br>
I am trying to find a convenient way to generate maps using phenix.mtz2map at increasingly greater values of d_min.<br>
<br>
For example:<br>
<br>
I have a .mtz file of a structure solved at 2.4A. I run phenix.mtz2map with d_min=none and obtain a map using all of the resolution data. I would like to also create 10 more maps with d_min = 3.4, 4.4, 5.4, 6.4,...12.4A.<br>
An mtz of 1.7A would increment at 2.7, 3.7...11.7A, etc.<br>
<br>
Might anyone know of a handy way to automate this over a large number of mtz files?<br>
<br>
ALTERNATIVELY - I am performing a phenix.cut_out_density step prior to this. So if it might be easier to automate a incrementing high resolution cutoff in phenix.cut_out_density, that would also work.<br>
<br>
Thanks for your help.<br>
<br>
-Andrew<br>
<br>
<br></div></div>
______________________________<wbr>_________________<br>
phenixbb mailing list<br>
<a href="mailto:phenixbb@phenix-online.org" target="_blank">phenixbb@phenix-online.org</a><br>
<a href="http://phenix-online.org/mailman/listinfo/phenixbb" rel="noreferrer" target="_blank">http://phenix-online.org/mailm<wbr>an/listinfo/phenixbb</a><br>
Unsubscribe: <a href="mailto:phenixbb-leave@phenix-online.org" target="_blank">phenixbb-leave@phenix-online.o<wbr>rg</a><br>
<br>
</blockquote>
______________________________<wbr>_________________<br>
phenixbb mailing list<br>
<a href="mailto:phenixbb@phenix-online.org" target="_blank">phenixbb@phenix-online.org</a><br>
<a href="http://phenix-online.org/mailman/listinfo/phenixbb" rel="noreferrer" target="_blank">http://phenix-online.org/mailm<wbr>an/listinfo/phenixbb</a><br>
Unsubscribe: <a href="mailto:phenixbb-leave@phenix-online.org" target="_blank">phenixbb-leave@phenix-online.o<wbr>rg</a><br>
</blockquote></div><br></div></div>