-
Notifications
You must be signed in to change notification settings - Fork 107
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
Releasing 2.3.1 #160
Merged
Merged
Releasing 2.3.1 #160
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Ligand structures in PLIP do not contain hydrogen, which affects HBond donor/acceptor identification. For donor identification, the atoms of the full structure with hydrogens is used, for acceptor identification this mapping was missing so far. This commit fixes the issue and closes #123.
The removed bit was not doing anything and seems to be a residual from more than 10 years ago (last change related to the in_ring variable was in commit 2b87b08)
Instead of the bond with angle omega closest to the ideal value the one further away was kept.
When checking, whether the donor atom already forms a hydrogen bond, the openBabel molecules atom index instead of the original index in the pdb file was used, resulting in random hydrogen bonds in other parts of the structure preventing water bridges from showing up and potentially not filtering out the ones that actually needed filtering.
OpenBabel crashes when trying to generate canonical SMILEs for peptide chains that are too long.
PLIP used to copy all ligand atoms and then all their bonds to create the ligand structure. However, this looses information like sidechain/backbone membership of atoms (relevant for detection of charge in peptide ligands). Using the "copy.substructure()" function of OpenBabel retains this information.
The functional groups considered for charge detection on the ligand side are not sufficient to detect the aminoacids that can form salt bridges when the ligand is a peptide. This commit implements charge detection for peptide ligands to match charge detection for protein receptors.
So far small molecule ligands present in the chain picked with the --inter or --intra flag were treated as part of that chain during intra or inter protein chain detections and for some interaction types interactions were detected.
For protein-protein interactions, HIS residues, which provide charge and a ring at the same time, can also be present on the ligand side, making the refinement step needed there as well. Also, refinement was improved to make sure it is indeed the same HIS residue that is already also forming a π-stacking interaction.
For protein-protein interactions we want to report one hydrophobic interactions per residue for both receptor and ligand side. No need to identify hydrophobic patches on the ligand side as needed in small molecule ligands.
fixes NumPy DeprecationWarning
Fixes several mistakes in interaction detection with peptide ligands
Fixes a mistake in hydrogen bond acceptor identification
Fixes mistakes in waterbridge detection and filtering
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Preparing to release bug-fix release 2.3.1