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 - protocol updates #367

Conversation

annamherz
Copy link
Contributor

This PR is for further updates relating to running free energy simulations, copying settings from this branch.

  • 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]

Changes:

  • Updates to the FreeEnergy for data processing. This includes concat outside of the function, so that the preprocessing function can be used independently for other analysis outside of BSS. I also updated the truncate arguments for more clarity.
  • All steps for reporting to 200 (from 250). This matches what is in the default protocol settings.
  • 10 A cutoff for PME and 12 A for reaction field.
  • Gromacs protocol softcore settings update for better default values, as well as some additional detail for the integrators/barostats.

Questions:

Suggested reviewers:

@lohedges

@lohedges
Copy link
Contributor

Thanks for this. The tweaks are now incorporated in to #366, so we can close this when you're happy.

@annamherz annamherz closed this Nov 14, 2024
@annamherz annamherz force-pushed the fix_amber_fep_mappings branch from 5dd36b7 to e017148 Compare November 14, 2024 13:52
@annamherz annamherz reopened this Nov 14, 2024
@annamherz annamherz closed this Nov 15, 2024
@annamherz annamherz force-pushed the fix_amber_fep_mappings branch from 754ccdd to 26bd4ec Compare November 15, 2024 13:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants