Skip to content
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

Fix AMBER FEP mappings #366

Merged
merged 15 commits into from
Nov 25, 2024
Merged

Fix AMBER FEP mappings #366

merged 15 commits into from
Nov 25, 2024

Conversation

lohedges
Copy link
Contributor

This PR adds the missing mapping pruning functions from the Exscientia, which are required for stable mappings when using AMBER as the FEP engine. This functionality is tested within the sandpit. I've also tidied a few bits of the mapping code and made sure that sub-functions take kwargs so that we don't get bugs if the order of inputs changes in future.

  • I confirm that I have merged the latest version of devel into this branch before issuing this pull request (e.g. by running git pull origin devel): [y]
  • I confirm that I have permission to release this code under the GPL3 license: [y]

@lohedges lohedges added the bug Something isn't working label Nov 13, 2024
@lohedges lohedges requested a review from mb2055 November 13, 2024 13:47
@lohedges
Copy link
Contributor Author

The PR also includes edits that are required for @annamherz's RBFE pipeline code.

Copy link
Contributor

@mb2055 mb2055 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good 👍

@lohedges lohedges merged commit 357beaf into devel Nov 25, 2024
@lohedges lohedges deleted the fix_amber_fep_mappings branch November 25, 2024 15:53
lohedges added a commit that referenced this pull request Nov 25, 2024
lohedges added a commit that referenced this pull request Dec 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants