Add script (CLI) / package to calculate atom pairwise energies in a protein complex interface #12
Conversation
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
1 participant
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.
Add script (CLI) to calculate atom pairwise energies in a protein complex interface.
This Python file can also be added as a package in a library, and its function
calculate_interface_atom_pairwise_energiescan be imported and used within other workflows.The algorithm uses OpenMM API to calculate energies. @JoaoRodrigues designed the OpenMM strategy to calculate atom pairwise energies, and I adapted it to fit specifically protein complexes and wrapped it around a CLI and useful function.
The
calculate_interface_atom_pairwise_energiesfunction returns a list of tuples where each tuple contains the information of each pair evaluated. Further description in the docstring. When using the CLI, this is ignored.Using the function (by import) or the CLI, an
energy.logfile is saved to disk by default but can be disabled.Updated the
READMEfile.