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

New (broken) Amber example #440

Closed
wants to merge 2 commits into from
Closed

New (broken) Amber example #440

wants to merge 2 commits into from

Conversation

Yoshanuikabundi
Copy link
Collaborator

@Yoshanuikabundi Yoshanuikabundi commented Apr 13, 2022

Description

This is the Amber example that is currently broken. I've broken it into its own PR as suggested to avoid blocking the other examples PR.

I've never used Amber before. OpenMM and LAMMPS both simulate identical positions and parameters with no trouble, but Amber blows up. It doesn't crash because the velocities are clamped at each step, but the simulation heats very quickly. Possibly unrelatedly, the protein_ligand example demonstrates that Amber's electrostatic potential energy is about 4 times that of LAMMPS or OpenMM.

Previous discussion in #408 and #432

@codecov
Copy link

codecov bot commented Apr 13, 2022

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 77.39%. Comparing base (968a129) to head (170ed50).
Report is 1621 commits behind head on main.

Additional details and impacted files

@Yoshanuikabundi Yoshanuikabundi marked this pull request as draft April 13, 2022 08:41
@j-wags
Copy link
Member

j-wags commented Apr 14, 2022

Ok, @Yoshanuikabundi and I looked at this a lot today, and were unable to determine what's going wrong here.

The changes we tried which were successful by any measure were:

  • Cranking up the gamma_ln to >100 could keep the simulation from exploding

The changes we tried which were not successful by any measure were:

  • Truncating atom names and atom type names to a max of 4 characters (we noticed that they overflowed their fields)
  • Setting the initial and/or final temperature to different values, including 0
  • Cranking up the box size by a factor of 10
  • Changing the fswitch to 8 and the cutoff to 9
  • Changing ntc to 2 and 3 (hbond constraints, all crashed due to large deviation from constraints)

Next steps would be to try:

  • Minimizing to see if it ever stabilizes
  • reducing the number of atoms to keep any 4-character name/type fields from overflowing (or implementing logic to know whern there are identical atoms)
  • Seeing whether the "explodey" molecules have their atoms in different orders from each other (maybe bonds in later isntances of a molecule are getting mangled by a reference vs. topology order thing?)

@mattwthompson mattwthompson mentioned this pull request Aug 29, 2024
3 tasks
@mattwthompson
Copy link
Member

Moving this into #1046

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.

3 participants