<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class="">Hi Alican,<div class=""><span class="Apple-tab-span" style="white-space:pre"> </span>It’s an ad hoc method. Generally speaking, without correction the helical axis vector is taken to be the largest eigenvector of the helical backbone atoms. For short helices, this vector may differ significantly from what it would be if the helix were longer because of a “partial turn” on the end of the short helix causing the eigenvector to tilt towards those “extra” atoms. In fact, for very short helices the largest eigenvector may not even be the best one to use — it could be going across the helix instead of along it.</div><div class=""><span class="Apple-tab-span" style="white-space:pre"> </span>Anyway, with helical correction “on" each eigenvector is evaluated to see which has the least variance in the distances from the helical backbone atoms to the vector — the one with the least total variance is used as the initial helix axis. Then a “corrected” axis is computed that tries to move the axis so that it has less variance, basically by having the axis “pulled” toward backbone atoms depending on the amount of variance to them. The corrected axis then evaluated for variance, and if the variance is less, then the corrected axis is accepted as the new helical axis. The process is repeated until no variance reduction occurs.</div><div class=""><span class="Apple-tab-span" style="white-space:pre"> </span>The code for this is the “while iterate:” loop in the axis() function of <your Chimera installation>/share/lib/StructMeasure/__init__.py. On a Mac, <your Chimera installation> is Chimera.app/Contents/Resources.</div><div class=""><br class=""></div><div class="">—Eric</div><div class=""><br class=""><div class="">
<div style="color: rgb(0, 0, 0); letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div class=""><span class="Apple-tab-span" style="white-space: pre;"> </span>Eric Pettersen</div><div class=""><span class="Apple-tab-span" style="white-space: pre;"> </span>UCSF Computer Graphics Lab</div></div><br class="Apple-interchange-newline">
</div>
<div><br class=""><blockquote type="cite" class=""><div class="">On Nov 12, 2018, at 4:04 PM, Gulsevin, Alican <<a href="mailto:alican.gulsevin@Vanderbilt.Edu" class="">alican.gulsevin@Vanderbilt.Edu</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div class="">Hello everyone,<br class=""><br class="">I have a question about the "helical correction" option for calculating helix axes. I've been trying to find the exact calculation Chimera uses to correct the helix axis, but I couldn't find anything specific in the archives and I also couldn't figure it from the source code. Where can I find a detailed description of how the helix axes and the corresponding corrections are calculated?<br class=""><br class="">Thanks for your help,<br class=""><br class="">Alican Gulsevin, PhD<br class="">Postdoctoral Researcher <br class=""><br class="">Vanderbilt University<br class="">Department of Chemistry<br class="">Center for Structural Biology - Meiler Laboratory<br class="">465 21st Ave South<br class="">Nashville, TN,37221<br class="">Office: MRBIII, Room: 5150C<br class="">Phone: (615)-936-6594<br class="">_______________________________________________<br class="">Chimera-users mailing list: <a href="mailto:Chimera-users@cgl.ucsf.edu" class="">Chimera-users@cgl.ucsf.edu</a><br class="">Manage subscription: <a href="http://plato.cgl.ucsf.edu/mailman/listinfo/chimera-users" class="">http://plato.cgl.ucsf.edu/mailman/listinfo/chimera-users</a><br class=""></div></div></blockquote></div><br class=""></div></body></html>