Thanks for your quick response. I checked the source code file in the light of your response. Unfortunately, Chimera has a lot of internal variables/modules so I'm not sure whether I get the whole picture just looking at the code. So,what I understand is that the initial calculation is used to predict the equation of the best fit line, which in turn is used as the starting point for a loop search to give the new "best" values that minimize the variance of the distance between the helix points and the best-fit line. Is my understanding correct? If so, do you take a "brute force" numerical approach to scan a number of different values and keep the best, or is that a gradient based scan? Alican Gulsevin, PhD Postdoctoral Researcher Vanderbilt University Department of Chemistry Center for Structural Biology - Meiler Laboratory 465 21st Ave South Nashville, TN,37221 Office: MRBIII, Room: 5150C Phone: (615)-936-6594 ________________________________________ From: Eric Pettersen [pett@cgl.ucsf.edu] Sent: Tuesday, November 13, 2018 3:36 PM To: Gulsevin, Alican Cc: chimera-users@cgl.ucsf.edu Subject: Re: [Chimera-users] Helix axis and correction Hi Alican, 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. 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. 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. —Eric Eric Pettersen UCSF Computer Graphics Lab On Nov 12, 2018, at 4:04 PM, Gulsevin, Alican <alican.gulsevin@Vanderbilt.Edu<mailto:alican.gulsevin@Vanderbilt.Edu>> wrote: Hello everyone, 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? Thanks for your help, Alican Gulsevin, PhD Postdoctoral Researcher Vanderbilt University Department of Chemistry Center for Structural Biology - Meiler Laboratory 465 21st Ave South Nashville, TN,37221 Office: MRBIII, Room: 5150C Phone: (615)-936-6594 _______________________________________________ Chimera-users mailing list: Chimera-users@cgl.ucsf.edu<mailto:Chimera-users@cgl.ucsf.edu> Manage subscription: http://plato.cgl.ucsf.edu/mailman/listinfo/chimera-users<https://na01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fplato.cgl.ucsf.edu%2Fmailman%2Flistinfo%2Fchimera-users&data=02%7C01%7Calican.gulsevin%40Vanderbilt.Edu%7Cf5fb868777b2438cc63b08d649b01dcf%7Cba5a7f39e3be4ab3b45067fa80faecad%7C0%7C1%7C636777418104582526&sdata=WLsVnWe2GcuSZ9lStcARemVPVbvQXVTR6i4lUiRx%2FfI%3D&reserved=0>