Repository navigation
ENH: Speedup the DSSP constructor - #5504
Open
BradyAJohnston wants to merge 1 commit into
Open
BradyAJohnston wants to merge 1 commit into
BradyAJohnston wants to merge 1 commit into
Conversation
7 tasks done
Documentation build overview
|
This branch has not been deployed
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
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.
Supersedes #5503 so that this PR can be stacked with later PRs.
The
DSSP()constructor'sselect_atomswas called on every single residue creating many atom groups and being a performance bottleneck especially on larger systems. Creating multiple atom groups has been replaced by numpy arrays providing a significant speedup for the constructor (~50xin my benchmarks).Changes made in this Pull Request:
_get_coordsis now one gather instead of a per-residue loop that ran every frameset(map(lambda...))).X | YinsteadLLM / AI generated code disclosure
LLMs or other AI-powered tools (beyond simple IDE use cases) were used in this contribution: no
I did have Claude write the benchmarking script (attached at bottom) but not the code or tests.
PR Checklist
package/CHANGELOGfile updated?package/AUTHORS? (If it is not, add it!)Developers Certificate of Origin
I certify that I can submit this code contribution as described in the Developer Certificate of Origin, under the MDAnalysis LICENSE.
Benchmarks
guess_hydrogens=Trueguess_hydrogens=FalseScript
Details