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

Multiple Dihedral types (equations) not accepted (Example: CHARMM style with Periodic and Harmonic dihedrals) #777

Closed
bc118 opened this issue Oct 21, 2023 · 3 comments

Comments

@bc118
Copy link
Contributor

bc118 commented Oct 21, 2023

Multiple Dihedral types (equations) not accepted (Example: CHARMM style with Periodic and Harmonic dihedrals)

Multiple dihedral types should be accepted for both the proper and improper dihedrals. This is the standard input in the CHARMM format. However, in CHARMM, the harmonic dihedrals (proper and improper) are listed as periodic with n=0 (yes, this can be confusing.

We should allow different dihedral types, entering correctly the periodic and harmonic forms as the equations define (see the attached XML). In MoSDeF-GOMC, we will read the proper and improper harmonic dihedrals and write them as the proper and improper periodic dihedrals with n=0 for the CHARMM FF style (required for CHARMM style format - yes, it is confusing). Each writer should handle this separately for their suited engines, where this specific formatted example is for NAMD and the future GOMC once harmonic dihedrals are added.

This is critical if we ever want to be able to use the CHARMM FF in MoSDeF force fields/simulations.

I have provided an example of a proper periodic and harmonic dihedral that fails due to the different dihedral styles.

gmso_ff_with_periodic_and_harmonic_dihedrals.zip

@CalCraven
Copy link
Contributor

We have an open PR for this that has gone stale. Would you consider trying to restart this? I think you would just "layer" dihedrals to make the full harmonic and periodic pseudo-hybrid PR that CHARMM likes to use.
#569

@bc118
Copy link
Contributor Author

bc118 commented Oct 23, 2023

Yeah, I believe this issue does overlap with the PR you mentioned above. Maybe we add these comments to that PR?

@bc118
Copy link
Contributor Author

bc118 commented Oct 24, 2023

I moved my comments in to PR #569, so I closed this one.

@bc118 bc118 closed this as completed Oct 24, 2023
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

No branches or pull requests

2 participants