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

[FEATURE] Support for glycam and ff12 #172

Open
jmichel80 opened this issue Dec 22, 2020 · 2 comments
Open

[FEATURE] Support for glycam and ff12 #172

jmichel80 opened this issue Dec 22, 2020 · 2 comments
Assignees
Labels

Comments

@jmichel80
Copy link
Contributor

We do occasionally work with glycoproteins is there a way to add this support so we can load these systems into BSS? I think using tleap and pdb4amber in BSS should be out of scope but reading in topologies with sugars but I think we would like to be able to read in topologies with sugars. We have already hit this as an issue.

I guess it shouldn’t be the biggest problem just that when you use sugars you normally have to use ff12SB. So I guess we may need an override flag or something.

@lohedges
Copy link
Member

From my reading of the AmberTools manual, it looks like GLYCAM is supported for ff14SB by adding:

source leaprc.GLYCAM_06j-1

(It only mentions ff14SB but perhaps it works with older versions of the forcefield too. The GLYCAM website is horribly out of date, but mentions ff99SB onwards.)

From reading the tLEaP output, this also pulls in tip3p ion parameters for monovalent ions, so perhaps we also need to be careful combining this with our ion handling.

Currently trying to find some example glycoproteins that work. A quick search of the PDB hasn't provided anything useful, yet.

@lohedges lohedges changed the title Support for glycam and ff12 [FEATURE] Support for glycam and ff12 Jan 28, 2021
@lohedges
Copy link
Member

lohedges commented Feb 3, 2021

While I've not yet come up with a specific implementation, this could probably be solved using the same approach as this, i.e. the use could load the required parameters using the optional leap_commands parameter.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants