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

double bonds #196

Open
richardjgowers opened this issue Dec 14, 2018 · 2 comments
Open

double bonds #196

richardjgowers opened this issue Dec 14, 2018 · 2 comments
Labels

Comments

@richardjgowers
Copy link
Contributor

So adding double bonds (ie C=O)

I guess this is low priority because by defining the coordination of atoms this is implicit?

If we wanted to add this, from what I can see:

  • add rules to the parser so it can expect a bond symbol in branches
  • add labels to edges in the nx.Graph denoting single/double/etc
  • make sure the rules check for degree of bonds

And I'm guessing these rules might have to be "soft" so that molecules with single bonds everywhere (even where double is appropriate) still get typed. So something like how types give higher precedence, bondedness should do similar?

@mattwthompson
Copy link
Member

I guess UA systems are the case in which this is relevant? In atomistic systems we implicitly do this based on hybridization (3 vs 4 bonds to a carbon, etc.) and don't really have the concept of single vs double vs etc. bonds. In the example of a UA carbonyl, a string like [O;X1]C would be able to type it but would have trouble deciding if it's a carbonyl or an alcohol.

Do you need different atomtyping rules for double and single bonds, apply different bond parameters, or both? We don't support it yet (#63) but SMARTS has the concept of bond types.

Something else to think about is that the input parmed.Structure/mb.Compound/OpenMM equivalent would needs its bonds to be labelled as double bonds. I think ParmEd and OpenMM support this but mBuild may not.

@richardjgowers
Copy link
Contributor Author

richardjgowers commented Dec 16, 2018 via email

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