-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
bug-frame-charge-94 #95
Conversation
72f3c1c
to
566a4fb
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good, approved. One thought on this that we should discuss though, your threshold for the Zimmerman polarity is quite high, so only a few residues are counted as polar, and this doesn't include residues like serine or threonine, which are traditionally included as such. We might want to explore using Grantham polarity with a cut off around 8 too.
In this part of create_frame_dataset.py
Does it appear that we are declaring the gaussian_atom variable and running add_gaussian_at_position function redundantly? In that case, does this one make sense:
|
@sunal1996 in the case of a charged residue (say lysine), the gaussian needs to be added in the atom index (C, N, O, Ca, Cb) AND in the charge index (ie. the fifth). I think in your if/else logic all the atoms of a charged residue (C, N, O, Ca, Cb) would end up in the 5th channel and there would be no atoms in the C, N, O, Ca, Cb channels |
Ah, all clear. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good merge when ready.
Closes #94 Fix