-
Notifications
You must be signed in to change notification settings - Fork 773
ENH: Change get_hbond_map to use KDTree for distance search
#5182
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
Open
BradyAJohnston
wants to merge
14
commits into
MDAnalysis:develop
Choose a base branch
from
BradyAJohnston:dssp-kdtree
base: develop
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+108
−44
Open
Changes from 5 commits
Commits
Show all changes
14 commits
Select commit
Hold shift + click to select a range
8f25085
initial port to KDTree based HBond map
BradyAJohnston a3f9ac4
change distance_matrix -> query_ball_tree
BradyAJohnston 617e7de
tweak comments
BradyAJohnston 234ad87
tweak commments and layout
BradyAJohnston 93906df
run black
BradyAJohnston f578aa9
add name to AUTHORS
BradyAJohnston d831ba2
add changelog and return comment
BradyAJohnston 86a045d
add test for donor_mask
BradyAJohnston 26c4ca8
run black
BradyAJohnston 2105bd6
change KDTree -> capped_distances
BradyAJohnston e81d2e2
run black
BradyAJohnston bdaadab
move changelog entry
BradyAJohnston f0b2e23
use before distance calculations
BradyAJohnston 4faa47c
warning for init of default box dimensions
BradyAJohnston File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or 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
Oops, something went wrong.
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.
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.
I know the original code was vendored from somewhere else, so it explains the heavy reliance on
linalg.normand the lack of PBC awareness - however, now that we're making changes, should we be using one of ourlib.distancescalls (maybecapped_distance) instead?Uh oh!
There was an error while loading. Please reload this page.
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.
I'm not at all experienced with
lib.distancesare you talking about for the KDTree / potential pair generation or for the actual distance computation? If just for computing distances then on the KDTree generation we would already be discarding some potential across-boundary bonds.We should be able to provide simple periodic checking with
KDTreeyou can specify aboxsizeparameter. But this wouldn't take into account the more complex boundaries we might come across?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.
Okay I just dug in and found
capped_distancewhich should do exactly what we are after with better periodic boundary checking.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.
The performance isn't as good but also as expected with more checks. Still a large improvement over current.
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.
I've currently updated the pair search to use
capped_distances- but the actual distance computation still isn't taking into account periodic boundaries. Is there a periodic boundary aware distance calculation that doesn't do "everything vs everything" whichdistance_arrayseems to do? Ideally we would avoid repeatedly callingcapped_distanceas we have already constructed the KDTree once and can just use those results for computation later on, but still taking into account periodic boundary crossing.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.
Pair-wise distances between two equal groups of atoms can be calculated with MDAnalysis.lib.distances.calc_bonds.